Crisphive MCP

What the Crisphive MCP MCP server does

The Crisphive MCP MCP server exposes the Crisphive field-operations API to MCP-compatible agents. It supports workflows for trades and home-service businesses, including HVAC, plumbing, electrical, cleaning, appliance repair, and property maintenance.

Agents can create and manage customers, submit job requests, inspect booking windows, follow request timelines, and access service and skill catalogs. The API also covers technician and crew rosters, geographic service areas, dispatch and scheduling data, and fleet-related operations. The available interface contains 66 tools generated from the public /v1 OpenAPI specification.

Scheduling decisions are handled by Crisphive's deterministic solver. The agent can gather requirements and present options, while the scheduling engine evaluates constraints such as job location, required skills, and current availability.

How it works

The hosted endpoint is available at https://api.crisphive.com/mcp and uses Streamable HTTP. A compatible client sends MCP requests to that endpoint, where they are authenticated and passed to the Crisphive API. The hosted option does not require installing or running a local process.

Authentication can use OAuth 2.1 for supported end-user connectors. A business owner authorizes the connection through a consent flow, so the agent does not need to handle a secret key. API-key authentication is also supported through a bearer token. Keys beginning with chsk_test_ use an isolated sandbox, while chsk_live_ addresses production data.

Setup and configuration

For a remote connection, configure the MCP URL in the client. Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT, Gemini CLI, Windsurf, Cline, Zed, and LM Studio are named as compatible options in the documentation. Clients that only support stdio can use mcp-remote as a bridge.

The npm package @crisphive/mcp provides a local stdio server. It contains the same tool names and schemas as the hosted endpoint, but tool calls are forwarded over HTTPS; business logic does not run locally. Set CRISPHIVE_API_KEY for tool calls. CRISPHIVE_BASE_URL can override the default API origin, which is https://api.crisphive.com.

API keys have configured expiration dates and should be loaded from the environment rather than committed to source control. The documentation recommends tracking expiration and rotating keys before they expire.

Tools and capabilities

The documented tool groups include:

• Customer CRUD and CRM synchronization.
• Job-request creation, listing, inspection, timelines, booking windows, and change history.
• Read access to job types, skills, skill categories, and service areas.
• Catalog-management operations for importing or updating job types and skill categories.
• Scheduling and dispatch workflows, including emergency rescheduling and absence resolution.
• Technician schedule and crew-related operations.

Example workflows include creating a customer and booking a job, previewing the effect of an emergency insertion before committing it, outlining a technician's day, and re-staffing jobs after an absence without moving customer appointments.

Limitations and notes

The remote endpoint requires an MCP client that supports Streamable HTTP. A stdio-only client needs the mcp-remote bridge or the local npm package. OAuth is available for supported connectors, while other configurations require a Crisphive API key.

The Crisphive MCP MCP server is an interface to the Crisphive API, not a locally running scheduling engine. The local package still sends each operation to Crisphive over HTTPS. Production keys operate on live data, so sandbox keys are more appropriate for initial testing.

Tool definitions are generated from the /v1 specification. Changes to the API specification can therefore affect the generated registry and the corresponding MCP surface.