# 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.
> **Note:** **Claude Code users:** If you run Claude Code in the terminal, see [Setup & Installation](/docs/guides/mcp/setup) instead. That path edits `~/.claude.json` directly and is separate from the connector UI covered here.
> **Note:** MCP server access requires a Studio plan or higher. Upgrade to Studio
## Prerequisites
- A Chipp account on a **Studio plan or higher** ([upgrade here](https://build.chipp.ai/plans))
- The **Claude app** (desktop or web) or **Claude Cowork** -- any recent version
## Step 1: Open Connector Settings
**Claude app (desktop or web):**
1. Open Claude.
2. Click your profile or the **Settings** icon.
3. Navigate to **Integrations** (some versions label this **Connectors** or **MCP Servers**).
**Claude Cowork:**
1. Open your Cowork project.
2. Click **Settings** for the project.
3. Select **Integrations** or **MCP Connectors**.
## Step 2: Add a Custom Connector
1. Click **Add custom connector** (some versions call this **Add MCP server**).
2. A dialog opens with a URL field.
3. Enter the URL of the Chipp MCP you want. Start with `core`:
```
https://mcp.chipp.ai/mcp/core
```
Then add one connector for each other area you use, for example `https://mcp.chipp.ai/mcp/knowledge` or `https://mcp.chipp.ai/mcp/tickets`. Each connector sends only its own tools to Claude, so conversations stay fast. [Chipp MCPs](/docs/guides/mcp/sub-mcps) lists them all. To add everything as one connector, use `https://build.chipp.ai/mcp` (about 157,000 tokens per message).
4. Leave the transport on the default setting (**HTTP** / **Streamable HTTP**). Do not switch to SSE.
5. 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 | The name of the app connecting (for example, **Claude**) |
| Your account | Confirm the organization and workspace shown are the ones you intend to connect |
| Permissions | Read permissions are pre-checked. Write permissions (for example **Manage your apps**) are unchecked and marked **Destructive, opt-in**: check only the ones you need |
> **Note:** **Claude Enterprise / Team organization connectors** use the same page. The full list of permissions, including every write permission, is shown on it. If an older connection only ever offered **View** permissions, disconnect the Chipp connector in Claude and connect it again: an existing connection keeps the permissions it was first granted, and only a new authorization shows the write options.
If the account shown is wrong, open [build.chipp.ai](https://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.
> **Warning:** 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:
1. Open a new conversation.
2. 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:**
1. In the integrations list, remove the Chipp connector.
2. Add it again using the same URL (`https://build.chipp.ai/mcp`).
3. When the authorization page opens, click **Authorize**.
4. If a popup blocker prevented the page from opening, allow popups for `build.chipp.ai` and 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/mcp
```
### Connector 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:**
1. Close and reopen Claude, then start a fresh conversation.
2. If the connector status shows **Error** instead of **Connected**, re-authorize: remove the connector and add it again to restart the OAuth flow.
3. Confirm your Chipp account is on a [Studio plan or higher](https://build.chipp.ai/plans). MCP access requires a paid subscription.
---
## Next Steps