get_rate_benchmark — TempGuru Event Staffing MCP Tool Read-only
get_rate_benchmark
(get rate benchmark) is one of 12 tools on the
TempGuru Event Staffing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_rate_benchmark from your client
- Claude Code TempGuru Event Staffing get_rate_benchmark run in your project directory
- Claude Desktop TempGuru Event Staffing get_rate_benchmark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TempGuru Event Staffing get_rate_benchmark ~/.cursor/mcp.json
- VS Code TempGuru Event Staffing get_rate_benchmark .vscode/mcp.json
- Zed TempGuru Event Staffing get_rate_benchmark ~/.config/zed/settings.json
- Windsurf TempGuru Event Staffing get_rate_benchmark ~/.codeium/windsurf/mcp_config.json
- Cline TempGuru Event Staffing get_rate_benchmark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TempGuru Event Staffing get_rate_benchmark ~/.gemini/settings.json
- Grok TempGuru Event Staffing get_rate_benchmark .mcp.json (in your project root)
- ChatGPT TempGuru Event Staffing get_rate_benchmark Settings → Connectors → Advanced → Developer mode
- Claude.ai TempGuru Event Staffing get_rate_benchmark Settings → Connectors → Add custom connector
- LangChain TempGuru Event Staffing get_rate_benchmark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http event-staffing https://mcp.tempguru.co/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.