Logbook Mcp
Keep a structured dev logbook—notes, TODOs, standups, decisions, debug sessions, and reminders—inside your agent workflow.
Overview
io.github.cocaxcode/logbook-mcp is a MCP server for the Operate phase that lets agents maintain notes, TODOs, standups, decisions, debug sessions, and reminders in a developer logbook.
What is this MCP server?
- Developer logbook MCP: notes, TODOs, standups, decisions, debug sessions, reminders
- stdio npm package @cocaxcode/logbook-mcp (v0.8.11)
- Gives agents a durable place to record context that otherwise lives in scattered chats
- Supports standup-style summaries and decision logs for solo accountability
- Debug session tracking aligned with post-ship troubleshooting
- Capabilities: notes, TODOs, standups, decisions, debug sessions, reminders
- Package @cocaxcode/logbook-mcp v0.8.11
- stdio npm transport
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders lose decisions and debug context between agent sessions because nothing durable captures what happened last time.
Who is it for?
Indie devs who run long agent sessions across days and need lightweight engineering diary tooling without another SaaS tab.
Skip if: Teams that already mandate a company wiki with strict compliance retention and block local or agent-written logs.
What do I get? / Deliverables
After registration, your agent can append and retrieve logbook entries so iteration builds on recorded TODOs, standups, and debug notes.
- Persistent notes, TODOs, and reminders the agent can query in later sessions
- Standup and decision records for solo delivery accountability
- Debug session trails that speed up Operate-phase fixes
Recommended MCP Servers
Journey fit
Persistent engineering memory matters most in Operate when you iterate on what shipped, but logbook entries also support every phase. Iterate is the canonical shelf for capturing decisions, debug trails, and follow-ups that inform the next change cycle.
How it compares
Agent-facing dev logbook MCP, not a monitoring dashboard or automated error tracker.
Common Questions / FAQ
Who is io.github.cocaxcode/logbook-mcp for?
It is for solo builders and small teams who want their AI coding agent to read and write structured dev notes, TODOs, and debug history via MCP.
When should I use io.github.cocaxcode/logbook-mcp?
Use it whenever you iterate on a shipped product—or any long build—and need standups, decisions, and reminders to persist across sessions.
How do I add io.github.cocaxcode/logbook-mcp to my agent?
Install @cocaxcode/logbook-mcp from npm, configure stdio MCP in your host, and point storage paths per the repo README so tools can manage your logbook.