MCP / Clients

Connect your AI client.

Bridge Town is bring-your-own-agent. Your AI client runs the model session; Bridge Town does not invoke server-side LLMs or proxy prompts. The MCP surface has 75 tools, with 14 hot tools loaded by default and the rest discovered on demand.

Get a connection token → Scopes reference →

Claude.ai

The fastest way to get started. Open Claude.ai → Customize → + Add custom connector, paste the URL below, and authorise via Bridge Town's OAuth consent screen.

endpoint

https://api.bridgetown.builders/mcp

Connect Claude.ai step by step →

Claude Desktop

Claude Desktop requires the mcp-remote bridge. Add the following to your claude_desktop_config.json under mcpServers:

json — claude_desktop_config.json

{
  "bridge-town": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://api.bridgetown.builders/mcp",
      "--header",
      "Authorization: Bearer btk_YOUR_TOKEN"
    ]
  }
}

Generate your token at app.bridgetown.builders/connect.

Connect Claude Desktop step by step →

Claude Code

Install via the CLI with your bearer token:

shell

claude mcp add bridge-town https://api.bridgetown.builders/mcp \
  --transport http \
  --header "Authorization: Bearer btk_YOUR_TOKEN"

Generate your token at app.bridgetown.builders/connect. Run claude mcp list to verify. Claude Code uses tool search for large MCP servers — for final-surface testing, launch with ENABLE_TOOL_SEARCH=auto:5 claude.

Connect Claude Code step by step →

Claude API

Use Anthropic's Messages API MCP connector with mcp_toolset.default_config.defer_loading=true, then mark Bridge Town's 14 hot tools as defer_loading=false.

The Anthropic Messages API MCP connector path is tools-only. Use Claude Code, Claude Desktop, or another full MCP client if you need Bridge Town resources or workflow prompts.

Connect the Claude API step by step →

Codex

shell

codex mcp add bridge-town https://api.bridgetown.builders/mcp \
  --transport http \
  --header "Authorization: Bearer btk_YOUR_TOKEN"

Generate your token at app.bridgetown.builders/connect. Run codex mcp list to verify.

Cursor

Add to your Cursor MCP config (~/.cursor/mcp.json):

json — ~/.cursor/mcp.json

{
  "mcpServers": {
    "bridge-town": {
      "transport": {
        "type": "http",
        "url": "https://api.bridgetown.builders/mcp",
        "headers": {
          "Authorization": "Bearer btk_YOUR_TOKEN"
        }
      }
    }
  }
}

Restart Cursor after saving. Generate your token at app.bridgetown.builders/connect.

OpenCode

shell

opencode mcp add bridge-town https://api.bridgetown.builders/mcp \
  --transport http \
  --header "Authorization: Bearer btk_YOUR_TOKEN"

Or use the JSON config form (same shape as the Cursor example above in opencode.json → mcpServers). Replace btk_YOUR_TOKEN with your token from app.bridgetown.builders/connect.

Any other MCP client

Any client that supports MCP Streamable HTTP transport can connect:

connection details

Transport: http
URL:       https://api.bridgetown.builders/mcp
Header:    Authorization: Bearer btk_YOUR_TOKEN

See the manual connection guide for the full JSON config format and mcp-remote bridge instructions for legacy SSE-only clients.