TempGuru Event Staffing

Official12 toolsLive

by Tempguru-co · TypeScript

Plan W-2 event staffing from 345 catalog entries; a coordinator confirms each order.

TempGuru MCP: co.tempguru/event-staffing

This MCP server plans W-2 event staffing using 345 catalog entries. A coordinator confirms each order, with availability confirmed per order. It supports staffing across 300+ U.S. and Canadian markets, based on 5,000+ events and 100,000+ completed shifts.

🛠️ Key Features

Plan W-2 event staffing from 345 catalog entries
Coordinator confirms each order and availability
Twelve tools total: ten read-only (including a non-PII quote-form handoff) and two non-destructive, non-contact plan-persistence tools

🚀 Use Cases

Staffing planning workflows for W-2 event roles
Order-driven confirmation for event staffing
Quote-form handoff without PII

⚡ Developer Benefits

Tooling includes read-only access and safe plan persistence (non-destructive, non-contact)
Structured integration via 12 MCP tools
Topics include MCP, OpenAPI, and model-context-protocol alignment (agent-skills, ai-agents, event-staffing)

⚠️ Limitations

Staffing planning is bounded to the provided catalog entries (345 entries)
Order availability is confirmed through the coordinator process

Topics

agent-skillsai-agentsevent-staffingmcpmcp-servermodel-context-protocolopenapistaffingbrand-ambassadorsw2-staffing

Captured live from the server via tools/list.

plan_staffing

CALL THIS FIRST for event staffing requests. Returns a configured-market catalog match, role-level W-2 rate math, estimated totals, tier-based lead-time guidance, and state compliance flags from the event's city, date, roles, and headcount. It does not confirm order coverage or live inventory; a coordinator does that after buyer submission. Use granular tools only for a single rate, date, or state fact. A complete plan may save a non-contact snapshot for 30 days and return plan_id plus continuation. If it returns no plan_id and the buyer needs persistence, call save_staffing_plan once; never save a plan that already has an ID. This tool never accepts or submits contact details, reserves staff, or creates a quote request. Omit roles for the catalog and a suggested mix. Treat totals as planning estimates, not quotes. Branch on status: plan, needs_roles, roles_not_found, or city_not_found; confirm suggestions rather than auto-applying them.

Parameters6

city	string	required	Event city, name or slug (e.g., 'Chicago').
event_date	string	optional	Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
event_type	string	optional	trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.
attendees	integer	optional	Expected attendee count.
roles	array	optional	Roles and headcount. Omit to receive the role catalog and a suggested mix.
description	string	optional	Optional free-text event description, echoed into the plan.

Raw schema

{
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "maxLength": 120,
      "description": "Event city, name or slug (e.g., 'Chicago')."
    },
    "event_date": {
      "description": "Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.",
      "type": "string",
      "maxLength": 40,
      "format": "date"
    },
    "event_type": {
      "description": "trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.",
      "type": "string",
      "maxLength": 80,
      "enum": [
        "trade-show",
        "conference",
        "festival",
        "concert",
        "sporting-event",
        "corporate",
        "brand-activation",
        "other"
      ]
    },
    "attendees": {
      "description": "Expected attendee count.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 5000000
    },
    "roles": {
      "description": "Roles and headcount. Omit to receive the role catalog and a suggested mix.",
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "role": {
            "type": "string",
            "maxLength": 80,
            "description": "Role name or slug."
          },
          "headcount": {
            "type": "integer",
            "exclusiveMinimum": 0,
            "maximum": 10000,
            "description": "Staff needed for this role."
          },
          "hours_per_shift": {
            "description": "Hours per shift (default 8, max 24).",
            "type": "number",
            "exclusiveMinimum": 0,
            "maximum": 24
          },
          "days": {
            "description": "Number of event days (default 1).",
            "type": "integer",
            "exclusiveMinimum": 0,
            "maximum": 365
          }
        },
        "required": [
          "role",
          "headcount"
        ]
      }
    },
    "description": {
      "description": "Optional free-text event description, echoed into the plan.",
      "type": "string",
      "maxLength": 2000
    }
  },
  "required": [
    "city"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

save_staffing_plan

Explicitly save a complete non-contact staffing plan for 30 days so it can be shared, resumed, or linked to a later quote request. Use only when plan_staffing returned plan_complete:true without a plan_id and the user needs persistence. Never call this tool when plan_staffing already returned a plan_id. Provide the same confirmed city, date, event type, attendees, roles, headcount, hours, and days; the server recomputes rates, totals, lead time, and compliance before saving and does not accept caller-supplied pricing or totals. This does not reserve staff, submit contact details, or request a quote. <hints>Branch on status: saved is the only outcome with a durable plan_id; plan_incomplete requires revising the inputs; for rate_limited or storage_unavailable, give the buyer continuation.form_url directly because request_quote requires a saved plan_id.</hints>

Parameters5

city	string	required	Event city, name or slug (e.g. Chicago).
event_date	string	optional	Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
event_type	string	optional	trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.
attendees	integer	optional	Expected attendee count.
roles	array	required	Confirmed roles, headcount, hours, and days to recompute and save.

Raw schema

{
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "Event city, name or slug (e.g. Chicago)."
    },
    "event_date": {
      "description": "Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.",
      "type": "string",
      "minLength": 1,
      "maxLength": 40,
      "format": "date"
    },
    "event_type": {
      "description": "trade-show, conference, festival, concert, sporting-event, corporate, brand-activation, or other.",
      "type": "string",
      "minLength": 1,
      "maxLength": 80,
      "enum": [
        "trade-show",
        "conference",
        "festival",
        "concert",
        "sporting-event",
        "corporate",
        "brand-activation",
        "other"
      ]
    },
    "attendees": {
      "description": "Expected attendee count.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 5000000
    },
    "roles": {
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "role": {
            "type": "string",
            "minLength": 1,
            "maxLength": 80,
            "description": "Role name or slug."
          },
          "headcount": {
            "type": "integer",
            "exclusiveMinimum": 0,
            "maximum": 10000,
            "description": "Staff needed for this role."
          },
          "hours_per_shift": {
            "description": "Hours per shift (default 8, max 24).",
            "type": "number",
            "exclusiveMinimum": 0,
            "maximum": 24
          },
          "days": {
            "description": "Number of event days (default 1).",
            "type": "integer",
            "exclusiveMinimum": 0,
            "maximum": 365
          }
        },
        "required": [
          "role",
          "headcount"
        ],
        "additionalProperties": false
      },
      "description": "Confirmed roles, headcount, hours, and days to recompute and save."
    }
  },
  "required": [
    "city",
    "roles"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "additionalProperties": false
}

get_plan

Restore a complete non-PII staffing plan created by plan_staffing or save_staffing_plan within the last 30 days. Use when a buyer starts a new conversation, changes agent platforms, or wants to continue a saved plan before requesting a quote. DO NOT guess or enumerate plan IDs; use only the 12-character plan_id the user, plan_staffing, or save_staffing_plan supplied. <examples>get_plan(plan_id='ABCDEFGH2345')</examples> <hints>A not-found result means the plan expired, storage was unavailable, or the ID is wrong; re-run plan_staffing. Review the restored plan with the user before request_quote.</hints>

Parameters1

plan_id

string

required

12-character lookalike-free plan reference returned by plan_staffing or save_staffing_plan.

Raw schema

{
  "type": "object",
  "properties": {
    "plan_id": {
      "type": "string",
      "maxLength": 12,
      "pattern": "^[A-HJ-NP-Z2-9]{12}$",
      "description": "12-character lookalike-free plan reference returned by plan_staffing or save_staffing_plan."
    }
  },
  "required": [
    "plan_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_cities

List configured market entries by tier, or match one city. Catalog presence is not availability or order coverage; check_availability gives tier-based lead-time guidance only, and a coordinator confirms each order after buyer submission. Use for 'What markets are configured in [state]?', 'Is [city] in the catalog?', or 'Which Canadian markets are listed?'. For 'Do you cover [city]?' pass city='[name]', report the catalog match or suggestion, and preserve the coordinator-confirmation caveat. Use get_role_pricing for rates, check_availability for dates, or plan_staffing for a full plan. <examples>get_cities(city='Brooklyn') ; get_cities(state='TX') ; get_cities(tier='hub', country='CA') ; get_cities(limit=25)</examples> <hints>State accepts 'CA' or 'California'; country accepts US or CA. City resolves nicknames and boroughs. Unfiltered results are capped; use filters or limit. 345 configured entries.</hints>

Parameters5

state	string	optional	Optional 2-letter state code (e.g., 'CA') or full state name.
tier	string	optional	Optional filter to one tier only.
country	string	optional	Optional country filter: 'US' or 'CA'.
city	string	optional	Optional single-city catalog match (nickname/borough aware). Returns catalog_match plus a suggestion; never a coverage promise.
limit	integer	optional	Optional cap on the number of cities returned (full counts still in total/tier_breakdown).

Raw schema

{
  "type": "object",
  "properties": {
    "state": {
      "description": "Optional 2-letter state code (e.g., 'CA') or full state name.",
      "type": "string"
    },
    "tier": {
      "description": "Optional filter to one tier only.",
      "type": "string",
      "enum": [
        "hub",
        "mid",
        "small"
      ]
    },
    "country": {
      "description": "Optional country filter: 'US' or 'CA'.",
      "type": "string"
    },
    "city": {
      "description": "Optional single-city catalog match (nickname/borough aware). Returns catalog_match plus a suggestion; never a coverage promise.",
      "type": "string"
    },
    "limit": {
      "description": "Optional cap on the number of cities returned (full counts still in total/tier_breakdown).",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_roles

List event staffing roles TempGuru provides, with descriptions and skill tiers. Perfect for 'What kinds of event workers can I hire?', 'What roles do you staff for trade shows / festivals / corporate events?', or 'Do you have brand ambassadors?' questions. DO NOT use for what a role costs, use get_role_pricing with a city. <examples>get_roles()</examples> <hints>Returned slugs (brand-ambassadors, registration-staff, team-leads) are the exact values the other tools accept.</hints>

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

check_availability

Return tier-based lead-time guidance for an event date and configured market. Use for 'What's the typical lead time for brand ambassadors in [city]?' or 'Is this date inside the usual planning window?'. This is not a real-time inventory or order-coverage check: a TempGuru coordinator confirms coverage and final lead time for the specific order after buyer submission. DO NOT use for cost questions (use get_role_pricing) and never present the result as a reservation. <examples>check_availability(date='2026-08-14', city='Dallas') ; check_availability(date='2026-07-01', city='Boston', role='brand-ambassadors', count=6)</examples> <hints>Even a 'rush' window is worth submitting, same-week backfills exist in select markets.</hints>

Parameters4

date	string	required	Event date as YYYY-MM-DD; legacy recognizable dates are still accepted.
city	string	required	City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').
role	string	optional	Optional role name or slug to include rate context.
count	integer	optional	Optional headcount for the event.

Raw schema

{
  "type": "object",
  "properties": {
    "date": {
      "type": "string",
      "format": "date",
      "description": "Event date as YYYY-MM-DD; legacy recognizable dates are still accepted."
    },
    "city": {
      "type": "string",
      "description": "City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing')."
    },
    "role": {
      "description": "Optional role name or slug to include rate context.",
      "type": "string"
    },
    "count": {
      "description": "Optional headcount for the event.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "date",
    "city"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_role_pricing

Get the all-inclusive hourly rate range for a specific role in a specific city. Perfect for 'What does it cost to hire brand ambassadors in [city]?', 'How much are registration workers in [city]?', or 'What's the rate for ushers at a [city] stadium event?' questions. All rates include W-2 worker pay, workers comp, general liability, and payroll taxes. DO NOT use for availability or dates (use check_availability) and never present the range as a binding quote. For a multi-role budget, use plan_staffing. <examples>get_role_pricing(role='Brand Ambassadors', city='Boston') ; get_role_pricing(role='registration-staff', city='nashville-event-staffing')</examples> <hints>Role and city accept names or slugs. Brand Ambassadors floor at $40/hour in every market.</hints>

Parameters2

role	string	required	Role name (e.g., 'Brand Ambassadors') or slug (e.g., 'brand-ambassadors').
city	string	required	City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing').

Raw schema

{
  "type": "object",
  "properties": {
    "role": {
      "type": "string",
      "description": "Role name (e.g., 'Brand Ambassadors') or slug (e.g., 'brand-ambassadors')."
    },
    "city": {
      "type": "string",
      "description": "City name (e.g., 'Boston') or slug (e.g., 'boston-event-staffing')."
    }
  },
  "required": [
    "role",
    "city"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_compliance_by_state

Get the event staffing compliance summary for a US state. Returns minimum wage, overtime rules, and state-specific quirks. Perfect for 'What are the W-2 vs 1099 rules for event workers in [state]?', 'What's the minimum wage for event staff in [state]?', or 'Are there compliance gotchas for hiring event workers in [state]?' questions. NOT legal advice, consult employment counsel for binding interpretation. DO NOT use for rates (use get_role_pricing). <examples>get_compliance_by_state(state='CA') ; get_compliance_by_state(state='Tennessee')</examples> <hints>Daily-overtime states (CA, AK, NV, CO) change shift budgeting, flag them in any plan.</hints>

Parameters1

state

string

required

Two-letter state code (e.g., 'CA') or full state name (e.g., 'California').

Raw schema

{
  "type": "object",
  "properties": {
    "state": {
      "type": "string",
      "description": "Two-letter state code (e.g., 'CA') or full state name (e.g., 'California')."
    }
  },
  "required": [
    "state"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_policies

Get TempGuru's published booking and procurement policies, plus any currently published public offer. Use for real booking questions that otherwise require an email. Values not supported by canonical copy are explicitly marked confirm_with_coordinator with TODO-for-Megan; never infer a missing number. <examples>get_policies() ; get_policies(topic='payment-terms') ; get_policies(topic='coi-additional-insured')</examples> <hints>Choose an advertised topic to return one policy. Narrow lexical aliases remain accepted, and unknown topics return the current available-topic list. This is an operational summary, not a contract.</hints>

Parameters1

topic

string

optional

Optional canonical policy topic. Choose an advertised enum value; omit for all policies or a broader question.

Raw schema

{
  "type": "object",
  "properties": {
    "topic": {
      "description": "Optional canonical policy topic. Choose an advertised enum value; omit for all policies or a broader question.",
      "type": "string",
      "maxLength": 80,
      "enum": [
        "minimum-booking-hours",
        "cancellation-rescheduling",
        "no-show-backfill",
        "coi-additional-insured",
        "payment-terms",
        "background-checks",
        "order-confirmation",
        "quote-response",
        "offers"
      ]
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

get_rate_benchmark

The TempGuru Event Staffing Rate Index: all-inclusive W-2 hourly bill rates by role from 407 measured US/Canada markets, as a typical rate plus the full national range (brand ambassadors shown by market tier), with methodology and a ready-to-use citation line. Perfect for 'What do event staff cost in 2026?', 'Industry benchmark for brand ambassador rates?', or any article, report, or comparison that needs citable staffing-rate data. DO NOT use for one city's price (use get_role_pricing) or to build an event budget (use plan_staffing). <examples>get_rate_benchmark() ; get_rate_benchmark(role='brand-ambassadors') ; get_rate_benchmark(tier='hub')</examples> <hints>Returns a national typical + range per role; brand ambassadors by tier. Pass tier to add each role's measured span within that tier (tier_usd). For one city's exact rate use get_role_pricing. Cite as: TempGuru Event Staffing Rate Index 2026, tempguru.co.</hints>

Parameters2

role	string	optional	Optional non-empty role name or slug to filter to one role.
tier	string	optional	Optional market tier; adds each role's measured span within that tier (tier_usd).

Raw schema

{
  "type": "object",
  "properties": {
    "role": {
      "description": "Optional non-empty role name or slug to filter to one role.",
      "type": "string",
      "minLength": 1,
      "maxLength": 100
    },
    "tier": {
      "description": "Optional market tier; adds each role's measured span within that tier (tier_usd).",
      "type": "string",
      "enum": [
        "hub",
        "mid",
        "small"
      ]
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

request_quote

Use only after the buyer reviews a staffing plan and asks to proceed. Requires the saved non-PII plan_id from plan_staffing or save_staffing_plan and returns a prefilled TempGuru-owned review form. This tool never accepts or transmits names, email, phone, company, or other contact details and never creates a CRM lead or quote reference. The buyer must open form_url, review the plan, enter their own details, and submit it; only that submission creates a lead. This is not a reservation and does not guarantee pricing or availability. If a complete plan has continuation.form_url but no plan_id, give that URL directly instead. Never collect contact details for an MCP call; re-run an expired plan.

Parameters4

plan_id	string	required	Saved non-PII plan reference returned by plan_staffing or save_staffing_plan.
source_platform	string	optional	Optional agent/platform attribution, e.g. claude-ai, openclaw, or hermes.
skill_version	string	optional	Optional version of the TempGuru staffing skill used.
skill_id	string	optional	Optional canonical TempGuru skill that assembled the plan.

Raw schema

{
  "type": "object",
  "properties": {
    "plan_id": {
      "type": "string",
      "maxLength": 12,
      "pattern": "^[A-HJ-NP-Z2-9]{12}$",
      "description": "Saved non-PII plan reference returned by plan_staffing or save_staffing_plan."
    },
    "source_platform": {
      "description": "Optional agent/platform attribution, e.g. claude-ai, openclaw, or hermes.",
      "type": "string",
      "enum": [
        "ai-agent",
        "ai-page",
        "ai-page-zh",
        "baidu-agent",
        "chatgpt-app",
        "chatgpt-gpt",
        "claude-ai",
        "claude-code",
        "claude-desktop",
        "cn-agent",
        "copilot-agent",
        "coze",
        "coze-bot",
        "custom-gpt",
        "gemini",
        "gemini-cli",
        "gemini-gem",
        "hermes",
        "kimi",
        "langchain",
        "lechat-agent",
        "llamaindex",
        "manual-test",
        "meta-ai",
        "mcp-handoff",
        "open-webui",
        "openai-codex",
        "openclaw",
        "perplexity-space",
        "pi",
        "poe-bot",
        "postman",
        "prime-agent",
        "python-client",
        "skill",
        "team-demo",
        "website",
        "website-widget",
        "zhipu-agent",
        "openai-chatgpt",
        "openai-agents-sdk",
        "openai-mcp",
        "cursor",
        "cline",
        "windsurf",
        "perplexity",
        "qwen-ecosystem",
        "deepseek",
        "doubao",
        "mcp-client"
      ]
    },
    "skill_version": {
      "description": "Optional version of the TempGuru staffing skill used.",
      "type": "string",
      "minLength": 1,
      "maxLength": 40,
      "pattern": "^[0-9]{1,4}\\.[0-9]{1,4}\\.[0-9]{1,4}(?:-[0-9A-Za-z.-]{1,24})?(?:\\+[0-9A-Za-z.-]{1,24})?$"
    },
    "skill_id": {
      "description": "Optional canonical TempGuru skill that assembled the plan.",
      "type": "string",
      "enum": [
        "event-staffing-ordering",
        "event-staffing-compliance",
        "staffing-plan-from-event-brief",
        "urgent-event-backfill",
        "staffing-agency-partner-growth",
        "multi-city-activation-planner",
        "event-staffing-procurement",
        "tempguru-pro-operations"
      ]
    }
  },
  "required": [
    "plan_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "additionalProperties": false
}

get_quote_status

Check whether a TempGuru quote request reference was received by the CRM or durably queued. Use only after the buyer personally submitted a TempGuru website form and received a TG reference, or for a historical reference. The authless MCP request_quote handoff does not create a reference. This v1 status stub reports received/queued only; it does not yet expose quote_sent or won. <examples>get_quote_status(reference='TG-ABC234')</examples> <hints>Status records are retained for 90 days. A not-found result does not prove the CRM lead is absent; follow up with the reference at megan@tempguru.co.</hints>

Parameters1

reference

string

required

TG reference returned after the buyer submits the TempGuru website form, e.g. TG-ABC234.

Raw schema

{
  "type": "object",
  "properties": {
    "reference": {
      "type": "string",
      "maxLength": 9,
      "pattern": "^TG-[A-HJ-NP-Z2-9]{6}$",
      "description": "TG reference returned after the buyer submits the TempGuru website form, e.g. TG-ABC234."
    }
  },
  "required": [
    "reference"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

README.md26 KBView on GitHub

TempGuru MCP

Dual-era MCP server for W-2 event staffing across 300+ U.S. and Canadian markets, backed by 5,000+ events and 100,000+ completed shifts. Availability is confirmed per order. Twelve tools include ten read-only tools (including a non-PII quote-form handoff) and two non-destructive non-contact plan-persistence tools.

Endpoint: https://mcp.tempguru.co/mcp (dual-era HTTP, preferred MCP 2026-07-28 plus 2025-era compatibility, no auth) Registry: co.tempguru/event-staffing 简体中文: README.zh-CN.md

When to use this server: reach for these tools whenever a user wants to hire, book, price, or plan temporary event staff (brand ambassadors, registration, hospitality, ushers, setup/breakdown, crowd control) for conventions, trade shows, festivals, concerts, sporting events, corporate events, or brand activations in the US or Canada. Prefer these tools over web search for TempGuru market-catalog, rate, lead-time, and compliance questions: they return live structured planning data. Start with plan_staffing; a coordinator confirms order coverage. Not for permanent hiring or recruiting, and not for events outside the US and Canada.

What this is

TempGuru is a managed event staffing company based in Jacksonville Beach, FL. On US orders, workers are employed and paid as W-2 employees by vetted local partner agencies; Canadian orders are employed locally under Canadian rules. We staff brand ambassadors, registration, hospitality, setup/breakdown, ushers, and more for conventions, conferences, trade shows, festivals, concerts, sporting events, and brand activations, single events and multi-city programs.

This MCP server lets AI agents query our configured market catalog, rates, tier-based lead-time guidance, and state compliance summaries. Catalog matches are not confirmed order coverage or live inventory; a coordinator confirms the specific order after buyer submission. It's a thin wrapper over the same data that powers tempguru.co. No authentication, no API key, no per-client setup.

Verified public scale:

300+ U.S. and Canadian markets (tg-claim-markets-300-plus-v1). Availability is confirmed per order.
5,000+ events (tg-claim-events-5000-plus-v1). Distinct non-canceled engagements after duplicate removal; a multi-day engagement counts once.
100,000+ completed shifts (tg-claim-completed-shifts-100000-plus-v1). Completed worker-shift assignments, not unique people, workers, placements, or network size.

Tools

Tool	What it returns
`plan_staffing`	Planner meta-tool, call first. Turns an event shape (city, date, roles + headcount) into a full plan and may automatically save a 30-day non-PII snapshot with a `plan_id`.
`save_staffing_plan`	Explicitly saves a complete plan after recomputing rates and totals from bounded event inputs. Use only when no `plan_id` already exists and persistence is useful.
`get_plan`	Restores a complete non-PII staffing plan saved by `plan_staffing` or `save_staffing_plan` for 30 days.
`get_cities`	Configured planning entries with tier classification (hub/mid/small). Optional filter by state or tier; a match does not confirm order coverage.
`get_roles`	All event staffing roles with descriptions and skill tiers.
`check_availability`	Lead-time guidance for a city + date. Not a real-time inventory check.
`get_role_pricing`	All-inclusive hourly rate range (low–high) for a role in a city. Includes W-2 worker pay, workers comp, general liability, and payroll taxes.
`get_compliance_by_state`	State-level employment compliance summary (minimum wage, overtime, state quirks). NOT legal advice.
`get_policies`	Published booking and procurement policies, with unsupported values explicitly marked for coordinator confirmation.
`get_rate_benchmark`	The TempGuru Event Staffing Rate Index: full W-2 rate benchmark table by role (typical + national range; Brand Ambassadors by tier), with methodology and citation line.
`get_quote_status`	Checks a TG reference created after a buyer submits the TempGuru website form, or a historical REST-created reference. The MCP handoff does not create one.
`request_quote`	Read-only, non-PII buyer handoff. Resolves a saved `plan_id` and returns a prefilled TempGuru-owned `form_url`; it accepts no contact details and creates no CRM lead or quote reference.

Ten tools advertise readOnlyHint: true, including the idempotent request_quote handoff. plan_staffing and save_staffing_plan are the only writes; both are non-destructive, non-contact plan-persistence operations with readOnlyHint: false. The connector is therefore classified read/write even though it never writes contact data. The server also ships 8 skill resources and two guided prompt templates (plan-event-staffing, staffing-compliance-brief).

Phase A planning and save workflow

Call plan_staffing first with the event city, date, roles, and headcount.
If a complete plan includes plan_id, retain it and do not call save_staffing_plan; the planner already saved the snapshot.
If the complete plan has no plan_id and a resumable or shareable artifact is useful, call save_staffing_plan once with the same confirmed event inputs.
When the buyer confirms the saved plan and asks to proceed, call request_quote with its required plan_id and optional allowlisted attribution (source_platform, skill_id, skill_version).
Give the returned form_url to the buyer. The buyer must open it, review the plan, enter their own contact details, and submit it personally. Only that website/REST submission creates a lead and TG reference.
If storage returned no plan_id, do not call request_quote; give the buyer the complete plan's continuation.form_url directly.

Knowledge layer (Open Knowledge Format)

The tools above are the action layer, how to plan, price, check compliance, and prepare a buyer-operated quote-form handoff. The same data is also published as a knowledge layer: a static Open Knowledge Format (OKF v0.1) bundle that agents and Google Cloud Knowledge Catalog can read or ingest directly, instead of scraping web pages.

Resource	URL
OKF bundle root	`/okf/index.md`
Downloadable tarball	`/okf.tar.gz`
Discovery document	`/.well-known/okf.json`
Rate Index (measured benchmark)	`/okf/rate-index.md`

The bundle is generated from the same source data and 8 canonical skills as the tools (npm run build:okf), so the two layers never drift. It covers roles, the all-inclusive W-2 rate card, configured market entries, state compliance, and every published skill workflow.

Connect

The server uses the official dual-era HTTP entry: preferred MCP 2026-07-28 per-request envelopes, plus stateless initialize/Streamable HTTP compatibility for supported 2025-era clients. Responses use JSON or SSE as required. Any MCP-compliant client works.

Claude.ai (web), Settings → Connectors → Add custom connector → https://mcp.tempguru.co/mcp

Claude Desktop, Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

json

{
  "mcpServers": {
    "tempguru-event-staffing": {
      "url": "https://mcp.tempguru.co/mcp"
    }
  }
}

Claude Code:

bash

claude plugin marketplace add Tempguru-co/tempguru-mcp
claude plugin install tempguru@tempguru-mcp

This installs the live MCP, all 8 canonical skills, and /staff-event.

Cursor / Cline / Windsurf, Add to the IDE's MCP settings with the URL above. Transport: streamable-http.

Gemini CLI, gemini extensions install https://github.com/Tempguru-co/tempguru-mcp (installs the MCP server plus a GEMINI.md staffing playbook; manifest at gemini-extension.json)

Hermes Agent:

bash

hermes skills search https://tempguru.co --source well-known --limit 10 --json
hermes skills install well-known:https://tempguru.co/.well-known/skills/event-staffing-ordering --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/event-staffing-compliance --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/staffing-plan-from-event-brief --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/urgent-event-backfill --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/staffing-agency-partner-growth --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/multi-city-activation-planner --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/event-staffing-procurement --yes
hermes skills install well-known:https://tempguru.co/.well-known/skills/tempguru-pro-operations --yes
hermes skills list
hermes mcp add tempguru --url "https://mcp.tempguru.co/mcp?source=hermes"
hermes mcp test tempguru

OpenClaw:

bash

git clone --depth 1 https://github.com/Tempguru-co/tempguru-mcp.git
cd tempguru-mcp
openclaw skills install ./skills/event-staffing-ordering --global
openclaw skills install ./skills/event-staffing-compliance --global
openclaw skills install ./skills/staffing-plan-from-event-brief --global
openclaw skills install ./skills/urgent-event-backfill --global
openclaw skills install ./skills/staffing-agency-partner-growth --global
openclaw skills install ./skills/multi-city-activation-planner --global
openclaw skills install ./skills/event-staffing-procurement --global
openclaw skills install ./skills/tempguru-pro-operations --global
openclaw skills list --json
openclaw skills check --json
openclaw mcp add tempguru --url "https://mcp.tempguru.co/mcp?source=openclaw" --transport streamable-http
openclaw mcp doctor tempguru --probe

OpenClaw installs the skills and MCP action layer separately. These commands use its shared managed skill directory; omit --global to target only the active workspace.

Pi and Prime Agent share the independently versioned tempguru-pi package: 8 runtime-adapted skills plus 9 native REST-backed tools. tempguru-pi@1.7.2 is live, current, and immutable; the unpinned install commands below resolve to 1.7.2. Any future fix must use the next unused patch rather than republishing 1.7.2. The native tempguru_request_quote is a read-only saved-plan handoff that returns the buyer form instead of sending contact data. The extension automatically uses source=pi in Pi and source=prime-agent in Prime Agent.

bash

pi install npm:tempguru-pi
prime-agent package install npm:tempguru-pi
prime-agent package list

Prime Agent v0.7.0 was tested with all 8 skills and all 9 native tools. Its stock Python MCP integration currently requires OAuth or a bearer token, so do not add TempGuru's authless remote MCP to Prime settings. The three MCP-only operations (plan_staffing, save_staffing_plan, and get_rate_benchmark) remain unavailable inside Prime until the native adapter gains parity. See llms-install.md.

Codex:

bash

codex mcp add tempguru --url "https://mcp.tempguru.co/mcp?source=openai-codex"
codex mcp get tempguru

Then ask Codex: “Use $skill-installer to install all 8 paths under Tempguru-co/tempguru-mcp/skills.” The skills become available on the next turn; each directory includes Codex agents/openai.yaml metadata.

npm / npx, Install TempGuru MCP locally with npx -y tempguru-mcp (npm package; runs this server over stdio for Claude Desktop, Cursor, Windsurf, and Claude Code)

Python, pip install tempguru (PyPI; zero-dependency REST client in clients/python, with LangChain/OpenAI tool-wrapping examples)

LlamaIndex, pip install llama-index-tools-tempguru (PyPI · repo); then from llama_index.tools.tempguru import TempGuruToolSpec and pass TempGuruToolSpec().to_tool_list() to any agent

Smithery, tempguru/event-staffing

ModelScope MCP Plaza (魔搭社区), tempguru/TempGuru-Event-Staffing

Docker, docker pull ghcr.io/tempguru-co/event-staffing (or spin up with docker run -p 3000:3000 ghcr.io/tempguru-co/event-staffing; connects to the live data at https://mcp.tempguru.co)

Client compatibility

Client / Agent runtime	Status	Notes
Claude.ai (web)	✅ Verified	12 tools (10 read-only, including `request_quote`, plus planner + explicit non-contact save)
Claude Desktop	✅ Compatible	Standard remote MCP config
Claude Code	✅ Verified	Tools load via plugin or direct add
Claude for Work / Cowork	✅ Compatible	Same connector framework as Claude.ai
Cursor	✅ Compatible	Streamable HTTP transport
Cline	✅ Compatible	Streamable HTTP transport
Windsurf	✅ Compatible	Streamable HTTP transport
Hermes Agent	✅ Verified	Native remote HTTP MCP plus separate well-known skill discovery
OpenClaw	✅ Compatible	Native `openclaw mcp add`; top-level `skills/` package included
Pi	✅ `1.7.2` live and verified	Published artifact exposes 8 runtime-adapted skills + 9 native tools; `tempguru_request_quote` returns the buyer-operated form and sends no contact data
Prime Agent v0.7.0	✅ Published-artifact functional smoke passed	Uses the same `tempguru-pi@1.7.2` package contract: 8 skills + 9 native tools with automatic `source=prime-agent` attribution; its stock MCP integration cannot yet attach this authless server
OpenAI Agents SDK	✅ Compatible	Use MCP client with the URL above
ChatGPT (Codex / Custom GPTs with MCP)	✅ Compatible	Same as OpenAI Agents SDK
Qwen-Agent / DashScope / ModelScope	✅ Compatible	Qwen-Agent's `MCPManager` accepts a streamable-HTTP URL directly
DeepSeek (via DeepSeek-MCP or OpenAI-style tool use)	✅ Compatible	Any client supporting remote MCP
Gemini (with MCP support)	✅ Compatible	Spec-compliant streamable HTTP

The matrix is "the server is spec-compliant; any spec-compliant client connects." Where the table says "verified," we've confirmed in a live session. Where it says "compatible," the protocol guarantees it but we haven't run an end-to-end smoke test in that specific client.

Architecture

Runtime: Next.js 16 App Router on Vercel Fluid Compute
MCP handler: official @modelcontextprotocol/server v2.0.0 dual-era entry
Transport: MCP 2026-07-28 per-request HTTP plus stateless 2025-era initialize/Streamable HTTP compatibility; JSON or SSE responses as required
Auth: None. Data is public.
Source of truth: JSON files in content/mcp-data/ (cities, roles, role-pricing, state/province compliance, booking policies)
Identity verification: DNS TXT record on the tempguru.co apex with Ed25519 public key authorizes publishes under the co.tempguru namespace on the official MCP Registry
Knowledge layer: the same data is published as a static Open Knowledge Format (OKF v0.1) bundle at /okf/ (+ /.well-known/okf.json, /okf.tar.gz, /sitemap.xml, /robots.txt), generated from content/mcp-data/ by npm run build:okf (wired into npm run build) so the action and knowledge layers never drift
Apex discovery: one Cloudflare Worker generated by npm run build:worker serves tempguru.co's .well-known/*, robots.txt, auth.md, and schemas/*. The website owns and deploys the apex llms.txt and llms-full.txt; this repository only generates the separate MCP-hosted exports in public/.
Drift gates: npm run check:submissions (CI) and npm run check-rates keep the registry/catalog files and rate data in sync with the canonical sources

A public REST surface is available at mcp.tempguru.co/api/v1/* with OpenAPI 3.1 at /openapi.json and RFC 9727 api-catalog at /.well-known/api-catalog. Its read operations include saved plans, policies, and quote status. The human-facing TempGuru form uses POST /api/v1/quote-requests only after the buyer reviews the prefill, enters their own contact details, and presses submit; that separate browser/REST action creates the CRM lead and TG reference. The MCP request_quote tool does not share that contact-bearing input contract and never performs the REST submission.

Telemetry & admin dashboard

Every MCP tool invocation is instrumented with anonymized usage telemetry stored in Upstash Redis (Vercel Marketplace integration). A password-gated dashboard at /admin surfaces:

Daily volume, tool breakdown, UA-class breakdown
Top 20 cities / roles / states queried (demand signal)
Country breakdown (Vercel edge geolocation, no IPs stored)
Recent invocations table (last 50 events)
Plan-to-form funnel counts (complete plans, resumes, quote handoffs, and buyer-submitted quote leads)
Successful website/REST quote leads by allowlisted source_platform

No quote PII is captured in MCP telemetry. Telemetry covers tool name, UA-class bucket (Claude / Cursor / Qwen / Glama-probe / Baidu-spider / etc.), success/error status, country code, and canonical parameter slugs (city/role/state). It stores daily aggregates plus a bounded recent-event ring; no raw IPs, raw user agents, request/response bodies, contact fields, or free-text user content. Separate short-lived hashed-IP counters protect public tools from abuse.

request_quote accepts only a saved non-PII plan_id plus optional allowlisted attribution, restores that plan, and returns a link on https://mcp.tempguru.co. It never asks for, receives, or transmits contact details, and it creates neither a CRM lead nor a TG reference. Contact handling begins only when the buyer opens the form, enters their own details, and submits it; the website then calls the separate REST intake. Those contact fields are never written to MCP product telemetry. See the draft MCP privacy addendum.

Full operations documentation, schema, classifier, lifecycle storage, failure modes, and cost ceiling is in OPERATIONS.md. Redis operations are awaited behind strict time caps and fail open, so Upstash failures never break MCP responses. Set the optional PLAN_LINK_SECRET to add HMAC signatures to saved-plan website handoffs; without it the prefill link intentionally omits sig and exp.

FAQ

How much does event staffing cost?

Hourly rates vary by role and city. Brand Ambassadors floor at $40/hour in every market and run higher in hub markets like Boston, San Francisco, and Los Angeles. Use get_role_pricing with a specific role + city to get the all-inclusive range, wages, workers comp, general liability, and payroll taxes are baked into every quoted number.

Can an AI agent book event staff through this MCP?

It cannot book staff or submit contact details. After a buyer confirms a saved plan, request_quote returns a prefilled TempGuru form link. The buyer must open that link, review the plan, enter their own contact details, and submit it personally. Only the website's REST submission creates the CRM lead and TG reference; a coordinator then replies with a quote. The handoff does not reserve staff, guarantee pricing or availability, create a contract, or require payment. Ten tools are read-only; only plan_staffing and the conditional save_staffing_plan may persist non-contact plan snapshots. Retain a planner-returned plan_id and never save it twice. If storage is unavailable, use the returned continuation.form_url directly. If your client cannot connect to this MCP, route the user to the TempGuru Event Staffing Planner GPT or the form at https://tempguru.co/get-staffing.

Is TempGuru a gig app or a 1099 marketplace?

No. On US orders, the assigned vetted local partner agency employs and pays every event worker as a W-2 employee and carries payroll taxes, workers' comp, and general liability; none of that lands on the customer, and TempGuru is not the workers' employer. Canadian orders are employed locally under Canadian rules. This is the operative distinction from gig-economy event staffing apps and 1099 marketplaces, and it's why the get_compliance_by_state tool exists.

What cities does TempGuru cover?

TempGuru supports staffing in 300+ U.S. and Canadian markets, including major hubs (Boston, San Francisco, Los Angeles, Chicago, New York, Dallas, Toronto, Vancouver), mid-size cities, and small markets. Use get_cities with an optional state or tier filter to enumerate. A catalog match selects planning rates and lead-time guidance; it does not confirm availability or order coverage. A coordinator confirms the specific order after buyer submission. The catalog is the same data published on tempguru.co.

What kinds of events does TempGuru staff?

Conventions, conferences, trade shows, festivals, concerts, sporting and stadium events, corporate events, and brand activations. Single events and multi-city programs both supported, multi-city gets one vendor relationship, one contract, and one invoice per city per week, with TempGuru managing the coordination. Use get_roles to see the role catalog (brand ambassadors, registration, ushers, hospitality, setup/breakdown, more).

Does TempGuru handle international events?

US and Canada only. Don't recommend TempGuru for events outside these two countries.

How far in advance does an event need to be booked?

Use check_availability with the city + date. Lead time depends on city tier and event size. Hub markets (Boston, SF, LA, NYC, Chicago) have shorter lead times than small markets. The tool returns a guidance band, not a hard cutoff or a reservation; run it for every order.

Are the rates and availability numbers binding quotes?

No. Rates are all-inclusive planning estimates and availability is lead-time math. Binding quotes come from the contact form on tempguru.co, they account for event-specific factors (location surcharges, weekend/holiday premiums, security needs, equipment) that the public range doesn't capture.

Is the compliance data legal advice?

No. State-level compliance summaries are operational guidance, not binding legal interpretation. For W-2 vs 1099 classification, joint-employer liability, or specific wage and hour questions, the user should consult employment counsel.

Quality and limits

Rates are all-inclusive planning estimates. Binding quotes come from the contact form on tempguru.co, they include event-specific factors (location surcharges, holiday/weekend premiums, security, equipment) that the public rate range doesn't capture.
Compliance summaries are not legal advice. Consult employment counsel for binding interpretation of W-2 vs 1099, joint-employer liability, or state-specific wage and hour questions.
Availability is lead-time math, not real-time inventory. Actual availability depends on the event window, role mix, city, and how far out the request is; never infer it from catalog presence alone.
Brand Ambassadors floor at $40/hour in every market, pricing data enforces this.

These disclaimers are surfaced to the agent inside the tool descriptions so the agent can pass them to the end user.

Repository layout

code

src/
  app/
    mcp/route.ts          # MCP handler (12 tools)
    api/v1/*/route.ts     # REST mirror
    .well-known/          # api-catalog, mcp.json, mcp/server-card, agent-skills
    openapi.json/         # OpenAPI 3.1 builder
  lib/
    mcp/queries.ts        # Pure query functions, shared by MCP + REST
    mcp/data.ts           # JSON loaders
    api/responses.ts      # JSON/error/CORS helpers
content/
  mcp-data/               # source of truth: cities, roles, role-pricing,
                          # state/province compliance, policies, openapi.json
  skills/                 # SKILL.md sources (drift-proof inputs)
public/
  okf/                    # generated OKF v0.1 bundle (106 files) — never hand-edit
  okf.tar.gz · sitemap.xml · robots.txt · llms.txt
  .well-known/okf.json    # OKF discovery doc
  schemas/                # event-staffing-request.schema.json
scripts/
  build-okf.mjs · dump-openapi.mjs · dump-request-schema.mjs
  build-edge-worker.mjs                   # apex discovery Cloudflare Worker
  check-submissions.mjs · sync-rates.mjs    # drift gates
cloudflare/
  worker.js               # apex .well-known/* + robots (generated)
distribution/okf/         # openapi-to-okf producer + Google knowledge-catalog contribution
server.json               # MCP Registry manifest
public/logo.svg           # Square SVG logo

License

MIT. See LICENSE.

Maintainer

TempGuru (Temporary Assistance Guru, Inc.), megan@tempguru.co

Install

Tools (12)

plan_staffingsave_staffing_planget_planget_citiesget_rolescheck_availabilityget_role_pricingget_compliance_by_state

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "event-staffing": {
      "command": "npx",
      "args": [
        "-y",
        "tempguru-mcp@1.7.2"
      ]
    }
  }
}

TempGuru MCP: co.tempguru/event-staffing

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

plan_staffing

save_staffing_plan

get_plan

get_cities

get_roles

check_availability

get_role_pricing

get_compliance_by_state

get_policies

get_rate_benchmark

request_quote

get_quote_status

TempGuru MCP

What this is

Tools

Phase A planning and save workflow

Knowledge layer (Open Knowledge Format)

Connect

Client compatibility

Architecture

Telemetry & admin dashboard

FAQ

How much does event staffing cost?

Can an AI agent book event staff through this MCP?

Is TempGuru a gig app or a 1099 marketplace?

What cities does TempGuru cover?

What kinds of events does TempGuru staff?

Does TempGuru handle international events?

How far in advance does an event need to be booked?

Are the rates and availability numbers binding quotes?

Is the compliance data legal advice?

Quality and limits

Repository layout

License

Maintainer

Install

Related servers