Crisphive MCP is the official MCP (Model Context Protocol) server for the Crisphive API, positioned as agentic AI dispatch infrastructure for field service operations. It enables AI agents (such as Claude, ChatGPT, Gemini, Cursor, or any MCP client) to match schedules and dispatch crews between customers and businesses based on location, skills, and real-time availability.
Key capabilities
- Job booking and appointment scheduling
- Work order tracking
- Availability queries from the real-time dispatch and scheduling engine
- Customer (CRM) sync
- Service catalog
- Technician and crew roster
- Geographic service areas
- Fleet management Suitable for trades and home service industries such as HVAC, plumbing, electrical, cleaning, appliance repair, and property maintenance.
Scheduling mechanism Scheduling is based on constraint computation by a deterministic solver: the agent handles the conversation, the solver makes the decisions—same input, same plan, never letting the LLM guess at the calendar.
How to use This service is a hosted remote server and requires no installation or running (this repository contains only documentation and a registration manifest). It supports any MCP client that supports Streamable HTTP remote servers, including claude.ai, Claude Desktop, Claude Code, ChatGPT, Gemini CLI, Cursor, VS Code, Windsurf, Cline, Zed, LM Studio, and others.
Connection examples:
- claude.ai / Claude Desktop (OAuth, no key required): Settings → Connectors → Add custom connector, paste https://api.crisphive.com/mcp，在同意屏幕以 Sign in as a Crisphive business owner.
- Cursor: add to .cursor/mcp.json.
- Gemini CLI: add to ~/.gemini/settings.json (note the use of httpUrl).
- Other MCP clients: most accept standard remote server configuration.
- Clients that only support stdio can be bridged via mcp-remote.
- Local server (npm @crisphive/mcp): provides the same 66 tools (same names and schemas, generated from the same /v1 OpenAPI specification), makes an HTTPS request to the Crisphive API on each call, and runs no business logic locally.
Authentication and keys Each request is authenticated using a secret API key sent as a bearer token. Keys are created from the Crisphive business dashboard. The key prefix selects the data environment: chsk_live_… for production data, chsk_test_… for sandbox data. Keys should be loaded from environment variables and never committed. Keys expire; the lifetime is chosen at creation (default 30 days, maximum 365 days) and cannot be extended. Renewal requires creating a second key, switching the agent over, and then revoking the first. Expired keys return API_KEY_EXPIRED, which is distinguished from API_KEY_INVALID. Crisphive sends an email to the business owner 7 days before key expiration (14 days for OAuth connections). The MCP endpoint also supports OAuth 2.1, allowing business owners to authorize agents on a consent screen without handling keys.
Tools and workflows There are 66 tools in total, corresponding one-to-one with public /v1 API operations, with the same names as the SDK methods (such as listCustomers, createJobRequest), generated from the same OpenAPI specification, ensuring REST and MCP do not drift. Typical agent workflows include: job creation (createCustomer → listJobRequestBookingWindows → createJobRequest → quoteJobRequest → confirmJobRequest), emergency insertion (listEmergencyCandidates → previewEmergencyReschedule → commitEmergencyReschedule), daily overview (listJobRequests → getTechnicianSchedule), sick leave handling (previewAbsenceResolve → commitAbsenceResolve). List tools support page/limit and return a meta object. Create/submit tools accept an idempotency_key parameter to avoid duplicates. Each tool returns a Crisphive response envelope, with error_code 0 indicating success and a stable string on failure.
Applicable scenarios Suitable for scheduling, dispatching, work orders, CRM, and fleet management in field service and home service industries such as HVAC, plumbing, electrical, cleaning, appliance repair, and property maintenance.
Limitations The documentation does not provide specific fees, prices, platform compatibility details, or performance guarantees. Key expiration cannot be extended and requires manual rotation. The local package is only for stdio clients and self-hosted scenarios.
