# 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 Builder plan or higher. <a href="https://build.chipp.ai/plans" target="_blank" rel="noopener noreferrer">Upgrade to Builder</a>

## Prerequisites

- A Chipp account on a **Builder 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**.

<img
  src="/assets/docs/screenshots/mcp-claude-app-connectors.png"
  alt="Claude app connector settings panel showing existing connectors and an Add custom connector button"
/>

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

<img
  src="/assets/docs/screenshots/mcp-claude-app-add-custom.png"
  alt="Add custom connector dialog with a URL input field ready for the Chipp MCP server address"
/>

3. Enter the Chipp MCP server URL:

   ```
   https://build.chipp.ai/mcp
   ```

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.

<img
  src="/assets/docs/screenshots/mcp-chipp-auth-modal.png"
  alt="Chipp authorization modal showing the application name Chipp MCP Server, the signed-in account email, the permissions being requested, and Authorize and Deny buttons"
/>

**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](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.

<img
  src="/assets/docs/screenshots/mcp-claude-app-connected.png"
  alt="Claude integrations panel showing Chipp MCP Server listed with a Connected status indicator"
/>

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 [Builder plan or higher](https://build.chipp.ai/plans). MCP access requires a paid subscription.

---

## Next Steps

<div>
  
  
  
  
</div>