When to Use MCP
Use MCP server when CLI is unavailable:- Claude Desktop (no shell access)
- Sourcegraph Amp without shell
- Other MCP-only environments
Installation
Using uv (Recommended)
Using pip
Configuration
Claude Desktop (macOS)
Add to~/Library/Application Support/Claude/claude_desktop_config.json:
Claude Desktop (Windows)
Add to%APPDATA%\Claude\claude_desktop_config.json:
Sourcegraph Amp
Add to MCP settings:VS Code / GitHub Copilot
Create.vscode/mcp.json in your project:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Code/User/mcp.json |
| Linux | ~/.config/Code/User/mcp.json |
| Windows | %APPDATA%\Code\User\mcp.json |
Available Tools
The MCP server exposes these tools:| Tool | Description |
|---|---|
ready | Show ready work (no open blockers) |
list | List issues with filters |
show | Show issue details, dependencies, and dependents |
create | Create a new issue |
claim | Atomically claim an issue |
update | Update an issue |
close / reopen | Close or reopen an issue |
dep | Manage dependencies |
comment / comments | Add or list comments |
note | Append to an issue’s notes |
blocked | Show blocked issues and their blockers |
stats / context | Database stats and workspace context |
admin | Administrative operations |
discover_tools / get_tool_info | Tool discovery and schemas |
bd dolt push /
bd dolt pull).
Usage
Once configured, use naturally:bd commands.
Trade-offs
| Aspect | CLI + Hooks | MCP Server |
|---|---|---|
| Context overhead | ~1-2k tokens | 10-50k tokens |
| Latency | Direct calls | MCP protocol |
| Setup | Hooks config | MCP config |
| Availability | Shell required | MCP environments |
Troubleshooting
Server won’t start
Check ifbeads-mcp is in PATH:
Tools not appearing
- Restart Claude Desktop
- Check MCP config JSON syntax
- Verify server path
Permission errors
See Also
- Claude Code - CLI integration
- Installation - Full install guide