MCP Server

Connect the btca MCP server to your agents

Get your MCP API key

Use the btca MCP server to query resources from your agent of choice. There are two options:

• Cloud MCP: Runs on btca’s hosted servers and uses your btca subscription. Requires an API key.
• Local MCP: Runs entirely on your machine using local resources. No API key required.

To scaffold configs automatically, run:

• btca mcp local

For cloud MCP, use the manual config snippets below with your API key.

Add to AGENTS.md

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

# btca MCP Usage Instructions

btca runs a cloud subagent that searches open source repos

Use it whenever the user says "use btca", or when you need info that should come from the listed resources.

## Tools

The btca MCP server provides these tools:

- `listResources` - List all available documentation resources
- `ask` - Ask a question about specific resources

## resources

The resources available are defined by the end user in their btca dashboard. If there's a resource you need but it's not available in `listResources`, proceed without btca. When your task is done, clearly note that you'd like access to the missing resource.

## Critical Workflow

**Always call `listResources` first** before using `ask`. The `ask` tool requires exact resource names from the list.

### Example

1. Call listResources to get available resources
2. Note the "name" field for each resource (e.g., "svelteKit", not "SvelteKit" or "svelte-kit")
3. Call ask with:
   - question: "How do I create a load function?"
   - resources: ["svelteKit"]

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:

{
	"mcpServers": {
		"server-name": {
			"url": "https://btca.dev/api/mcp",
			"headers": {
				"Authorization": "Bearer ak..."
			}
		}
	}
}

Reference: Cursor MCP docs

Local (stdio) in .cursor/mcp.json:

{
	"mcpServers": {
		"btca-local": {
			"command": "bunx",
			"args": ["btca", "mcp"]
		}
	}
}

Codex

Cloud (HTTP) in config.toml, and add the API key to your environment variables (for example in .zshenv):

[mcp_servers.btca]
bearer_token_env_var = "BTCA_API_KEY"
enabled = true
url = "https://btca.dev/api/mcp"

Reference: Codex MCP docs

Local (stdio) via CLI:

codex mcp add btca-local -- bunx btca mcp

Claude Code

Cloud (HTTP) in the CLI:

claude mcp add --transport http better-context https://btca.dev/api/mcp \
 --header "Authorization: Bearer ak..."

Reference: Claude Code MCP docs

Local (stdio) in the CLI:

claude mcp add --transport stdio btca-local -- bunx btca mcp

OpenCode

Cloud (HTTP) in opencode.json:

{
	"$schema": "https://opencode.ai/config.json",
	"mcp": {
		"better-context": {
			"type": "remote",
			"url": "https://btca.dev/api/mcp",
			"enabled": true,
			"headers": {
				"Authorization": "Bearer ak..."
			}
		}
	}
}

Reference: OpenCode MCP docs

Local (stdio) in opencode.json:

{
	"$schema": "https://opencode.ai/config.json",
	"mcp": {
		"btca-local": {
			"type": "local",
			"command": ["bunx", "btca", "mcp"],
			"enabled": true
		}
	}
}