TempGuru MCP Server

Model Context Protocol server and public REST API for TempGuru event staffing data. Twelve tools: ten read-only tools, including a non-PII buyer handoff, plus a non-destructive planner that may save a 30-day non-PII snapshot, an explicit non-destructive save tool.

Evidence-verified public scale

The completed-shift figure counts worker-shift assignments, not unique people, workers, placements, or network size. Availability is confirmed per order.

MCP Endpoint

POST /mcp

Official dual-era HTTP transport. Preferred MCP 2026-07-28 per-request envelopes, with stateless initialize/streamable-HTTP compatibility for supported 2025-era clients. Responses use JSON or SSE as required. No authentication.

Phase A workflow

  1. Call plan_staffing first with the event city, date, roles, and headcount.
  2. If the complete plan already includes a plan_id, retain it and do not call save_staffing_plan. The planner already saved the non-PII snapshot.
  3. Call save_staffing_plan only when a complete plan has no plan_id and needs a durable 30-day artifact. The server recomputes rates and totals before saving.
  4. When the buyer asks to proceed, call request_quote with the saved plan_id, then give the buyer its form_url. The buyer enters and submits their own contact details on that form.

MCP Tools

Public REST API

Same data as the MCP tools, exposed as plain HTTP for clients that don't speak MCP. No authentication, JSON responses, CORS open. The read endpoints have a 1-hour public cache; the quote endpoint (POST /api/v1/quote-requests) is no-store and rate-limited.

Full machine-readable spec: /openapi.json · API catalog: /.well-known/api-catalog

Discovery & knowledge

Agent-readable surfaces for crawlers and clients that resolve a server without an install:

Operated by TempGuru. Docs: tempguru.co/ai-agents.