Project memory for vibe coders. BirdBot gives your AI coding assistant persistent memory across sessions — no more re-explaining what you built last time.
Three tools, one SQLite file, zero cloud.
get_briefing— call at the start of every session to catch the AI up on your projectlog_session_end— call at the end to summarize what was built and what's openlog_decision— log architectural choices with their reasoning
Data lives at ~/.birdbot/birdbot.db. Nothing leaves your machine except API calls to Anthropic for briefing synthesis.
Sign up at console.anthropic.com and create a key. You'll need it in step 3.
Open ~/.claude/settings.json and add the birdbot entry inside "mcpServers":
{
"mcpServers": {
"birdbot": {
"command": "npx",
"args": ["-y", "birdbot-mcp"],
"env": {
"ANTHROPIC_API_KEY": "sk-ant-..."
}
}
}
}Replace sk-ant-... with your key from step 1.
Close and reopen Claude Code. BirdBot's three tools will appear in the MCP tools list.
Add this to your project's CLAUDE.md so Claude calls BirdBot automatically:
## Session protocol
- **Start of session:** call `get_briefing` with the project name before doing anything else
- **End of session:** call `log_session_end` with a 2-3 sentence summary of what was built, decided, and what's still open
- **When making architectural decisions:** call `log_decision` with the decision and reasoningOnce installed, just start a session and ask Claude to get your briefing:
"Get the BirdBot briefing for project 'my-app'"
BirdBot will synthesize your recent sessions and decisions into a sharp paragraph that catches Claude up instantly.
| Env var | Default | Description |
|---|---|---|
ANTHROPIC_API_KEY |
required | Your Anthropic API key |
BIRDBOT_MODEL |
claude-sonnet-4-6 |
Override the synthesis model |
All data is stored locally at ~/.birdbot/birdbot.db (SQLite). To reset a project's history, delete rows from the sessions and decisions tables.
MIT