Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Crisp (BYOK) icon

Crisp (BYOK)

Read your Crisp inbox conversations, messages, customer profiles, operators and availability with BYOK

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderCrispunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What is the name and domain of my Crisp website?
Tools called
get_website
Is my Crisp chat online right now?
Tools called
get_availability
Who are the operators on my Crisp website?
Tools called
list_operators
Which Crisp operators are online?
Tools called
list_operator_availabilities
Show my unresolved Crisp conversations
Tools called
list_conversations
Show Crisp conversation session_8c842203-7ed8-4e24-a2d1-3f52ba9d4b6e
Tools called
get_conversation

About

Crisp (BYOK) lets an AI assistant read your own Crisp data through the Crisp API with a key you supply (Crisp token identifier). Read-only: 9 tools (get_website, get_availability, list_operators, list_operator_availabilities, list_conversations, get_conversation, list_messages, list_people_profiles, get_people_profile). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.crisp.chat. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Crisp API (api.crisp.chat) with a BYOK key; documentation: https://docs.crisp.chat/references/rest-api/v1/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • Get websiteGet a Crisp website (workspace): name, domain, logo and verification status.
  • Get availabilityShow whether the Crisp chatbox currently appears online, away or offline to visitors.
  • List operatorsList the operator members of a Crisp website with name, email, role and availability.
  • List operator availabilitiesList each Crisp operator's current availability (online, away or offline).
  • List conversationsList Crisp conversations, 20 to 50 per page, with state, visitor contact, last message, topic and times.
  • Get conversationGet one Crisp conversation by session id: state, assignee, unread counters, visitor nickname and email, topic and times.
  • List messagesList the latest messages of a Crisp conversation (the most recent batch), with sender, type, text or file content and time.
  • List people profilesList Crisp customer (people) profiles, 20 to 50 per page, with email, name, phone, company, segments and activity.
  • Get people profileGet one Crisp customer profile by people id or email address.

Information

PublisherUnify Dynamics LLC
CategoryWork & productivity
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-crisp.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-crisp.connectorbay.com/mcp
RESTPOST https://byok-crisp.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-crisp.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Crisp token identifier in the X-Upstream-Key header (get one at docs.crisp.chat).
  • Ask a question; the agent picks the right tool and answers from the live data.

Crisp connector: questions and answers

What is the Crisp connector?

Crisp (BYOK) lets an AI assistant read your own Crisp data through the Crisp API with a key you supply (Crisp token identifier). It is a hosted MCP server with 9 tools such as Get website, Get availability, List operators, List operator availabilities, List conversations, Get conversation, published by Unify Dynamics LLC. It is independent and not affiliated with Crisp.

How do I connect Crisp to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-crisp.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-crisp.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-crisp.json.

Do I need a Crisp account or API key?

Yes: this is a bring-your-own-key connector. Create a Crisp token identifier at https://docs.crisp.chat/guides/rest-api/authentication/website-token/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Crisp read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Crisp connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Trint US (BYOK)

Read your Trint US tenant transcripts, folders and Shared Drives with your own API key ID and secret

Live · MCP + REST6 tools

Trint EU (BYOK)

Read your Trint EU tenant transcripts, folders and Shared Drives with your own API key ID and secret

Live · MCP + REST6 tools

Tulip (BYOK)

Read your Tulip frontline operations setup: stations, station groups, interfaces, roles, user groups, app groups, machine types and tables with your own API token

Live · MCP + REST8 tools

Tumblr (BYOK)

Read public Tumblr blogs, their posts, likes and notes, and posts under a tag, with your own API key (OAuth consumer key)

Live · MCP + REST8 tools

Twilio (BYOK)

Read your Twilio account, phone numbers, call and message logs and usage records with BYOK (read-only; never sends anything)

Live · MCP + REST6 tools

Twilio Content (BYOK)

Read your Twilio Content Templates (rich messages for WhatsApp, SMS and more) and their approval status with your own credentials (read-only)

Live · MCP + REST5 tools

Documentation

Back to top

Crisp (BYOK) — connector documentation

  • MCP endpoint: https://byok-crisp.connectorbay.com/mcp
  • REST API: POST https://byok-crisp.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-crisp.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Crisp Crisp token identifier, sent in the X-Upstream-Key header and the Crisp token key (secret) in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-crisp.connectorbay.com/health · Tool schemas: https://byok-crisp.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-crisp · agent@connectorbay.com

What Crisp (BYOK) is for

Crisp (BYOK) lets an AI assistant read your own Crisp data through the Crisp API with a key you supply (Crisp token identifier). Read-only: 9 tools (get_website, get_availability, list_operators, list_operator_availabilities, list_conversations, get_conversation, list_messages, list_people_profiles, get_people_profile). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.crisp.chat. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What is the name and domain of my Crisp website?"
  • "Is my Crisp chat online right now?"
  • "Who are the operators on my Crisp website?"
  • "Which Crisp operators are online?"
  • "Show my unresolved Crisp conversations"
  • "Show Crisp conversation session_8c842203-7ed8-4e24-a2d1-3f52ba9d4b6e"

What it does

  • get_website: Get a Crisp website (workspace): name, domain, logo and verification status.
  • get_availability: Show whether the Crisp chatbox currently appears online, away or offline to visitors.
  • list_operators: List the operator members of a Crisp website with name, email, role and availability. Invite keys are never returned.
  • list_operator_availabilities: List each Crisp operator's current availability (online, away or offline).
  • list_conversations: List Crisp conversations, 20 to 50 per page, with state, visitor contact, last message, topic and times. Filter by unread, resolved, assignment, inbox or date; or search.
  • get_conversation: Get one Crisp conversation by session id: state, assignee, unread counters, visitor nickname and email, topic and times.
  • list_messages: List the latest messages of a Crisp conversation (the most recent batch), with sender, type, text or file content and time. Page towards older messages with timestamp_before.
  • list_people_profiles: List Crisp customer (people) profiles, 20 to 50 per page, with email, name, phone, company, segments and activity. Supports a quick text search.
  • get_people_profile: Get one Crisp customer profile by people id or email address.

BYOK key

You bring your own Crisp Crisp token identifier (https://docs.crisp.chat/guides/rest-api/authentication/website-token/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.crisp.chat over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Crisp API (api.crisp.chat) with a BYOK key; documentation: https://docs.crisp.chat/references/rest-api/v1/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Crisp account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Crisp (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Crisp (BYOK) is. Crisp (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Crisp data: Read your Crisp inbox conversations, messages, customer profiles, operators and availability with BYOK. You bring your own Crisp Crisp token identifier; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Crisp call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.crisp.chat, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Crisp rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Crisp receives. The request we make on your behalf, including the key and the arguments, under Crisp's own terms and privacy policy. Crisp acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Crisp gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Crisp data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Crisp (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Crisp at any time to end all access.

Children. Crisp (BYOK) is a general-audience service operated by the adult using the assistant, under Crisp's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Crisp (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Crisp (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Crisp (BYOK) provides: Read your Crisp inbox conversations, messages, customer profiles, operators and availability with BYOK. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Crisp credentials and only access data you are allowed to access. Crisp's terms apply to your use of Crisp; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Crisp. Crisp and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Crisp returns, lightly trimmed; it may be incomplete, delayed or changed by Crisp. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Crisp account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Crisp's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Crisp may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Crisp key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Crisp takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-crisp

Crisp (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Crisp (BYOK) never asks for them.

Get Crisp (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Crisp Crisp token identifier. Create one at https://docs.crisp.chat/guides/rest-api/authentication/website-token/, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Crisp. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Crisp.