> ## Documentation Index
> Fetch the complete documentation index at: https://www.integrate.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# ETL: Connect Claude Desktop and Claude.ai to MCP

> Connect Claude Desktop or Claude.ai web to the Integrate.io ETL MCP server with an OAuth custom connector, the one-click extension, or a token bridge.

This page covers Claude Desktop and Claude.ai web. Using Claude Code instead? See [Claude Code](https://www.integrate.io/docs/etl/mcp-connect-claude-code.md). For token and OAuth detail, see [Authentication](https://www.integrate.io/docs/etl/mcp-authentication.md).

The endpoint for every option below is:

`https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp`

Replace `YOUR_ACCOUNT_ID` with your account subdomain or numeric id (the value in your dashboard URL).

## Claude.ai web (OAuth custom connector)

Claude.ai supports custom connectors natively over OAuth, so there is no token to paste and no bridge to install.

**1. Open connector settings**

In Claude.ai, go to **Settings → Connectors** and click **Add custom connector**.

**2. Enter the endpoint**

Enter a recognizable name (e.g. "Integrate.io") and the endpoint URL above.

**3. Authorize with OAuth**

Authorize with OAuth. Sign in to Integrate.io if you aren't already, then click **Authorize**. Claude stores the credentials and refreshes them automatically.

Custom connectors are available on the free, Pro, Max, Team, and Enterprise plans (free accounts are limited to one custom connector).

> [!NOTE]
>
> Claude.ai connects from Anthropic's cloud rather than from your device, so the endpoint must be reachable over the public internet (the production URL is). See the reachability note in [Authentication](https://www.integrate.io/docs/etl/mcp-authentication.md).

## Claude Desktop (OAuth custom connector, recommended)

Recent Claude Desktop versions support the same OAuth custom connectors as Claude.ai web. Add the endpoint as a custom connector under **Settings → Connectors**, authorize with OAuth, and you are done, no token to manage.

## Claude Desktop (one-click extension)

If you'd rather use a Personal Access Token than OAuth, the quickest token-based option is the Integrate.io extension (`.mcpb`). The extension prompts you for your account subdomain and Personal Access Token at install time, so you never touch `claude_desktop_config.json` by hand.

Requires Claude Desktop 0.10 or later on macOS or Windows.

1. In the Integrate.io dashboard, go to **Settings → Developer Settings → Connected Applications**.
2. In the **Quick install for Claude Desktop** card, click **Download Claude Desktop extension**. The browser downloads `integrate-io-mcp.mcpb`.
3. Open Claude Desktop and go to **Settings → Extensions**. Drag the downloaded `.mcpb` file onto that page. Claude Desktop opens the extension install dialog.
4. When prompted:
   * **Account Subdomain**: your Integrate.io account subdomain or numeric id (the value in your dashboard URL).
   * **Personal Access Token**: a PAT (see [Authentication](https://www.integrate.io/docs/etl/mcp-authentication.md#personal-access-token-pat)). If you haven't minted one yet, click **+ Create new connection** on the Connected Applications page first.
5. Click **Install**, then restart Claude Desktop (fully quit and reopen).

In Claude Desktop's MCP picker you should now see `integrateio` with the full tool list. See [Verify](#verify) below.

> [!NOTE]
>
> On a staging Integrate.io account the same card serves `integrate-io-mcp.staging.mcpb` and displays a **Staging build** badge. The staging extension only talks to `api-staging.xplenty.com`, so it won't work with a production PAT. Both extensions can be installed side by side. Claude Desktop treats them as separate integrations (`integrate-io-mcp` and `integrate-io-mcp-staging`).

> [!TIP]
>
> **Migrating from the manual `claude_desktop_config.json` entry?** Remove the old `xplenty` (or whatever you named it) entry from `mcpServers` in your config file **before** installing the extension. If both an extension and a manual entry point at the same backend, the install dialog may silently no-op because Claude Desktop sees the integration as already configured. Restart Claude Desktop after removing the stale entry, then drag the `.mcpb` in.

### Updating or removing the extension

* **Update:** download the latest `.mcpb` from the Connected Applications page and drag it onto **Settings → Extensions** again. The version field in the bundle increments on each release, so Claude Desktop treats it as an update rather than a duplicate. Your subdomain and token entered at first install are preserved.
* **Remove:** go to **Settings → Extensions** in Claude Desktop, find **Integrate.io** in the list, and click the remove/uninstall control. Optionally revoke the underlying Personal Access Token from **Connected Applications** in the Integrate.io dashboard.

## Claude Desktop (token bridge, fallback)

If you can't use the custom connector or the extension (an older Claude Desktop, corporate policy, or you'd rather hand-edit the config), connect over a token using the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) bridge. Claude Desktop speaks MCP over stdio only, so the bridge turns the remote HTTP endpoint into a local stdio server.

Edit your Claude Desktop configuration file:

* macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
* Windows: `%APPDATA%\Claude\claude_desktop_config.json`

Add an entry under `mcpServers`:

```json theme={null}
{
  "mcpServers": {
    "integrateio": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp",
        "--header",
        "Authorization: Bearer YOUR_ACCESS_TOKEN"
      ]
    }
  }
}
```

Replace `YOUR_ACCOUNT_ID` with your account subdomain or numeric id and `YOUR_ACCESS_TOKEN` with a Personal Access Token (see [Authentication](https://www.integrate.io/docs/etl/mcp-authentication.md)), then restart Claude Desktop (Cmd+Q on macOS, fully quit and reopen; reloading the window isn't enough).

> [!TIP]
>
> The Connected Applications reveal modal generates this snippet for you with the URL and token already filled in. Click **Copy** under the **Claude Desktop** tab, paste into your config, restart Claude.

## Verify

In Claude Desktop, type `/mcp` in the chat input. You should see `integrateio` listed with its tools available. Try: "List the workspaces in my Integrate.io account." Trouble connecting? See [Troubleshooting](https://www.integrate.io/docs/etl/mcp-troubleshooting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.