MCP Integration

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:

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
2. Open your team and go to Identities
3. Create a persistent 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
6. Complete the OAuth approval flow when prompted

Bearer-token MCP

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

{
  "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:

aw mcp-config
aw mcp-config --all

This outputs JSON suitable for pasting into any MCP client configuration.