ba8fdf1a8c
Critical bug: MCP init tool reported success but didn't create .beads directory. It was using --db flag which tells bd to use an existing database elsewhere instead of creating a new one. Root cause: - bd_client.init() was calling _global_flags() which adds --db flag - bd init --db <path> uses existing db instead of creating new one - Result: init appeared to succeed but created nothing Fix: - Remove _global_flags() from init command - Only pass --actor flag (safe for init) - Do NOT pass --db flag to init (defeats the purpose) - Add explicit comment explaining why Testing: - Added test_init_creates_beads_directory() integration test - Verifies .beads directory is created in current working directory - Verifies database file has correct prefix - All 91 tests pass This was causing silent failures where agents thought they initialized bd but the .beads directory was never created. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
beads-mcp
MCP server for beads issue tracker and agentic memory system. Enables AI agents to manage tasks using bd CLI through Model Context Protocol.
Installing
git clone https://github.com/steveyegge/beads
cd beads/integrations/beads-mcp
uv sync
Add to your Claude Desktop config:
{
"mcpServers": {
"beads": {
"command": "uv",
"args": [
"--directory",
"/path/to/beads-mcp",
"run",
"beads-mcp"
],
"env": {
"BEADS_PATH": "/home/user/.local/bin/bd",
}
}
}
}
Environment Variables (all optional):
BEADS_PATH- Path to bd executable (default:~/.local/bin/bd)BEADS_DB- Path to beads database file (default: auto-discover from cwd)BEADS_ACTOR- Actor name for audit trail (default:$USER)BEADS_NO_AUTO_FLUSH- Disable automatic JSONL sync (default:false)BEADS_NO_AUTO_IMPORT- Disable automatic JSONL import (default:false)
Features
Resource:
beads://quickstart- Quickstart guide for using beads
Tools:
init- Initialize bd in current directorycreate- Create new issue (bug, feature, task, epic, chore)list- List issues with filters (status, priority, type, assignee)ready- Find tasks with no blockers ready to work onshow- Show detailed issue info including dependenciesupdate- Update issue (status, priority, design, notes, etc)close- Close completed issuedep- Add dependency (blocks, related, parent-child, discovered-from)blocked- Get blocked issuesstats- Get project statistics
Development
Run MCP inspector:
# inside beads-mcp dir
uv run fastmcp dev src/beads_mcp/server.py
Type checking:
uv run mypy src/beads_mcp
Linting and formatting:
uv run ruff check src/beads_mcp
uv run ruff format src/beads_mcp
Testing
Run all tests:
uv run pytest
With coverage:
uv run pytest --cov=beads_mcp tests/
Test suite includes both mocked unit tests and integration tests with real bd CLI.