crisphive/crisphive-mcp

The official MCP (Model Context Protocol) server for the
Crisphive API — **agentic AI scheduling
infrastructure for field operations**.
Lets AI agents — Claude, ChatGPT, Gemini, Cursor or any MCP client — match
schedules between customers and businesses and route crews to jobs by
**location, skills, and real-time availability**: **job booking & appointment
scheduling**, **work-order tracking**, availability from a live **dispatch &
scheduling engine**, **customer (CRM) sync**, service catalogs,
**technician & crew rosters**, geographic **service territories** and **fleet**
— for trades and home services such as HVAC, plumbing, electrical, cleaning,
appliance repair and property maintenance. Scheduling is **constraint-based on
a deterministic solver**: the agent handles the conversation, the solver makes
the decision — same inputs, same plan, never an LLM guessing at a calendar.
Hosted remote server; nothing to
install or run (this repository holds the documentation and registry manifest).
Try these first
Connect (a chsk_test_ sandbox key is enough), then paste any of these straight
into your agent:
1. **Job creation** — *"Schedule a 2-hour HVAC job at 145 Laurier Ave W
tomorrow for Marie Tremblay, 613-555-0142."*
(createCustomer → listJobRequestBookingWindows → createJobRequest →
quoteJobRequest → confirmJobRequest)
2. **Emergency insertion** — *"Emergency plumbing job now at 99 Bank St for
David Okafor (613-555-0198) — show me what gets rescheduled."*
(listEmergencyCandidates → previewEmergencyReschedule →
commitEmergencyReschedule)
3. **Daily outline** — *"Outline my day tomorrow and flag anything at risk."*
(listJobRequests → getTechnicianSchedule)
. **Sick call** — *"Dmitri called in sick for tomorrow — re-staff his jobs
without moving any customer's appointment."*
(previewAbsenceResolve → commitAbsenceResolve)
The same prompts appear on every Crisphive listing and docs page, so what you
see here is exactly the first-run experience everywhere.
→ Full overview, tool table and one-click connect: https://crisphive.com/claude
Requirements
Any MCP client that supports remote servers over Streamable HTTP —
claude.ai, Claude Desktop, Claude Code, ChatGPT, Gemini CLI, Cursor, VS Code,
Windsurf, Cline, Zed, LM Studio, ….
Installation
claude.ai / Claude Desktop (OAuth — no key needed)
**Settings → Connectors → Add custom connector**, paste
https://api.crisphive.com/mcp. Sign in as the Crisphive business owner when
the consent screen opens. *(Custom connectors require a Claude plan that
supports them.)*
Claude Code
Cursor
Or add to .cursor/mcp.json:
VS Code
ChatGPT
**Settings → Connectors** (developer mode) → add MCP server with URL
https://api.crisphive.com/mcp (OAuth).
Gemini CLI
Add to ~/.gemini/settings.json (note: Gemini CLI uses httpUrl for
Streamable HTTP servers):
Other MCP clients (Windsurf, Cline, Zed, LM Studio, …)
Most clients accept the standard remote-server shape:
Only the URL field name varies in a few clients:
| Client | Config file | URL field |
|---|---|---|
| Cline / Roo Code | cline_mcp_settings.json | url |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | serverUrl |
| Gemini CLI | ~/.gemini/settings.json | httpUrl |
| Zed | settings.json → context_servers | url |
Clients that only speak stdio can bridge with
mcp-remote:
Local server (npm — @crisphive/mcp)
This repository also ships a thin **local stdio server**: the same 66 tools
(same names, same schemas — generated from the same /v1 OpenAPI spec as the
hosted endpoint), where each call is an HTTPS request to the Crisphive API
with your key. No business logic runs locally.
Environment variables:
| Variable | Required | Meaning |
|---|---|---|
| CRISPHIVE_API_KEY | for tool calls | chsk_live_… = production data, chsk_test_… = isolated sandbox. Create keys in the dashboard (Developers → API keys). |