Connect your AI assistant

The running API serves BBM-Atlas's tools over MCP at /mcp (Streamable HTTP), so your assistant works on the same repositories, facts and flags as the CLI and the web console. With the server from Index and search, the address is http://127.0.0.1:8000/mcp. The console's overview page shows it, with setup ready to copy.

From your project's folder, register the endpoint in the project's .mcp.json:

bbm-atlas mcp install --url http://127.0.0.1:8000/mcp# When the server requires API keys: the key stays in your environment,# and .mcp.json only names the variableexport BBM_ATLAS_API_KEY=…bbm-atlas mcp install --url http://127.0.0.1:8000/mcp --api-key-env BBM_ATLAS_API_KEY

bbm-atlas mcp uninstall removes the entry again.

The BBM-Atlas extension offers the tools to Copilot's agent mode by itself. Without it, add the server to .vscode/mcp.json:

{  "servers": {    "bbm-atlas": {      "type": "http",      "url": "http://127.0.0.1:8000/mcp"    }  }}

When the server requires API keys, have VS Code ask for the key rather than writing it into the file:

{  "inputs": [    { "type": "promptString", "id": "bbm-atlas-key", "description": "BBM-Atlas API key", "password": true }  ],  "servers": {    "bbm-atlas": {      "type": "http",      "url": "https://atlas.example.com/mcp",      "headers": { "Authorization": "Bearer ${input:bbm-atlas-key}" }    }  }}

Any host that speaks MCP over HTTP connects to the same address. In Cursor, for example, .cursor/mcp.json:

{  "mcpServers": {    "bbm-atlas": { "url": "http://127.0.0.1:8000/mcp" }  }}

A key goes in an Authorization: Bearer <key> header (or X-API-Key), in whatever way the host sets headers.

bbm-atlas mcp serve runs the tools over stdio instead, as a process the host starts. bbm-atlas mcp install without --url registers it with Claude Code.

Each tool checks the same permission as its REST route, so a key or role that can't do something over REST can't do it over MCP either.