Crisphive

MCP server + REST API

Talk to your schedule. Get deterministic answers.

Crisphive is an MCP server and REST API that lets Claude, ChatGPT or your own code run constraint-based scheduling for field ops fleets. Your assistant interprets the request; Crisphive's deterministic solver computes the cascade — dependencies, travel time, supply runs and breaks included — in under 3 seconds.

REST API Integrate directly with the scheduling engine.docs.crisphive.com
Shared endpointhttps://api.crisphive.com/mcpone endpoint · both assistants

Crisphive is listed in the Claude connectors directory.

01ConnectAdd Crisphive from the Claude connectors directory and authorize with OAuth.
02Ask in plain language“What breaks if truck 2 goes down at noon?” No syntax, no query language.
03Review and approveCrisphive's solver computes the cascade; Claude presents the plan and trade-offs for your approval.

Read the full Claude guide

Example promptsCopy link to this sectionLink copied

Ask it like a dispatcher

These prompts work verbatim in Claude or ChatGPT — the assistant passes them to the same solver. Click to copy.

MCP toolsCopy link to this sectionLink copied

Tool reference

What the assistant can call. Five of the 43 tools — the live manifest is served at the endpoint.

getTechnicianScheduleRead the current schedule for a day, truck, or technician.All priorities
createJobRequestAdd a job with service window, duration, and priority.Classified P0–P3 on insert
previewEmergencyReschedulePreview the full downstream re-flow of a change without committing.P0/P1 pre-emption rules applied
getJobRequestTimelineReturn the dependency chain behind any moved job.Shows which priority displaced it
listMatchingSlotsList the slots that satisfy every hard constraint: travel, mobilization, supply runs, breaks.

Determinism & latencyCopy link to this sectionLink copied

Same input, same schedule, every time.

A constraint solver — not a language model — recomputes the full dependency graph on every change: travel time, mobilization and demobilization, supply runs, and breaks as hard constraints. Cascade reschedules return in under 3 seconds for fleets of 10+ technicians.

cascade computed in 2.1s · 14 jobs re-sequenced · 0 SLA violations

SecurityCopy link to this sectionLink copied

Security & privacy

The same OAuth scope model applies whether the client is Claude, ChatGPT, or your own code.

OAuth scopes
  • job_viewRead jobs, timelines, booking windows, schedules
  • job_createBook a job
  • job_manageQuote, confirm, move, re-prioritise, emergency reschedule
  • customers_viewRead customers
  • customers_manageCreate, update, delete customers
  • team_viewRead the technician roster
  • team_manageCreate, update, delete technicians and their relations
  • fleet_viewRead vehicles
  • settings_viewRead the job-type, skill and service-area catalogs
Writes are proposals. Nothing commits to the live schedule without dispatcher approval.
Data touchedJob records, technician availability, service windows, and constraint definitions in your Crisphive tenant — only within the scopes you grant.
Data not touchedYour conversation history, payment data, and customer records beyond service addresses. Nothing is used to train models.

Authorizing a connection with no scopes grants FULL access to everything the business can do — an empty scope list is not the cautious choice. Grant only the scopes the assistant needs.

Details in our Privacy Policy.

Does Crisphive work with Claude?
Yes. Crisphive is in the Claude connectors directory — connect it in one click, authorize with OAuth, and ask scheduling questions in plain language.
Does Crisphive work with ChatGPT?
Yes. Install the Crisphive app from the ChatGPT apps directory. The same MCP server serves both assistants.
Is the scheduling done by AI?
No. The assistant interprets your request; Crisphive's deterministic constraint solver computes the schedule. Same input, same schedule, every time.
What is the Crisphive MCP endpoint?
https://api.crisphive.com/mcp — Streamable HTTP with OAuth 2.1 or a sandbox API key. It serves Claude, ChatGPT and any MCP-compatible client.
Do I need a paid Claude or ChatGPT plan?
Connector support depends on your assistant's plan. Crisphive itself is licensed per fleet, not per assistant — and MCP calls are never billed.
Can the assistant reschedule jobs without approval?
No. Every mutating flow is a preview/commit pair — the assistant shows the proposed cascade and nothing is committed until a dispatcher approves it.
What data does the connector access?
Job, technician and schedule data within the OAuth scopes you grant. It never reads your conversation history, and customer data stays in your Crisphive tenant.
Is there an API if I don't use an AI assistant?
Yes. The same deterministic solver is available as a REST API — full reference at docs.crisphive.com.
Is this the same as Crisp's MCP server?
No. Crisphive's MCP server exposes field ops 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).

Shadow Schedule Audit

See your own week, re-solved.

Send us one real day of jobs. Within 48 hours you get it back re-solved by Crisphive — recovered drive hours, jobs that would have fit, and the revenue on the table.

Book a Shadow Schedule Audit