Set up Crisphive in Claude

Last updated October 4, 2026

Follow these steps and the Crisphive connector will be working in your Claude account — signed in, pointed at the right data, with sensible approvals — in about five minutes.

A connector is a link that lets Claude use another service on your behalf. Crisphive’s connector speaks MCP (Model Context Protocol), the open format Claude uses to discover and call another service’s actions. You do not need to know anything about MCP to set it up. For what Claude can do once connected, see Crisphive for Claude; for the full list of tools, see the MCP reference.

If you see Crisphive in Claude’s connector directory, connecting from there skips Step 1 — continue at Step 2. Otherwise add Crisphive by URL as a custom connector (Step 1 below); it gives exactly the same connection.

Ways to connect

Where you use Claude	How to connect	Sign-in
claude.ai (web)	Customize → Connectors → + Add → Add custom connector (this guide)	Crisphive sign-in + Approve
Claude Desktop	The same, in the Desktop app’s Customize → Connectors	Crisphive sign-in + Approve
Claude mobile apps	Connect once on claude.ai or Desktop; the connector follows your Claude account	Done on web or Desktop
Claude Code (terminal)	One command — see Claude Code	Browser sign-in, or an API key

Before you start

A Crisphive account you can sign in to at https://crisphive.com/app.
Know who should approve. The connection always acts as the person who clicks Approve, with that person’s current Crisphive role. For dispatch work that person should be an Owner or Booking Coordinator. See Which role to connect with.
Any Claude plan. Custom connectors work on Free (one connector), Pro, Max, Team and Enterprise. On Team and Enterprise an organization Owner adds the connector first.
About 5 minutes. No API key and nothing to install for claude.ai or Desktop.
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. We recommend sandbox for your first connection.

Step 1 — Add Crisphive as a custom connector

On a Claude Team or Enterprise plan, an organization Owner adds the connector once for everyone: Organization settings → Connectors → Add → Custom → Web, with the same name and URL as below. Members then open Customize → Connectors, find Crisphive and click Connect — continue at Step 2. On Free, Pro and Max you add it yourself:

Open Claude’s connectors

On claude.ai or in Claude Desktop, open Customize → Connectors.

Add a custom connector

Click + Add, then Add custom connector. If the option is missing, your Claude organization does not allow custom connectors — see Troubleshooting.

Enter the name and server URL

Name: Crisphive. Remote MCP server URL: https://api.crisphive.com/mcp. Click Continue.

Keep sign-in on

Under Authentication, choose Sign in now (or Sign in when needed). Do not choose No sign in. Leave the OAuth client setting and Request headers as they are — Claude registers itself with Crisphive automatically and no API key is needed. Click Add.

Step 1 of 4In Customize → Connectors, click + Add, then Add custom connector.

All steps

In Customize → Connectors, click + Add, then Add custom connector.
Type Crisphive as the name.
Paste https://api.crisphive.com/mcp as the remote MCP server URL, then click Continue.
Under Authentication choose Sign in now, leave the OAuth client and request headers as they are, and click Add.

Clicking Connect opens a Crisphive page in your browser. This is OAuth: a standard way to let one app act for you in another without you copying a password or key. You confirm once, Claude receives a token, and you can revoke it at any time.

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.

Check what you are approving

The page is titled Authorize Claude and reads Claude wants to access your Crisphive business. Under This will allow Claude to it shows Access and manage the business data made available to this integration.

Click Approve

Crisphive shows Taking you back to Claude… and returns you to Claude, where the connector now shows as connected. Deny shares nothing.

Step 1 of 2Read the request: Claude 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: Claude 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 returns you to Claude and the connector shows as connected.

Which role to connect with

Claude can do exactly what the approving person can do in the Crisphive dashboard, re-checked on every request. Change their role and Claude’s access changes on its next call; 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 a dispatcher’s Claude.
Administrator	Rehearsal (sandbox) only by default; in live data it can do nothing until the Owner grants modules in the role matrix.
Technician	Can read the job type list, but not the business job board, any job’s details or timeline, matching views or another technician’s schedule (`403 FORBIDDEN`). This is the role, not a setting you can widen.

Step 3 — Point it at Live or Rehearsal data

Crisphive keeps two separate copies of your business: Live (real customers, jobs and team) and Rehearsal (the sandbox: isolated test data — bookings there never reach a real customer and send no real notifications). Claude has no setting for this. The connection uses whichever mode your Crisphive dashboard was in when you clicked Approve, and keeps it.

For a Rehearsal (test) connection

Before Step 2, open https://crisphive.com/app, click Rehearsal in the Rehearsal | Live switch in the left sidebar, and confirm with Switch. Then click Connect in Claude and approve.

For a live connection

Make sure the Rehearsal | Live switch shows Live when you approve.

To switch later

Disconnect Crisphive in Claude, switch the dashboard to the other mode, then click Connect and approve again.

Ready-to-copy settings

Connector name:   Crisphive
Server URL:       https://api.crisphive.com/mcp
Authentication:   OAuth — automatic; leave client ID and client secret empty
Transport:        Streamable HTTP (Claude's default for remote connectors)

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

Use the plain /mcp URL unless you want Claude to see fewer tools. A smaller set only changes which tools Claude is shown; what it is allowed to do is still the approving person’s role.

Step 4 — Choose which tools run without asking

Every Crisphive tool tells Claude whether it only reads, whether it overwrites or removes something (updates, deletes and the three “commit” tools), and whether it can reach outside Crisphive (every write can email or text a customer or technician). Claude combines these labels with your per-tool permission settings.

Open the connector’s tools

In Customize → Connectors, open Crisphive to see each tool and its permission.

Allow reads, keep approval on writes

A safe setup: let tools starting with list, get and preview run without asking (they change nothing), and keep approval on everything that creates, updates, deletes or commits. On a live connection, never auto-approve commitEmergencyReschedule, commitJobRequestMove, commitAbsenceResolve or any delete… tool.

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. In a new chat, make sure Crisphive is switched on: click the + button at the lower left, choose Connectors and turn on Crisphive.

Ask a read-only question

In a new chat with Crisphive enabled, ask: “List my Crisphive job types and technicians.” Expected: your Rehearsal job types (at least General) and technicians. An error here means the connection itself is not working — see Troubleshooting.

Book one test job

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.” Approve the tool calls Claude shows you.

Read Claude’s answer

Success: the job is confirmed, with a reference code such as REQ-CA-…, the date and time, and the assigned technician. “Saved but not confirmed” means no technician fits that time — the job is waiting in the coordinator queue (see Troubleshooting).

Check in the dashboard

In https://crisphive.com/app, still in Rehearsal, the job is on the schedule board on Monday at 10:00 under the assigned technician, and Alex Martin is in Customers.

Check the connection record

Open Settings → Developer → MCP connections (/app/settings/developer/mcp-servers). Claude is listed under Connected AI apps with Connected, Expires and Last active dates.

Claude Desktop and mobile

Claude Desktop: add the connector in Desktop’s own Customize → Connectors, exactly as in Step 1. Sign-in from Desktop has been tested end to end on production. If you added Crisphive on claude.ai and Desktop does not show it as connected, add it again directly in Desktop — this is a Claude Desktop behaviour, not a Crisphive one.
Claude mobile apps: connectors belong to your Claude account. Connect on claude.ai or Desktop first, then use Crisphive from the mobile app.

Claude Code

# Browser sign-in (acts as you, same consent page as above)
claude mcp add --transport http crisphive https://api.crisphive.com/mcp

# Or with a sandbox API key instead of sign-in
claude mcp add --transport http crisphive https://api.crisphive.com/mcp \
  --header "Authorization: Bearer chsk_test_YOUR_KEY"

An API key is a secret password for software, created in Crisphive under Settings → Developer → API Keys; a chsk_test_ key only reaches sandbox data. Other editors and agents (Cursor, VS Code, Gemini CLI, Windsurf…) are covered in the MCP install guide.

Keep the connection alive

While you use it, Claude refreshes its access automatically. After 30 days without any use, the connection lapses.
Whatever the use, it ends 90 days after you approved it. To change that, open Settings → Developer → MCP connections, click Set lifetime on Claude’s row, enter Lifetime (days) (1–365) and click Save. The days count from the original approval, not from today.
You are warned: the business’s Owners and Administrators are emailed 14 days before it ends.
To renew, click Connect in Claude and approve again. A connection that has already ended cannot be extended, only re-approved.

Disconnect Claude

From Crisphive — cuts off Claude for the whole business

Open Settings → Developer → MCP connections. Under Connected AI apps, click Disconnect on Claude’s row, then Disconnect again to confirm. This revokes every active grant Claude holds for your business — if several people connected their own Claude (the row shows how many active grants), all of them are disconnected. The list shows only the mode the dashboard is in — switch to Rehearsal to find a Rehearsal connection.

From Claude

Open Customize → Connectors, open Crisphive, and disconnect or remove it. This affects only your own Claude account.

Expect a short tail

An access token Claude already holds keeps working for up to one hour after a disconnect in Crisphive; nothing new is issued. Removing or suspending the member stops the connection on its very next request.

Troubleshooting

Symptom	Cause	Fix
No Add custom connector option	Your Claude plan or organization does not allow custom connectors.	Use a plan that supports them, or ask your Claude organization admin to allow or add the connector.
Crisphive page says Invalid authorization request	The sign-in link was incomplete or expired.	Close the window and click Connect in Claude again.
Connected on claude.ai, but Desktop shows it disconnected	Claude Desktop does not always pick up a connector added on the web.	Add the connector directly in Claude Desktop.
Claude finds no customers or jobs, or different ones than you see	The connection is in the other mode (Live vs Rehearsal) than your dashboard.	Disconnect, switch the dashboard to the mode you want, connect and approve again.
`403 FORBIDDEN` when asking about jobs or the schedule	The person who approved is a Technician, or their role lacks job management.	Have an Owner or Booking Coordinator connect instead.
Approve fails with `access_denied`	Your membership is suspended, or the request asked for a permission your role does not hold.	Ask the Owner to reactivate you or adjust your role, then connect again.
Claude asks you to reconnect; `OAUTH_GRANT_EXPIRED`	The connection reached its lifetime (90 days by default) or was unused for 30 days.	Click Connect and approve again; raise the lifetime with Set lifetime if needed.
Claude disconnects unexpectedly soon after a refresh	A refresh token was used again more than 30 seconds after it was replaced, which Crisphive treats as theft and revokes the whole connection.	Connect and approve again.
Test booking “saved but not confirmed”, or `JOB_REQUEST_NO_TECHNICIAN_AVAILABLE`	No technician fits that exact time (skills, service area, working hours, other jobs).	Ask Claude for the nearest open times. Do not book the same 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 (e.g. `outside_service_area`, `outside_working_hours`).	Choose another day, or fix the cause in the dashboard (service area, working hours, technician skills).
`PHONE_INVALID`	The phone number is not a real number in international form.	Give it with the country code, e.g. `+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.
`ABSENCE_RESOLVE_TIME_OFF_REQUIRED`	A sick-call commit needs a time-off record covering every day of the absence.	Ask Claude to record the time off first, then commit again.
A commit fails because the schedule changed (e.g. `ABSENCE_RESOLVE_PLAN_DRIFTED`)	Someone changed the board between the preview and the commit.	Ask Claude for a fresh preview and approve that one.
`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; split large imports into smaller requests.

Move from Rehearsal to Live

Disconnect the Rehearsal connection, switch the dashboard to Live, then click Connect in Claude and approve — 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. Keep approval on for those tools (Step 4).
Note the Expires date in MCP connections (90 days by default) and renew before it, or raise the lifetime.
Using Claude Code with a key? Swap chsk_test_… for a chsk_live_… key. Keys expire too (30 days by default, up to 365, set when created; Owners and Administrators are emailed 7 days before). Revoke a key with Revoke access on its row under API keys.

AI assistants overview — Claude, ChatGPT and any other MCP client
ChatGPT — the Crisphive app and developer-mode connector
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

FAQ

Do I need an API key to connect Claude?

No. On claude.ai and Claude Desktop you sign in to Crisphive and click Approve. An API key is only an option for Claude Code and other developer tools.

How do I connect Claude to my sandbox (Rehearsal) instead of live data?

Switch the Crisphive dashboard to Rehearsal before you click Approve. The connection keeps the mode it was approved in; to change it, disconnect and approve again from the other mode.

Why can my technician’s Claude not see the schedule?

The connection acts as the person who approved it, and the Technician role cannot read the business-wide job board. Have an Owner or Booking Coordinator connect for dispatch work.

Why did my Crisphive connector stop working in Claude?

Usually the connection reached its lifetime (90 days after approval by default) or sat unused for 30 days, or the person who approved was removed, suspended or changed role. Reconnect and approve; check Settings → Developer → MCP connections for the expiry date.

Can two people in my business each connect their own Claude?

Yes. Each person approves with their own Crisphive sign-in, and each connection acts with that person’s role. In MCP connections they appear as one Claude row with several active grants; disconnecting that row disconnects all of them, so to remove one person’s access, have them disconnect in their own Claude settings.

Where do I see which AI apps are connected to my business?

In the Crisphive dashboard under Settings → Developer → MCP connections, section Connected AI apps. It lists the current mode only, so switch to Rehearsal to see Rehearsal connections.

Next ›ChatGPT

ON THIS PAGE

Ways to connect Before you start Step 1 — Add Crisphive as a custom connector Step 2 — Sign in to Crisphive and approve Which role to connect with Step 3 — Point it at Live or Rehearsal data Ready-to-copy settings Step 4 — Choose which tools run without asking Step 5 — Test the connection Claude Desktop and mobile Claude Code Keep the connection alive Disconnect Claude Troubleshooting Move from Rehearsal to Live Related guides and reference FAQ