# Crisp setup for PopMCP

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.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.crisp.chat/v1
- Credentials screen: https://app.crisp.chat/settings/
- Provider docs: https://docs.crisp.chat/guides/rest-api/authentication/website-token/

## 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

### 1. Open Workspace Settings

Click Settings at the bottom of the left sidebar, then switch to the Workspace Settings tab.

Screen: https://app.crisp.chat/settings/

### 2. Copy your Website ID

Open Setup & Integrations and click Copy next to Website ID. Copy the UUID, not the workspace display name above it.

Screen: https://app.crisp.chat/settings/

### 3. Generate a website API token

Open Advanced configuration in the same Workspace Settings tab and scroll to the API Token section. Click Generate Token.

### 4. Copy both halves of the token pair

Click Copy credentials, then paste the identifier and the key somewhere safe before you close the panel.

### 5. Paste all three values into PopMCP

Fill Website ID, Token Identifier and Token Key in PopMCP, then click Connect.

## Fields PopMCP asks for

- Website ID (websiteId) [required]: 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 Identifier (identifier) [required]: Settings → Workspace Settings → Advanced configuration → API Token → Generate Token. Copy the identifier (the left half of the pair). Shown only once.
- Token Key (key) [required]: 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.

## Verify

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

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: 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.

---

Source: https://www.docs.popmcp.com/docs/integrations/crisp/