Logbook MCP

@cocaxcode/logbook-mcp

Your developer logbook, always one sentence away.

Notes · TODOs · Reminders · Code scanning · Full-text search · Native CLI · Obsidian-only

⚠️ v2.0 breaking change: SQLite eliminado. v2 sólo soporta backend Obsidian. Datos en ~/.logbook/logbook.db (v1) no se migran automáticamente — quedan intactos en disco. Si necesitas acceso a ellos, mantente en @cocaxcode/logbook-mcp@0.4. Tools 10→5 (con shims deprecated). Ver CHANGELOG.md para detalles.

Overview · Usage · Installation · Features · Tool Reference · Storage · Architecture

---

Quick Overview

logbook-mcp is an MCP server that turns your AI assistant into a persistent developer logbook. Capture decisions, track TODOs, set reminders, scan code TODOs, and search everything with full-text search — without leaving your editor.

It auto-detects your git project, stores everything locally, and works with any MCP-compatible client: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Codex CLI, or Gemini CLI. All data stays on your machine — nothing is synced, nothing is tracked, nothing leaves your disk. Notes are scoped per-project automatically, but you can search globally across all your projects at any time.

Two storage modes: SQLite (default, zero config) or Obsidian (markdown files with frontmatter, visible in your Obsidian vault with Graph View, Dataview, Tasks, and Calendar). Switching from SQLite to Obsidian auto-migrates your data on startup.

---

Just Talk to It

No commands to memorize. Just say what you need.

Capture notes

"I decided to use JWT instead of sessions for scalability"

→ Saved as a decision — retrievable months from now

"The CI is failing due to a timeout in integration tests" → Captured as a blocker — shows up when you review activity

Track TODOs

"TODO: implement email validation"

→ Created with auto-inferred topic

"Add these: fix token refresh. update deps. add rate limiting" → 3 TODOs created at once, each categorized

"Mark 5 and 8 as done" → Both completed

"What's pending across all projects?" → Global view of everything, including code TODOs

Set reminders

"Remind me tomorrow to deploy"

→ One-time reminder

"Remind me every Tuesday to review PRs" → Recurring weekly — auto-acknowledged after each session

"Remind me on weekdays to check the CI" → Monday to Friday

Search anything

"Why did we choose JWT?"

→ Finds the decision note, even months later

"Search everything about auth" → FTS5 search across all notes and TODOs

---

Installation

Claude Code (recommended)

claude mcp add --scope user logbook -- npx -y @cocaxcode/logbook-mcp@latest --mcp

With Obsidian mode:

claude mcp add --scope user logbook -- npx -y @cocaxcode/logbook-mcp@latest --mcp --storage obsidian --dir "/path/to/vault/logbook"

Claude Desktop

Add to your claude_desktop_config.json:

{

"mcpServers": { "logbook-mcp": { "command": "npx", "args": ["-y", "@cocaxcode/logbook-mcp@latest", "--mcp"] } } }

With Obsidian mode:

{

"mcpServers": { "logbook-mcp": { "command": "npx", "args": [ "-y", "@cocaxcode/logbook-mcp@latest", "--mcp", "--storage", "obsidian", "--dir", "/path/to/vault/logbook" ] } } }

Config file locations

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

Cursor, Windsurf, VS Code, Codex CLI, Gemini CLI

Cursor — add to .cursor/mcp.json:

{

"mcpServers": { "logbook-mcp": { "command": "npx", "args": ["-y", "@cocaxcode/logbook-mcp@latest", "--mcp"] } } }

Windsurf — add to .windsurf/mcp.json:

{

"mcpServers": { "logbook-mcp": { "command": "npx", "args": ["-y", "@cocaxcode/logbook-mcp@latest", "--mcp"] } } }

VS Code — add to .vscode/mcp.json:

{

"servers": { "logbook-mcp": { "command": "npx", "args": ["-y", "@cocaxcode/logbook-mcp@latest", "--mcp"] } } }

Codex CLI:

codex mcp add logbook-mcp -- npx -y @cocaxcode/logbook-mcp@latest --mcp

Gemini CLI — add to .gemini/settings.json:

{

"mcpServers": { "logbook-mcp": { "command": "npx", "args": ["-y", "@cocaxcode/logbook-mcp@latest", "--mcp"] } } }

---

Configuration

logbook-mcp supports three ways to configure storage, with this priority order:

1. CLI args (highest priority): --storage obsidian --dir "/path" --workspace "name"
2. Environment variables: LOGBOOK_STORAGE, LOGBOOK_DIR, LOGBOOK_WORKSPACE
3. Config file: ~/.logbook/config.json (auto-created on first run)

{

"storage": "sqlite", "dir": null, "workspace": null, "autoMigrate": true }

Switching from SQLite to Obsidian

Just change the config and restart. If autoMigrate is true (default), your existing SQLite data is automatically migrated to Obsidian on the next startup. No manual steps needed.

You can also check the current status with logbook_setup action:status.

---

Features

7 built-in topics

Every note, TODO, and reminder is categorized automatically by your AI, or you can specify a topic explicitly.

Custom topics can be created at any time — just say *"create a topic called security"*.

Custom topics with type, folder, and dashboard

Topics can define their own behavior (kind), Obsidian folder, and whether they appear in the project dashboard (index.md):

• kind: `note` (default) — each entry is an individual .md file
• kind: `todo` — entries are checkboxes in a consolidated .md file
• show_in_index: `true` (default) — adds a Dataview section and quick link to index.md
• show_in_index: `false` — topic exists but is hidden from the dashboard

"Create a topic called incident with its own folder"

→ logbook_topics action:add name:"incident" kind:"note" folder:"incidents" → Entries saved to: project/incidents/2026-03-24-server-down.md → Dashboard updated with Incidents section

"Create a topic called sprint-task as todo type" → logbook_topics action:add name:"sprint-task" kind:"todo" folder:"sprint" → Entries saved to: project/sprint.md (as checkboxes)

"Create a private topic not shown in the dashboard" → logbook_topics action:add name:"internal" kind:"note" folder:"internal" show_in_index:false → Entries saved to: project/internal/ (not visible in index.md)

Without a folder, entries go to the default notes/ or todos/ directory. The dashboard (index.md) is auto-regenerated when a topic with show_in_index: true and folder is created.

Code TODO scanning

Your TODO, FIXME, HACK, and BUG comments are detected via git grep and shown alongside manual TODOs:

feature (2)

[ ] #12 [manual] Implement email validation [code] TODO: add OAuth support — src/auth/service.ts:45

fix (3) [ ] #8 [manual] Token doesn't refresh [code] FIXME: handle null case — src/users/controller.ts:78 [code] BUG: race condition — src/chat/gateway.ts:112

When a code TODO disappears from source (because you fixed it), logbook detects it automatically and marks it as resolved.

Reminders

Both one-time and recurring patterns are supported:

Recurring reminders auto-acknowledge after being shown once per day. One-time reminders that were missed show as overdue.

Tip: logbook-mcp exposes an MCP Resource (logbook://reminders) that clients can load on session start. In Claude Code and Claude Desktop, reminders appear automatically without asking. In other clients, just say *"any reminders?"*.

Full-text search (FTS5)

Search across all notes and TODOs instantly, powered by SQLite FTS5. Filter by topic, type, project, or search globally across all projects.

Batch operations

"Add: validate email. fix token. update deps"     → 3 TODOs created

"Mark 5, 8, and 12 as done" → 3 TODOs completed "Delete TODOs 3 and 7" → 2 TODOs removed

Smart project detection

logbook-mcp auto-detects which git project you're in via git rev-parse. No config needed — it scopes queries to the current project by default, with a global option to see everything.

---

Tool Reference

logbook_note — Add a note

logbook_todo — Full TODO management

action: `add` — Create TODOs

| Param | Type | D