Connect from Claude App or Claude Cowork
Add Chipp as a custom connector in the Claude desktop app or Claude Cowork, approve the authorization modal, and confirm the connected state.
This guide walks you through connecting the Chipp MCP Server to Claude (the desktop or web app) or Claude Cowork. You add a custom connector, paste the Chipp URL, and approve a Chipp authorization modal. No config file editing is required.
Claude Code users: If you run Claude Code in the terminal, see Setup & Installation instead. That path edits ~/.claude.json directly and is separate from the connector UI covered here.
MCP server access requires a Builder plan or higher. Upgrade to Builder
Prerequisites
- A Chipp account on a Builder plan or higher (upgrade here)
- The Claude app (desktop or web) or Claude Cowork — any recent version
Step 1: Open Connector Settings
Claude app (desktop or web):
- Open Claude.
- Click your profile or the Settings icon.
- Navigate to Integrations (some versions label this Connectors or MCP Servers).
Claude Cowork:
- Open your Cowork project.
- Click Settings for the project.
- Select Integrations or MCP Connectors.
Step 2: Add a Custom Connector
- Click Add custom connector (some versions call this Add MCP server).
- A dialog opens with a URL field.
-
Enter the Chipp MCP server URL:
plaintexthttps://build.chipp.ai/mcp -
Leave the transport on the default setting (HTTP / Streamable HTTP). Do not switch to SSE.
-
Click Add or Connect.
Step 3: Approve the Chipp Authorization Modal
After clicking Add, a Chipp authorization page opens in your browser.
Review these fields before you approve:
| Field | What to check |
|---|---|
| Application name | Must read Chipp MCP Server |
| Your account | Confirm this is the Chipp account you intend to connect |
| Permissions | Full access to your Chipp apps, knowledge sources, and analytics |
If the account shown is wrong, open build.chipp.ai in the same browser, sign in to the correct account, then return to the authorization page and refresh.
Click Authorize to approve the connection. The browser tab closes and control returns to Claude.
If you click Deny, the connector is added without credentials. Remove it from the integrations list and add it again to restart the authorization flow.
Step 4: Confirm the Connected State
Back in Claude or Claude Cowork, the Chipp connector appears in your integrations list with a Connected status.
To verify Chipp is active:
- Open a new conversation.
- Ask:
List my Chipp apps
Claude calls the Chipp MCP tools and returns a list of your applications. Seeing your apps confirms the connection works.
Troubleshooting
Authorization modal was rejected or did not open
Cause: The OAuth flow did not complete, or you clicked Deny.
Fix:
- In the integrations list, remove the Chipp connector.
- Add it again using the same URL (
https://build.chipp.ai/mcp). - When the authorization page opens, click Authorize.
- If a popup blocker prevented the page from opening, allow popups for
build.chipp.aiand retry.
Connection error or “Server not found”
Cause: A typo in the MCP URL.
Fix: Remove the connector, add it again, and enter the URL exactly as shown — no trailing slash, no extra path:
https://build.chipp.ai/mcpConnector shows as Connected but Chipp tools do not appear
Cause: The connector did not finish loading, or MCP access is not enabled for your plan.
Fix:
- Close and reopen Claude, then start a fresh conversation.
- If the connector status shows Error instead of Connected, re-authorize: remove the connector and add it again to restart the OAuth flow.
- Confirm your Chipp account is on a Builder plan or higher. MCP access requires a paid subscription.