Connect your MCP client

Before connecting, review MCP authentication and sign in to Agent Builder once.

Connect your client

The examples name the connection bandwidth_agents. Keep that name consistent when adding, authenticating, and inspecting the server. If you already added the correct URL, continue with sign-in or connection verification.

Claude web
Claude Code
Codex
Other MCP clients

Open Customize → Connectors → Add → Add custom connector and name it bandwidth_agents. On Team and Enterprise plans, an eligible administrator first adds it under Organization settings → Connectors → Add → Custom → Web.
Paste https://agents.labs.bandwidth.com/api/v1/mcp/, including the final /, and continue.
Select Sign in now and Use Claude’s published identity (Recommended) under OAuth client. Leave custom client credentials and request headers empty.
Finish adding the connector and complete Labs sign-in and consent.
Enable the connector in your conversation, then try the workspace access prompt.

Claude web connects from Anthropic’s cloud. A working local CLI connection does not verify that cloud connection. See Claude’s custom connector guide for plan-specific setup and connector management.

Run these commands in your terminal.1. Add the server. The user scope makes the connection available across your projects.

claude mcp add --transport http --scope user \
  bandwidth_agents \
  https://agents.labs.bandwidth.com/api/v1/mcp/

2. Sign in. Complete the Labs sign-in and consent flow in your browser. Claude Code discovers CIMD automatically.

claude mcp login bandwidth_agents

3. Check the connection. After authentication, the status should be Connected.

claude mcp get bandwidth_agents

4. Open Claude Code. Enter /mcp inside the session, select bandwidth_agents, and inspect its status and tools. You can also authenticate from this menu.

claude

See Claude Code’s MCP guide for configuration scopes and client settings.

Run these commands in your terminal.1. Add the server. This saves the connection in your Codex configuration and starts OAuth setup when available. Complete the Labs sign-in and consent flow if prompted.

codex mcp add bandwidth_agents \
  --url https://agents.labs.bandwidth.com/api/v1/mcp/ \
  --oauth-client-registration cimd

2. Sign in if needed. If setup did not finish authentication, or you need to authorize again, run:

codex mcp login bandwidth_agents \
  --scopes voai \
  --oauth-client-registration cimd

3. Confirm the saved URL. This command displays configuration; use the next step to check the active connection.

codex mcp get bandwidth_agents

4. Open a new Codex session. Enter /mcp inside the session to inspect the server and available tools.

codex

See Codex’s MCP guide for OAuth and configuration options. If your CLI does not recognize the CIMD flag, update it before continuing.

Add a remote MCP server with https://agents.labs.bandwidth.com/api/v1/mcp/, including the trailing slash.
Select Streamable HTTP and OAuth if your client asks for transport and authentication methods.
Complete the Labs sign-in and consent flow in your browser.
Open your client’s tool list and confirm that the Agent Builder tools are available.

Your client must support CIMD. Use its built-in OAuth flow and let it manage token refresh; manually copying a REST token or configuring API-key headers will not establish this connection.

Get started

Use MCP

Workspaces

Agents

Calls and outcomes

Phone numbers

Resources

Authoring guidance

Documentation

Connect your client

​Connect your client

Connect your client