Talk to your schedule. Claude asks. Crisphive answers — deterministically.
The Crisphive connector lets Claude read and act on your live field service schedule — book jobs, check availability and reschedule around emergencies in plain language. Claude interprets what you ask; Crisphive's deterministic solver computes every change in under 3 seconds.
https://api.crisphive.com/mcp
Hosted remote server over Streamable HTTP — OAuth or a sandbox API key, nothing to install.
Add the Crisphive connector in Claude's settings and sign in with OAuth as the business owner — hosted remote server, nothing to install or run.
2
Ask in plain language
"Insert an emergency P0 job at 2pm and show me what cascades." Claude turns your intent into tool calls against your live schedule.
3
The solver computes, Claude explains
Crisphive's deterministic solver computes the cascade — travel, skills, breaks and SLAs as hard constraints — and Claude explains the plan and its trade-offs before anything is committed.
Real prompts against a live schedule. The same ask sounds different from a dispatcher, a developer and an owner — Claude understands all three. Pick your voice and copy.
Try these first
Paste one into Claude right after connecting — the same three prompts as the directory listing.
1
Schedule a 2-hour HVAC job at 145 Laurier Ave W tomorrow for Marie Tremblay, 613-555-0142.
2
Emergency plumbing job now at 99 Bank St for David Okafor (613-555-0198) — show me what gets rescheduled.
3
Outline my day tomorrow and flag anything at risk.
More prompts, in your voice
Emergency insertion
Insert an emergency P0 job right now at 99 Bank Street for David Okafor (613-555-0198) — burst pipe, needs a licensed plumber — and show me what gets rescheduled to make room.
Insert a P0 job now at 99 Bank St, customer=David Okafor, phone=613-555-0198, skill=PLUMBER_LICENSED. Run cascade reschedule and return the dual plan: jobs moved, new ETAs, and total SLA impact.
David Okafor (613-555-0198) has a burst pipe emergency at 99 Bank Street. Get a licensed plumber there now and tell me which customers get bumped and how it affects today's commitments.
Dispatch & availability, job booking, work orders — returns the dual plan with every cascaded move for approval.
Availability discovery
Find a 3-hour window in my work week when I can go on a bike ride with my wife without putting any jobs at risk.
Query my week for a contiguous 3h personal block that keeps all jobs feasible — no SLA breaches, no cascade required. Return candidate windows ranked by schedule slack.
When this week can I go on a bike ride with my wife without anything on the schedule slipping?
Dispatch & availability — ranks free windows by schedule slack; nothing on the board moves.
Job creation
Schedule a 2-hour HVAC maintenance job at 145 Laurier Ave W tomorrow afternoon for Marie Tremblay (613-555-0142) and assign the closest available technician.
Create a job: 2h duration, location 145 Laurier Ave W, skill=HVAC_MAINT, window=tomorrow 12:00–17:00, customer=Marie Tremblay, phone=613-555-0142. Assign nearest qualified tech and return the placement rationale.
Book a 2-hour HVAC maintenance visit tomorrow afternoon at 145 Laurier Ave W for Marie Tremblay, 613-555-0142, with whoever can get there with the least drive time.
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.
Job booking & appointments
Create, confirm and reschedule appointments against live crew availability.
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.
Claude never invents your schedule. Every booking, cascade and reschedule is computed by Crisphive's constraint solver — the same deterministic engine that runs the live dispatch board. Ask the same question twice and you get the same plan twice: the language model interprets, the solver decides.
The path of one request — the language model stays at the edges; the solver owns the schedule.
<3sto compute a full cascade reschedule
43scheduling tools behind one URL
0hallucinated schedules — plans come from the solver, not the LLM
Cascade reschedules solve in under 3 seconds, measured on a 20-location, 3-vehicle Ottawa fleet simulation with mobilization, travel time, supply runs and breaks as hard constraints.
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)
Fastest path: open the Crisphive listing in the connectors directory and connect in one click. Or add it by hand — 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
Least access, explicit approval — the connector can only see what the tools expose.
OAuth as the business owner
Connecting signs you in through OAuth — no API keys pasted into chat. Revoke access anytime from Claude's connector settings or your Crisphive account.
Scheduling data only
Tools cover jobs, work orders, customers, crews, catalogs, territories and fleet. Billing and payment data are not exposed to the connector.
Plans before changes
Anything that moves existing work returns as a reviewable plan — jobs moved, new ETAs, SLA impact — and commits only after you approve.
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).
Is the scheduling done by AI?
No — and that's the point. Claude interprets what you ask; the schedule itself is computed by Crisphive's deterministic constraint solver. Same input, same schedule, every time — a language model never places, moves or invents a job.
Can Claude reschedule jobs without my approval?
No. Changes that touch existing work come back as a plan first: Claude shows which jobs move, the new ETAs and the SLA impact, and nothing is committed until you approve it.
What data does the connector access?
Only your Crisphive scheduling data, through OAuth as the business owner: jobs, work orders, customers, crews, service catalogs, territories and fleet. Billing and payment data are not exposed, and a sandbox API key keeps experiments in an isolated test environment.
Your schedule, audited in 48 hours
Send us one real day from your dispatch board. We rebuild it with the same deterministic solver behind this connector and show you the billable hours you left on the table.
