Job booking & appointments
Create, confirm and reschedule appointments against live crew availability.
MCP Server
Field service scheduling your AI agents can call
The official Model Context Protocol server for the Crisphive API. Connect Claude, ChatGPT, Cursor or any MCP client to a live field service scheduling engine — job booking, work orders, dispatch availability, customers, catalogs, crew rosters, territories and fleet. It's a hosted remote server: nothing to install or run.
https://api.crisphive.com/mcp
Hosted remote server over Streamable HTTP — OAuth or a sandbox API key, nothing to install.
What agents can do
43 scheduling tools behind one URL
43 tools over the Crisphive Developer API /v1, grouped by what your agent is trying to do — every one respects the same hard constraints as the live board.
Work-order tracking
Open, update and track work orders end-to-end, with status that mirrors the dispatch board.
Dispatch & availability
Ask the live dispatch and scheduling engine who can take a job, and when.
Customer (CRM) sync
Sync customer records so bookings land on the right account with the right history.
Service catalogs
Browse services, durations and pricing your agent can quote from.
Crews & rosters
Technician and crew rosters with the skills and certifications that drive matching.
Service territories
Geographic service territories, applied as scheduling constraints — not suggestions.
Fleet
Vehicle capabilities and fleet data that shape which crew can take which job.
Quickstart
Connect your client in one line
Every client takes the same URL. OAuth signs you in as the business owner; a sandbox API key (chsk_test_…) gives an isolated test environment that's safe to experiment in.
claude.ai / Claude Desktop (OAuth)
Settings → Connectors → Add custom connector, paste the server URL, then sign in as the Crisphive business owner when the consent screen opens.
Claude Code
claude mcp add --transport http crisphive \ https://api.crisphive.com/mcp
Cursor — .cursor/mcp.json
{
"mcpServers": {
"crisphive": { "url": "https://api.crisphive.com/mcp" }
}
}Other MCP clients
{
"mcpServers": {
"crisphive": {
"url": "https://api.crisphive.com/mcp",
"headers": { "Authorization": "Bearer chsk_test_YOUR_KEY" }
}
}
}The full client table (ChatGPT, Gemini CLI, Windsurf, Cline, Zed, LM Studio) lives in the GitHub README and the developer docs.
MCP server — quick answers
What is the Crisphive MCP server?
It's the official Model Context Protocol server for the Crisphive API — a hosted remote server at https://api.crisphive.com/mcp that gives AI agents 43 tools for job booking, work orders, dispatch availability, customers, service catalogs, crew rosters, service territories and fleet. There is nothing to install or run.
How do I connect Claude to Crisphive?
On claude.ai or Claude Desktop, go to Settings → Connectors → Add custom connector and paste https://api.crisphive.com/mcp — you'll sign in as the Crisphive business owner via OAuth. In Claude Code, run: claude mcp add --transport http crisphive https://api.crisphive.com/mcp
Does the MCP server cost extra?
No. MCP access is included on every business plan and on the free developer sandbox. MCP calls, cascades, reschedules and reads are never billed — billing counts live jobs only.
Which MCP clients are supported?
Any client that supports remote MCP servers over Streamable HTTP — claude.ai, Claude Desktop, Claude Code, ChatGPT, Gemini CLI, Cursor, VS Code, Windsurf, Cline, Zed and LM Studio among others. Clients that only speak stdio can bridge with mcp-remote.
Is this the same as Crisp's MCP server?
No. Crisphive's MCP server exposes field service scheduling tools — dispatch, routing, crew scheduling and work orders — and is built by WicWac Inc. in Ottawa, Canada. It is unrelated to Crisp (the customer-support messaging platform) and Krisp (the noise-cancellation app).