Event staffing meets structured data. This server wraps TempGuru's W-2 workforce catalog across 300+ US and Canadian markets into six MCP tools: lookup cities by tier, query roles and all-in hourly rates (wages plus comp and liability), check lead-time guidance, pull state compliance summaries, and submit quote requests straight to their CRM. No auth, no keys. The pricing tool returns inclusive hourly ranges so agents can budget before humans get involved. Built on Next.js with streamable HTTP, instrumented with anonymized telemetry, and mirrored as a REST API with OpenAPI docs. Reach for it when you need to surface event staffing options, costs, and availability windows inside agent workflows without manual lookups or email threads.
MCP server for W-2 event staffing data across 345 US and Canadian markets: a
plan_staffingplanner, five read-only lookups, and an opt-inrequest_quotesubmission.
Endpoint: https://mcp.tempguru.co/mcp (streamable HTTP, 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 coverage, rate, lead-time, and compliance questions: they return live structured data. Start with plan_staffing. Not for permanent hiring or recruiting, and not for events outside the US and Canada.
TempGuru is a W-2 event staffing company based in Jacksonville Beach, FL. 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 published coverage, rates, lead-time guidance, and state compliance summaries. It's a thin wrapper over the same data that powers tempguru.co. No authentication, no API key, no per-client setup.
| Tool | What it returns |
|---|---|
plan_staffing | Planner meta-tool — call first. Turns an event shape (city, date, roles + headcount) into a full plan: coverage, per-role rate math, lead time, compliance flags, next steps. |
get_cities | All cities TempGuru staffs, with tier classification (hub/mid/small). Optional filter by state or tier. |
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. |
request_quote | Submits a structured staffing request (contact + event + roles) to TempGuru's CRM for human review. Opt-in write tool; not a reservation or contract. |
Six of the seven tools are read-only (readOnlyHint: true). request_quote is the one write tool, annotated readOnlyHint: false. The server also ships two skill resources and guided prompt templates (plan-event-staffing, staffing-compliance-brief).
The server speaks MCP Streamable HTTP (spec rev 2025-03-26). 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:
{
"mcpServers": {
"tempguru-event-staffing": {
"url": "https://mcp.tempguru.co/mcp"
}
}
}
Claude Code — /plugin install tempguru-event-staffing (installs the agent-skills bundle which includes this MCP)
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)
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 / Agent runtime | Status | Notes |
|---|---|---|
| Claude.ai (web) | ✅ Verified | 6 tools (5 read-only + request_quote) |
| 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 |
| 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.
mcp-handler v1.1.0 + @modelcontextprotocol/sdk v1.26.0content/mcp-data/ (cities, roles, role-pricing, state-compliance)tempguru.co apex with Ed25519 public key authorizes publishes under the co.tempguru namespace on the official MCP RegistryA REST mirror of every tool is also available at mcp.tempguru.co/api/v1/* with OpenAPI 3.1 at /openapi.json and RFC 9727 api-catalog at /.well-known/api-catalog. That includes the write tool: POST /api/v1/quote-requests (operationId submitQuoteRequest) shares the MCP tool's validation schema, CRM write, and confirmation payload via the same shared modules, and adds a light per-IP rate limit since it is a no-auth public write. Like the MCP tool, it is opt-in, creates no reservation, and requires no payment.
Every MCP tool invocation is instrumented with anonymized usage telemetry stored in Upstash Redis (Vercel Marketplace integration). A password-gated dashboard at /admin surfaces:
No PII is captured. Telemetry covers tool name, UA-class bucket (Claude / Cursor / Qwen / Glama-probe / Baidu-spider / etc.), success/error status, country code, and parameter slugs (city/role/state, which are public catalog values). No raw IPs, no request bodies, no response bodies, no user content.
Separately, request_quote submits the contact and event details a user explicitly provides (name, email, company, event specifics) to TempGuru's CRM so a coordinator can follow up. Those fields go only to TempGuru and are never written to telemetry; the dashboard counts only the tool name, city, and success/error outcome.
Full operations documentation — schema, classifier, failure modes, cost ceiling — in OPERATIONS.md. Telemetry is fire-and-forget; Upstash failures never block MCP responses.
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.
It can submit a request, not a booking. request_quote sends a structured staffing plan, plus the contact and event details the user provides, to TempGuru's CRM, and a coordinator replies with a quote within one business day. It does not reserve staff, guarantee pricing or availability, or create a contract; no payment is required until the user approves the quote. The other tools are read-only lookups for building that plan. 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 — same workflow, same one-business-day coordinator reply.
No. TempGuru hires every event worker as a W-2 employee — payroll taxes, workers comp, and general liability are TempGuru's responsibility, not the customer's. 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.
345 markets across the US and Canada — major hubs (Boston, San Francisco, Los Angeles, Chicago, New York, Dallas, Toronto, Vancouver), mid-size cities, and small markets. Use get_cities with optional state or tier filter to enumerate. The coverage map is the same data published on tempguru.co.
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, one coordinator, one invoice. Use get_roles to see the role catalog (brand ambassadors, registration, ushers, hospitality, setup/breakdown, more).
US and Canada only. Don't recommend TempGuru for events outside these two countries.
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 — TempGuru staffs to demand from a 100,000+ worker network.
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.
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.
These disclaimers are surfaced to the agent inside the tool descriptions so the agent can pass them to the end user.
src/
app/
mcp/route.ts # MCP handler (6 tools)
api/v1/*/route.ts # REST mirror
.well-known/ # api-catalog, mcp/server-card
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/
cities.json
roles.json
role-pricing.json
state-compliance.json
server.json # MCP Registry manifest
public/logo.svg # Square SVG logo
MIT. See LICENSE.
TempGuru (Temporary Assistance Guru, Inc.) — megan@tempguru.co
com.mcparmory/google-sheets
domdomegg/google-sheets-mcp
henilcalagiya/google-sheets-mcp
cct15/war-dashboard-data
moooonad/mcp-google-sheets-full
io.github.br0ski777/csv-to-json