# TempGuru Event Staffing MCP server

> Plan W-2 event staffing with role rates, lead times and state compliance flags across US and Canadian markets.

- Listing: https://mcp.tc/i/tempguru-event-staffing
- Connect: use the server's own URL `https://mcp.tempguru.co/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Utilities](https://mcp.tc/c/utilities)
- Vendor: TempGuru
- Homepage: <https://tempguru.co/ai-agents>
- Repository: <https://github.com/tempguru-co/tempguru-mcp>
- Package: npm `tempguru-mcp`

## About

Connects to TempGuru's event staffing data for conventions, trade shows, festivals and brand activations in the US and Canada. You can build a staffing plan from city, date, roles and headcount, look up all-inclusive W-2 hourly rate ranges, check lead-time guidance, read state compliance summaries and booking policies, and get the Event Staffing Rate Index. All totals are planning estimates, and a TempGuru coordinator confirms availability per order.

Runs as a hosted streamable HTTP endpoint at https://mcp.tempguru.co/mcp, or locally with npx -y tempguru-mcp. No sign-in or API key is needed. Plans can be saved for 30 days without contact details. The quote tool returns a prefilled TempGuru form URL that the buyer opens and submits personally.

## What it can do

- Build an event staffing plan with per-role rate math and estimated totals
- Look up hourly rate ranges for a role in a city
- Get lead-time guidance for an event date and market
- Read state minimum wage, overtime and compliance notes
- Browse staffing roles and configured markets
- Read booking and procurement policies
- Get the Event Staffing Rate Index benchmark
- Restore a saved plan and get a prefilled quote form link

## Tools (12)

- `plan_staffing`: Build a staffing plan from city, date, roles and headcount with rates, lead time and compliance…
- `save_staffing_plan`: Save a complete non-contact plan for 30 days when plan\_staffing returned no plan\_id.
- `get_plan`: Restore a saved non-PII staffing plan by its 12-character plan\_id. (read-only)
- `get_cities`: List configured markets by state, tier or country, or match one city. (read-only)
- `get_roles`: List event staffing roles with descriptions and skill tiers. (read-only)
- `get_lead_time_guidance`: Return tier-based lead-time guidance for an event date and configured market. (read-only)
- `get_role_pricing`: Get the all-inclusive hourly rate range for a role in a city. (read-only)
- `get_compliance_by_state`: Get minimum wage, overtime rules and quirks for a US state. (read-only)
- `get_policies`: Get published booking and procurement policies and any public offer. (read-only)
- `get_rate_benchmark`: Get the Event Staffing Rate Index with national ranges and a citation line. (read-only)
- `prepare_quote_form`: Use only after the buyer reviews a staffing plan and asks to proceed. (read-only)
- `get_quote_request_status`: Check whether a TempGuru quote request reference was received by the CRM or durably queued. (read-only)

## Example prompts

- "Plan staffing for a 3-day trade show in Dallas with 10 brand ambassadors and 4 registration staff"
- "What does it cost to hire brand ambassadors in Boston?"
- "What are the overtime rules for event staff in California?"
- "Is Nashville in the TempGuru market catalog, and what is the usual lead time?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http tempguru-event-staffing https://mcp.tempguru.co/mcp
```

2. Start Claude Code and type `/mcp`. **tempguru-event-staffing** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **TempGuru Event Staffing** and paste this URL:

```url
https://mcp.tempguru.co/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=TempGuru%20Event%20Staffing&connectorUrl=https%3A%2F%2Fmcp.tempguru.co%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.tempguru.co/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.tempguru.co/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=tempguru-event-staffing&config=eyJ1cmwiOiJodHRwczovL21jcC50ZW1wZ3VydS5jby9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=tempguru-event-staffing&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.tempguru.co%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"tempguru-event-staffing","type":"http","url":"https://mcp.tempguru.co/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "tempguru-event-staffing": {
      "type": "http",
      "url": "https://mcp.tempguru.co/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "tempguru-event-staffing": {
      "serverUrl": "https://mcp.tempguru.co/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add tempguru-event-staffing --url https://mcp.tempguru.co/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.tempguru-event-staffing]
url = "https://mcp.tempguru.co/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http tempguru-event-staffing https://mcp.tempguru.co/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "tempguru-event-staffing": {
      "type": "http",
      "url": "https://mcp.tempguru.co/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.tempguru.co/mcp`.

## Recent changes

- 2026-11-11 17:52 UTC: New version 1.7.5 (was 1.7.3), reported by the server. Source: automatic check.
- 2026-11-11 17:52 UTC: 3 tools added, 3 tools removed and 5 tools changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Added: get\_lead\_time\_guidance, get\_quote\_request\_status, prepare\_quote\_form. Removed: check\_availability, get\_quote\_status, request\_quote. Changed: get\_cities, get\_plan, get\_rate\_benchmark, get\_role\_pricing, save\_staffing\_plan.
- 2026-11-02 05:48 UTC: New version 1.7.3 (was 1.7.2), reported by the server. Source: automatic check.
- 2026-11-01 23:41 UTC: 6 tools changed. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Changed: check\_availability, get\_compliance\_by\_state, get\_plan, get\_policies, plan\_staffing, save\_staffing\_plan.
- 2026-10-06 21:21 UTC: Tracking started: 12 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/tempguru-event-staffing#history (Atom feed: https://mcp.tc/i/tempguru-event-staffing/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.7.5
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-17 (reachable)
- Listed: 2026-10-05
- Updated: 2026-11-11

---
Source: https://mcp.tc/i/tempguru-event-staffing (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
