Set up Crisphive in ChatGPT
Follow these steps and Crisphive will be connected to your ChatGPT account — signed in, pointed at the right data, and tested — in about five minutes.
ChatGPT reaches other services through apps and connectors. Crisphive’s connector speaks MCP (Model Context Protocol), the open format ChatGPT uses to discover and call another service’s actions. You do not need to know MCP to set it up. For what ChatGPT can do once connected, see Crisphive for ChatGPT; for the full tool list, see the MCP reference.
If you find Crisphive in ChatGPT’s apps directory, Option A is quickest. Otherwise connect in developer mode (Option B) — same server, same sign-in, same tools.
Choose how to connect
| Option | Use it when | You need |
|---|---|---|
| A — Crisphive app from the apps directory | Crisphive is listed in your ChatGPT apps directory. | A ChatGPT plan with apps; your workspace admin may have to allow it. |
| B — Custom connector in developer mode | Crisphive is not in your apps directory, or your workspace only allows custom connectors. | A ChatGPT plan where developer mode is available. |
Before you start
- A Crisphive account you can sign in to at
https://crisphive.com/app. - Know who should approve. ChatGPT always acts as the person who clicks Approve, with that person’s current Crisphive role. For dispatch work, an Owner or Booking Coordinator; see Which role to connect with.
- A ChatGPT plan that allows it (see the table above). On Business and Enterprise workspaces, your ChatGPT admin may control apps, connectors and developer mode.
- About 5 minutes. No API key and nothing to install.
- Decide Live or Rehearsal first. Rehearsal is your business’s sandbox: isolated test data — nothing there reaches a real customer. The mode is fixed when you approve; see Step 3.
Option A — Add the Crisphive app
In ChatGPT open the apps directory and search for Crisphive. If it does not appear, use Option B.
Open the Crisphive app and click its connect button. ChatGPT opens the Crisphive sign-in page — continue at Step 2.
Option B — Add a custom connector in developer mode
ChatGPT moves these settings between versions, so the steps below say what to do rather than which menu to click. OpenAI keeps the current menu path in its own guide: ChatGPT developer mode.
In ChatGPT’s settings, find Developer mode and switch it on. If you cannot find it, your plan or your workspace admin does not allow it — see Troubleshooting.
With developer mode on, ChatGPT shows an option to create your own app (connector) from an MCP server. Open it.
Name: Crisphive. Description (if asked): Book and dispatch field jobs in Crisphive. Server URL: https://api.crisphive.com/mcp. Authentication: OAuth. Leave any client ID and client secret fields empty — ChatGPT registers itself with Crisphive automatically. If ChatGPT asks you to confirm that you trust the server, confirm.
ChatGPT connects to Crisphive, lists the Crisphive tools and opens the Crisphive sign-in page — continue at Step 2.
Step 2 — Sign in to Crisphive and approve
Both options end on the same Crisphive page. This is OAuth: a standard way to let ChatGPT act for you in Crisphive without you copying a password or key.
The page shows Checking your session…. If you are signed out, sign in with your usual email or phone code; you come back to the consent page afterwards.
The page is titled Authorize followed by the name ChatGPT registered, and shows This will allow … to Access and manage the business data made available to this integration.
Crisphive shows Taking you back to … and returns you to ChatGPT, where Crisphive now shows as connected. Deny shares nothing.
Step 1 of 2Read the request: ChatGPT wants to access your Crisphive business and will be able to access and manage the business data made available to this integration.
All steps
- Read the request: ChatGPT wants to access your Crisphive business and will be able to access and manage the business data made available to this integration.
- Click Approve. Crisphive sends you back to ChatGPT, now connected.
Which role to connect with
ChatGPT can do exactly what the approving person can do in the Crisphive dashboard, re-checked on every request. Change their role and ChatGPT’s access follows; remove or suspend them and the connection stops at once.
| Approved by | Result |
|---|---|
| Owner | Full access to the business, as in the dashboard. |
| Booking Coordinator | The schedule and customers — the usual choice for dispatch. |
| Administrator | Rehearsal (sandbox) only by default; nothing in live data until the Owner grants modules in the role matrix. |
| Technician | Can read the job type list, but not the business job board, job details, matching views or other technicians’ schedules (403 FORBIDDEN). |
Step 3 — Point it at Live or Rehearsal data
Crisphive keeps a Live copy of your business (real customers and jobs) and a Rehearsal copy (the sandbox: isolated test data that never reaches a real customer). ChatGPT has no setting for this: the connection uses the mode your Crisphive dashboard was in when you clicked Approve, and keeps it.
Before Step 2, open https://crisphive.com/app, click Rehearsal in the Rehearsal | Live switch in the left sidebar, and confirm with Switch.
Make sure the Rehearsal | Live switch shows Live when you approve.
Disconnect Crisphive in ChatGPT, switch the dashboard, then connect and approve again.
Ready-to-copy settings
Name: Crisphive MCP server URL: https://api.crisphive.com/mcp Authentication: OAuth — leave client ID and client secret empty Smaller tool sets (optional, same sign-in, same permissions): https://api.crisphive.com/mcp/dispatch jobs, moves, emergencies, sick calls, roster reads https://api.crisphive.com/mcp/crm customers and their bookings
Step 4 — Turn Crisphive on in a chat and confirm writes
Start a new chat and select Crisphive from the composer’s tools menu. A developer-mode connector only works in chats where you enable it.
Before ChatGPT runs a Crisphive tool that changes data, it shows the tool and its inputs and asks you to confirm. Check the date, time, customer and technician, then confirm or cancel.
Crisphive labels every tool so ChatGPT knows when to ask: read-only for lookups; destructive for anything that overwrites, reschedules or deletes (updates, deletes, and the three “commit” tools); open world for every write, because a write can email or text a customer or technician, send a webhook, or update a connected calendar. Matching reads are also marked open world because they price travel through Google Maps — they still change nothing.
Step 5 — Test the connection
Do this on a Rehearsal connection. The contact details are fictional; Crisphive never messages 555-01xx numbers or @example.com addresses.
Ask: “List my Crisphive job types and technicians.” Expected: your Rehearsal job types (at least General) and technicians.
Ask: “Book a General job for Alex Martin, +1 613 555 0177, alex.martin@example.com, at 145 Laurier Avenue West, Ottawa, ON K1P 5J3, CA, next Monday at 10:00, and confirm it.” Confirm the tool calls ChatGPT shows you.
Success: the job is confirmed with a reference code such as REQ-CA-…, a time and an assigned technician. “Saved but not confirmed” means no technician fits that time; the job waits in the coordinator queue.
In https://crisphive.com/app (Rehearsal), the job is on the board on Monday at 10:00 and Alex Martin is in Customers. Under Settings → Developer → MCP connections, ChatGPT is listed in Connected AI apps.
Keep the connection alive
- While you use it, ChatGPT refreshes its access by itself. After 30 days without use, the connection lapses.
- Whatever the use, it ends 90 days after approval. Change that with Set lifetime on ChatGPT’s row in Settings → Developer → MCP connections (1–365 days, counted from the original approval).
- You are warned: Owners and Administrators are emailed 14 days before it ends. To renew, connect again and approve.
Disconnect ChatGPT
Open Settings → Developer → MCP connections, click Disconnect on ChatGPT’s row under Connected AI apps, then confirm. This revokes every active grant ChatGPT holds for your business, including other people’s. The list shows the dashboard’s current mode only — switch to Rehearsal to find a Rehearsal connection.
In ChatGPT’s settings, open the list of apps and connectors, open Crisphive, and disconnect or delete it.
An access token ChatGPT already holds keeps working for up to one hour after a disconnect in Crisphive. Removing or suspending the member stops it on the next request.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No Developer mode switch | Your ChatGPT plan or workspace does not allow it. | Check your plan supports developer mode, ask your workspace admin, or use the Crisphive app (Option A) if it appears in the app directory. |
| Crisphive does not appear in a chat’s tools menu | The connector is not enabled for this chat, or developer mode was turned off. | Re-enable developer mode, start a new chat and select Crisphive. |
| Crisphive page says Invalid authorization request | The sign-in link was incomplete or expired. | Close the window and start the connection again from ChatGPT. |
| ChatGPT finds no customers or jobs, or the wrong ones | The connection is in the other mode (Live vs Rehearsal) than your dashboard. | Disconnect, switch the dashboard, connect and approve again. |
403 FORBIDDEN when asking about jobs or the schedule | The approving member is a Technician or lacks job management. | Have an Owner or Booking Coordinator connect. |
Approve fails with access_denied | Your membership is suspended, or the request asked for a permission your role lacks. | Ask the Owner to reactivate you or adjust your role. |
ChatGPT asks to reconnect; OAUTH_GRANT_EXPIRED | The connection reached its lifetime or was unused for 30 days. | Connect and approve again. |
Test booking “saved but not confirmed”, or JOB_REQUEST_NO_TECHNICIAN_AVAILABLE | No technician fits that exact time. | Ask for the nearest open times. Do not book the job again — it is already in the coordinator queue. |
JOB_REQUEST_QUOTE_NOT_SCHEDULABLE | No technician can take the job in any window asked for; data.reason says why. | Pick another day, or fix the cause in the dashboard (service area, working hours, skills). |
PHONE_INVALID | The phone number is not in international form. | Give it with the country code: +1 613 555 0177. |
JOB_REQUEST_INVALID_INPUT with data.means_locally | A time carried a timezone offset that disagrees with your business’s local time. | Ask for the time in your business’s local time, without an offset. |
429 | More than 240 requests a minute on this key or connection, shared with REST — about 120 MCP tool calls a minute, since each tool call also makes one REST request. | Wait a minute and retry. |
Move from Rehearsal to Live
- Disconnect the Rehearsal connection, switch the dashboard to Live, then connect and approve again — as an Owner or Booking Coordinator.
- On live data, a confirmed job notifies the customer and technician, and a committed move, emergency or sick-call plan notifies every customer whose visit changed. Read each confirmation card before you accept it.
- Note the Expires date in MCP connections (90 days by default) and renew or raise the lifetime before it.
Related guides and reference
- AI assistants overview — Claude, ChatGPT and any other MCP client
- Claude — the Crisphive connector for claude.ai, Desktop and Claude Code
- MCP server reference — every tool, the tool profiles and client setup
- Voice agents overview — the voice tool set and booking rules
- Automation platforms overview — what every automation integration shares