Tempguru MCP Server

MCP server and CLI for W-2 event staffing: plan staffing, hire event staff, check brand ambassador rates and availability, state labor compliance, and quote requests across 345 US/Canada markets. Includes the TempGuru Event Staffing Rate. Exposed over MCP by the tempguru mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

Its toolset

Everything the assistant can do here goes through one of these:

• 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
• 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
• get_plan — Restores a complete non-PII staffing plan saved by plan_staffing or save_staffing_plan for 30 days
• 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
• 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
• 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
• 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

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need one environment variable: PLAN_LINK_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Tempguru's toolset — plan_staffing, save_staffing_plan, get_plan and 9 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Tempguru.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tempguru mcp server does with a few real requests.