Developer logbook MCP server. Notes, TODOs, standups, decisions, debug sessions, reminders.
Logbook MCP server exists for a simple reason — assistants are far more useful when they can act on Logbook directly instead of describing what you should do. Developer logbook MCP server. Notes, TODOs, standups, decisions, debug sessions, reminders.
Your developer logbook, always one sentence away.
Once Logbook is connected, these are the calls the assistant has available:
macOS — ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows — %APPDATA%\Claude\claude_desktop_config.jsonLinux — ~/.config/Claude/claude_desktop_config.jsonkind — note** (default) — each entry is an individual .md fileshow_in_index — true** (default) — adds a Dataview section and quick link to index.mdTopic — Purposefeature — New functionalityfix — Bug fixeschore — Maintenance, CI/CD, refactoringidea — Future proposalsdecision — Architecture choicesblocker — Things blocking progressBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Logbook's toolset — macOS, Windows, Linux and 11 more — is a fair guide to whether it matches your workflow. It is maintained by cocaxcode; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
| kind | note** (default) — each entry is an individual .md file |
| show_in_index | true** (default) — adds a Dataview section and quick link to index.md |
| Topic | Purpose |
| feature | New functionality |
| fix | Bug fixes |
| chore | Maintenance, CI/CD, refactoring |
| idea | Future proposals |
| decision | Architecture choices |
| blocker | Things blocking progress |
| reminder | Time-based reminders |
| Pattern | Example |
{
"mcpServers": {
"logbook-mcp": {
"command": "npx",
"args": ["-y", "@cocaxcode/logbook-mcp@latest", "--mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.