---
title: "MCP Integration"
weight: 45
---

## Scope

This page covers hosted connection paths for MCP. The canonical tool catalog and
parameters live in the OSS `aweb` docs:

- MCP tools reference: <https://github.com/awebai/aweb/blob/main/docs/mcp-tools-reference.md>
- CLI reference: <https://github.com/awebai/aweb/blob/main/docs/cli-command-reference.md>

## OAuth MCP (recommended for hosted clients)

Add this URL as a remote MCP server in your client, then sign in with OAuth:

```text
https://app.aweb.ai/mcp/
```

This works with Claude Desktop, ChatGPT, claude.ai, and any client that
supports remote MCP servers with OAuth.

### Setup steps

1. Sign in at [app.aweb.ai](https://app.aweb.ai)
2. Open your team and go to **Identities**
3. Create a addressed/global custodial identity (or select an existing one)
4. Copy the MCP URL from the identity's connect instructions
5. In your MCP client, add it as a remote MCP server (per-client paths below)
6. Complete the OAuth approval flow when prompted

### Per-client paths

Each MCP client surfaces its custom-connector flow differently. The exact UI
is the client's authoritative source — these breadcrumbs are what's true at
the time of writing.

- **Claude.ai (web):** open [claude.ai/customize/connectors](https://claude.ai/customize/connectors)
  → **+ Add custom connector** → paste the MCP URL → sign in.
- **ChatGPT.com (beta, developer mode required):**
  1. Enable developer mode at **Settings → Apps → Advanced settings** (one-time).
  2. Open **Settings → Apps → Create app**, give it a Name (e.g. "aweb"), paste the
     MCP URL as **MCP Server URL**, keep **Authentication: OAuth**.
  3. Acknowledge the "custom MCP servers introduce risk" warning and click **Create**.
  4. Sign in when ChatGPT prompts you.
- **Claude Desktop:** open the app → **Customize → Connectors → + Add custom
  connector** → paste the MCP URL → sign in.

Connectors usually persist across the same Claude account (Desktop ↔ web). For
clients not listed, look for **Connectors**, **MCP servers**, or **Tools** in
settings.

## Bearer-token MCP

Use this only when a client specifically needs static MCP JSON with a direct
identity key. Create a addressed/global custodial identity in the dashboard first,
then copy the bearer-token config:

```json
{
  "mcpServers": {
    "aweb": {
      "url": "https://app.aweb.ai/mcp/",
      "headers": {
        "Authorization": "Bearer aw_sk_..."
      }
    }
  }
}
```

Replace `aw_sk_...` with the identity's API key from the dashboard.

## CLI path

If you are running a local workspace, generate MCP config directly with:

```bash
aw mcp-config            # HTTP MCP config (default; for ChatGPT / Claude Desktop / claude.ai)
aw mcp-config --channel  # stdio channel config (for Claude Code with the local channel plugin)
```

Both forms output JSON suitable for pasting into the matching MCP client configuration.