Connect an agent

TeamDuo is a remote MCP server. Claude alone has several distinct ways to add one, and which applies depends on which Claude product you’re using — a chat client, a team workspace, a terminal, or your own code calling the API directly. This page covers all of them.

The connector URL

https://api.teamduo.ai/mcp

That single URL is the whole configuration for every path below except one — the API, which also needs a credential, since there’s no browser to complete an OAuth flow in.

Connect Claude

claude.ai, Desktop, or Cowork
Team or Enterprise workspace
Claude Code (CLI)
Claude Developer Platform (API)

These three share one setting, because a remote connector is brokered through your Claude account, not your device — the connection to TeamDuo runs from Anthropic’s servers, not your machine, even when you added it from the Desktop app.

Open Connectors settings

In claude.ai, Claude Desktop, or Cowork: Settings → Connectors.

Add a custom connector

Click Add custom connector, paste the URL above, and click Add.

Connect

Back in the connector list, click Connect and approve TeamDuo in the browser tab that opens. You’re authorizing as yourself — the agent will reach exactly what your TeamDuo account can reach, and nothing more.

This is a Claude account limit, not a TeamDuo one: Claude’s Free plan allows one custom connector; Pro and Max have no limit on personal connectors.

This is separate from Claude Desktop’s claude_desktop_config.json, which configures local stdio servers that run on your machine. TeamDuo is a remote HTTP server, so it’s added through Connectors settings above, never through that file.

claude mcp add --transport http teamduo https://api.teamduo.ai/mcp

Then authorize, either from inside a session:

/mcp

and follow the browser flow, or without opening one:

claude mcp login teamduo

Choose a scope

claude mcp add writes to local scope by default — visible only to you, in the current project. Add --scope user to reach it from every project instead, or --scope project to check it into .mcp.json and share it with your team:

{
  "mcpServers": {
    "teamduo": {
      "type": "http",
      "url": "https://api.teamduo.ai/mcp"
    }
  }
}

A teammate who pulls a repo with this file still authorizes with their own TeamDuo login the first time they use it — the checked-in file shares the connector, not anyone’s access.

Verify

claude mcp get teamduo

/mcp inside a session also shows connection health, and offers Re-authenticate if your token ever needs refreshing.

Building your own application on the Messages API rather than using a Claude chat client calls for the MCP connector feature — no separate MCP client library required.

curl https://api.anthropic.com/v1/messages \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: mcp-client-2025-11-20" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-opus-5",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "List my TeamDuo datasources."}],
    "mcp_servers": [
      {
        "type": "url",
        "url": "https://api.teamduo.ai/mcp",
        "name": "teamduo",
        "authorization_token": "sk_live_..."
      }
    ],
    "tools": [
      { "type": "mcp_toolset", "mcp_server_name": "teamduo" }
    ]
  }'

There’s no browser here for TeamDuo’s OAuth flow to redirect to, so skip it — pass a TeamDuo API key directly as authorization_token. TeamDuo accepts an sk_live_... key on the same /mcp endpoint it accepts an OAuth token on, so this is a normal, supported credential for this path, not a workaround.

Restrict which tools Claude can call with default_config/configs on the mcp_toolset entry — useful for e.g. denying run_query while keeping describe_datasource and search_docs available. See MCP tools for what each one does.

Other MCP clients

Any client that supports remote MCP servers over OAuth can connect the same way: add the connector URL, and follow its own authorization flow. ChatGPT, for one, adds custom connectors under its own connector settings, the same shape as Claude’s.

Clients that need an API key

For anything that can’t complete an interactive OAuth flow — scripts, CI, a self-hosted agent — create an API key under Settings → API keys and send it as a bearer token:

Authorization: Bearer <your_api_key>

Keys carry scopes, and a key is the only way to reach the connector without a browser session. Treat one as equivalent to your read access to every exposed datasource its scopes allow.

Transports

Transport	Endpoint
Streamable HTTP	`POST https://api.teamduo.ai/mcp`
SSE	`https://api.teamduo.ai/mcp/sse`

Streamable HTTP is the current standard and what Claude uses. SSE exists for older clients that haven’t moved off it yet.

Verifying the connection

Ask the agent to list your teams, then your datasources. If the teams come back but the datasource list is empty, the connection is fine and nothing has been exposed yet — see Connect a datasource.

Calling the same data over plain HTTP

MCP is the recommended path for an agent. For a script or service that would rather speak raw HTTP, the same read-only surface — list teams, list datasources, describe one, run a query — is available as a small REST API. See the REST API overview.

Get started

Guides

Connect an agent

The connector URL

Connect Claude

Other MCP clients

Clients that need an API key

Transports

Verifying the connection

Calling the same data over plain HTTP

​The connector URL

​Connect Claude

​Other MCP clients

​Clients that need an API key

​Transports

​Verifying the connection

​Calling the same data over plain HTTP

The connector URL

Connect Claude

Other MCP clients

Clients that need an API key

Transports

Verifying the connection

Calling the same data over plain HTTP