TempGuru Event Staffing
OfficialRelated Servers
Alternatives to TempGuru Event Staffing
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityBmaintenanceMCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.-- FlicenseNot gradedqualityDmaintenanceFull-coverage, read-only MCP server for the Teamtailor recruitment API. Exposes 18 tools covering candidates, jobs, applications, offers, stages, departments, locations, users, and activities with strict input validation.-
- AlicenseAqualityBmaintenanceMCP server providing 12 tools for Seattle-area home remodeling: real-time cost estimation across 8 project types, contractor business info, project portfolio, blog content, and quote submission. Connects via Streamable HTTP — no auth required.36MIT
- AlicenseAqualityAmaintenanceUnofficial Thumbtack MCP server for searching local service professionals and reading their profiles, ratings, reviews, and credentials. Read-only and anonymous.6203 npmMIT
- AlicenseAqualityBmaintenanceProduction-ready MCP server for Greenhouse ATS with 175 tools for recruiting teams — manage candidates, applications, jobs, interviews, and hiring pipelines. Role-based profiles (full/recruiter/read-only), composite workflow tools for pipeline views, analytics, candidate search, and bulk operations.18766 PyPI5MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that answers questions about turva.dev from its published data. Five tools return JSON: the service catalog with prices, contact and operator details, engagement principles and dated agent-readiness and security evidence with verification links. Connect over Streamable HTTP. You need no API key. The server does not scan other websites or run audits.MIT
TDQS
Scored across 12 tools
Most tools have crisply separated purposes and the descriptions actively cross-reference each other (get_rate_benchmark vs get_role_pricing vs plan_staffing, check_availability vs get_cities). The only real overlap risk is plan_staffing vs save_staffing_plan, which both recompute the same rate/total math; that boundary is heavily guarded with explicit 'never call when plan_id returned' rules but still requires careful reading.
A predictable pattern holds: get_* for reads (get_plan, get_cities, get_roles, get_policies, get_role_pricing), action verbs for writes (plan_staffing, save_staffing_plan, check_availability, request_quote). Minor deviation: noun placement flips between plan_staffing and save_staffing_plan, and get_compliance_by_state is longer/qualifier-style, but nothing is ambiguous.
12 tools is well inside the sweet spot and each maps to a distinct buyer question or lifecycle step (discovery, pricing, compliance, availability, plan persistence, quote handoff). No tool feels redundant filler or a missing sibling of another.
The surface covers the full non-contact lifecycle: find roles/markets, price, check lead time, check compliance and policies, build/save/restore a plan, and hand off to a quote form with status lookup. Gaps are deliberate (no order reservation or booking, quote status is a 'received/queued only' v1 stub, no cancellation tool beyond get_policies), which an agent can work around via the coordinator handoff.