Crisp
Connect Crisp to read and send conversation messages, manage contacts and visitors, run campaigns, and use the helpdesk.
You paste three values into PopMCP: your Crisp Website ID, which is a UUID, plus both halves of a website API token, the token identifier and the secret token key.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://api.crisp.chat/v1
- Rate limits
- Website tokens are capped at 10,000 requests per day. Crisp also applies a load-balancer limit, a permissive API-global limiter and a stricter per-route limiter, so bursty polling on one route can return 429 well below the daily cap.
Before you begin
- A Crisp workspace on any plan. Website tokens need no Marketplace account and no approval
- Owner-level access to the workspace. Workspace Settings → Advanced configuration is hidden from ordinary operators
- Somewhere safe to paste the token pair immediately, because Crisp shows the key exactly once
Get your credentials
Open Workspace Settings
Click Settings at the bottom of the left sidebar, then switch to the Workspace Settings tab.
Copy your Website ID
Open Setup & Integrations and click Copy next to Website ID. Copy the UUID, not the workspace display name above it.
Setup & Integrations
Install the chatbox and connect Crisp to your stack.
- Workspace name
- Acme Supply
- Website ID
- e93e****-****-****-****-********65bb
- Plan
- Pro
The same UUID appears as the /website/<id>/ segment of any dashboard URL.
Generate a website API token
Open Advanced configuration in the same Workspace Settings tab and scroll to the API Token section. Click Generate Token.
Advanced configuration
Developer access, webhooks and data controls.
Generating a new token replaces the previous one for this workspace.
Copy both halves of the token pair
Click Copy credentials, then paste the identifier and the key somewhere safe before you close the panel.
Advanced configuration
Paste all three values into PopMCP
Fill Website ID, Token Identifier and Token Key in PopMCP, then click Connect.
Connect in PopMCP
Open your workspace, choose Crisp in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Website IDtext | In Crisp: Settings → Workspace Settings → Setup Instructions. It's a UUID. You can also paste a dashboard URL (https://app.crisp.chat/website/<id>/…); we'll extract the id. This is the workspace the MCP is locked to. |
| Token Identifiertext | Settings → Workspace Settings → Advanced configuration → API Token → Generate Token. Copy the identifier (the left half of the pair). Shown only once. |
| Token Keysecret | The secret key (the right half of the token pair), shown only once when you generate the token. Sent as HTTP Basic auth and stored encrypted; used server-side only.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Crisp immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks Crisp as Connected, names the workspace it locked onto, and a first tool call such as listing recent conversations returns real threads instead of a 401.
Troubleshooting
401 Unauthorized on every call
Why: Identifier and key were pasted into each other's field, or extra whitespace was copied with the key.
Fix: Re-paste carefully. The identifier is the shorter left-hand value. If in doubt, generate a fresh token and reconnect.
403 on a workspace you can see in the dashboard
Why: The Website ID belongs to a different workspace than the one the token was generated in. Website tokens are single-workspace.
Fix: Copy the Website ID from Setup & Integrations of the same workspace where you generated the token.
Requests start failing part-way through the day
Why: Website tokens are capped at 10,000 requests per day, and a stricter per-route limiter sits on top of that.
Fix: Back off and retry after a pause. If you need a larger quota, move to a Marketplace plugin token instead of a website token.
Advanced configuration is not in the menu
Why: You are signed in as an operator rather than an owner of the workspace.
Fix: Ask a workspace owner to generate the token, or have them raise your role.
You generated an MCP Server Token but PopMCP wants a pair
Why: The Advanced configuration page offers both an API Token and a separate MCP Server Token. PopMCP uses the REST API pair.
Fix: Use Generate Token in the API Token section and copy the identifier and key it returns.