Skip to main content
Get your MCP API key Connect btca to Cursor, Claude Code, Codex, and other MCP-compatible tools so they can query the right repos. There are two options:
  • Cloud MCP: Use your btca subscription to give coding tools access to btca-managed resources.
  • Local MCP: Run btca entirely on your machine and expose local resources to coding tools.
To scaffold configs automatically, run:
  • btca mcp local
For cloud MCP, use the manual config snippets below with your API key. The hosted MCP endpoint is optimized for request/response tool calls. Long-lived SSE notification streams are disabled in cloud deployments.

Add to AGENTS.md

Add the following section to your project’s AGENTS.md:

Configure your agent

Each agent supports both cloud (HTTP) and local (stdio) MCP servers. Use the examples below to pick the option you want.

Cursor

Cloud (HTTP) in .cursor/mcp.json:
Reference: Cursor MCP docs Local (stdio) in .cursor/mcp.json:

Codex

Cloud (HTTP) in config.toml, and add the API key to your environment variables (for example in .zshenv):
Reference: Codex MCP docs Local (stdio) via CLI:

Claude Code

Cloud (HTTP) in the CLI:
Reference: Claude Code MCP docs Local (stdio) in the CLI:

OpenCode

Cloud (HTTP) in opencode.json:
Reference: OpenCode MCP docs Local (stdio) in opencode.json: