GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
Logbook
Overview
Description from the maker (original English)
Git-history memory for coding agents: reverts, weakened tests, hot spots, and unreviewed notes.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiEarly↓ 1.3K/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"logbook": {
"command": "npx",
"args": [
"-y",
"@promptwheel/logbook-mcp"
]
}
}
}Run this in your terminal
claude mcp add logbook -- npx -y @promptwheel/logbook-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"logbook": {
"command": "npx",
"args": [
"-y",
"@promptwheel/logbook-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"logbook": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@promptwheel/logbook-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account promptwheel-ai, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 4932 servers in this category
- Published to the registry more recently than 93% of the other 4932 servers in this category
- Basic checks equal to or better than 100% of the other 4932 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Logbook safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.8.0) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
logbook
Git history is large. When coding agents do not inspect it, they can re-propose approaches a repository already rejected.
Logbook turns a repository's Git history into memory an agent can use: a deterministic recall layer (hotspots, reverted approaches, suppressions, assertion weakening, and bounded history queries) plus durable notes an agent writes down after it investigates why a change happened.
Everything runs locally. The CLI has zero npm dependencies, reads raw Git objects for evidence checks, and never sends repository data anywhere. Node.js 18 or newer is required.
npx -y @promptwheel/logbook@latest initinit analyzes the repo, writes the history artifacts, and installs a compact workflow in AGENTS.md, CLAUDE.md, or .cursorrules so the agent reads history before it plans: read LOGBOOK.md, page each task path with context --file, verify leads with git show, refresh, audit, and annotate what it verified. The same workflow ships as an agent skill in plugin/skills/logbook/SKILL.md.
Its output, shortened:
1,326 commits · 322 files · 7.3 years · 354 authors✓ wrote LOGBOOK.md hotspots · do-not-retry · suppression ledger ✓ wrote events.jsonl 1,326 structured events
The examples below use logbook as the binary name. Run them through the exact package above, or install @promptwheel/logbook@latest locally or globally.
Quick start
logbook # refresh the history artifactslogbook context --file src/cache.ts --revert # bounded history for a path logbook audit # what is still suppressed, and since when logbook query --json --file src/cache.ts # the same events as JSONL logbook doctor # read-only artifact and wiring health
context returns history in pages of at most 20 events and 8 KiB; repeat the identical filters with each NEXT cursor until END complete.
When an agent investigates why a prior change happened during real work, it can preserve the result immediately, with no prompt or human gate:
logbook annotate <commit> "why this approach was rejected" --by codexThe note is durably appended to annotations.jsonl and appears in LOGBOOK.md before the command exits. It is always labeled machine-authored and unreviewed and is bounded in the startup digest. An optional exact quote can be attached with --span, --side, and (for diff evidence) --evidence-file; a quote that does not ground in raw Git objects is rejected rather than guessed.
What it stores
| Path | Purpose |
|---|---|
LOGBOOK.md | Bounded history brief for agents: hotspots, do-not-retry reverts, suppressions, weakened assertions, and fragile areas |
events.jsonl | Structured deterministic history events for tools and queries |
annotations.jsonl | Durable machine-authored notes, shown in the digest as explicitly unreviewed leads |
Commit annotations.jsonl to share the notes with the team, or add it to .gitignore to keep them local to one checkout.
History queries and context economics
context preserves filtered query order but emits pages of at most 20 events and 8 KiB. A cursor is bound to the repository HEAD, filters, analysis window, and ordered event set, so a stale or edited cursor is rejected instead of silently drifting.
The history scan is cached in bounded windows. On a history of tens of thousands of commits a cold run takes tens of seconds, a warm run that reuses the ledger on disk is well under a second, and a repeat call with an unchanged HEAD in an MCP session is milliseconds. LOGBOOK_NO_CACHE=1 forces a rebuild; LOGBOOK_WINDOW=N tunes the window.
In a random 400-repo sample of the top 2,500 GitHub repositories, the median LOGBOOK.md was about 1,000 estimated tokens while the median full git log was 82× larger. See context economics and the bounded context format.
Integrate: CLI, MCP, or import
Three surfaces over the same deterministic history layer:
- CLI + JSON.
logbook query --json(filtered, 200 rows unless you pass--limit) andlogbook --json(the full ledger) emit JSONL you can shell from any language.logbook audit --jsonreturns the live suppressions as one array. The JSON is cache-invariant (byte-identical with and withoutLOGBOOK_NO_CACHE=1), so it is safe to parse in CI. - MCP.
@promptwheel/logbook-mcp(binlogbook-mcp) serves the history to an agent over the Model Context Protocol: a Claude Code or other MCP client reads hotspots, do-not-retry reverts, and suppression signals without shelling anything. - Import. The package is importable and importing it never runs the CLI.
queryEvents,analyze,auditHead, andhotspotsare exported for advanced in-process use; the scan and cache entry points take explicit options, so the CLI and MCP are the first-class surfaces for most integrations.
The paired check engine, promptwheel, has the matching surface. Both are described in its INTEGRATE.md.
Evidence status
An internal six-task planning experiment on history-dense repos found that agents without history re-proposed already-tried or already-finished work in 4 of 6 repos and 0 of 6 with LOGBOOK.md in context, at about 4.7k extra plan tokens. A later sealed held-out screen on ten new tasks found no advantage over a strong raw-Git instruction, and traced the gap to retrieval rather than the index. The calibrated claim is: valuable on sufficiently difficult, history-dense tasks; not universally better. Details and limits are in wrong-work-benchmark.md and does-it-change-agent-behavior.md.
Honest scope
- Findings are leads, not verdicts. A suppression means "look here," not misconduct.
- Detection is deterministic regex over commit subjects and diffs. It misses history erased by squash/rebase and anything never committed.
- Shallow clones starve historical analysis; fetch the missing history before treating absence as evidence.
- Code maps explain where code is. Logbook focuses on what happened over time.
Command reference
logbook init [path]logbook [path] [--json] logbook audit [path] [--json [--file P ...] [--ref REF]] logbook doctor [path] logbook query [path] [filters] [--json] logbook context [path] [filters] [--cursor TOKEN] logbook annotate SHA "WHY" [optional evidence] [--by WHO]
logbook --help lists every filter and option.
Upgrading
0.11.0 removes logbook refine, logbook journey, and --out. Both commands now fail with not a git repository, and --out is an unknown option. Artifacts always go to the repository root. The analyze result no longer carries first, last, threshold, mentor, abyss, winter, or trials, and renderJourneyAnsi, journeyBeats, almanacStats, GATE_PAT, and MENTOR_PAT are no longer exported. The event and --json shapes, the five MCP tools, and doctor did not change. MCP server 0.8.0 requires this core.
0.10.0 removed the experimental reviewed-decision layer and the OKF export: annotate-draft, pending, accept/accept-draft, accept-lead, reject-lead, check, publish, outcomes, and export. Files that layer left behind (.logbook/, decision-cards.jsonl, annotation-reviews.jsonl) are ignored and can be deleted by hand.
From any release, a normal refresh rewrites a ## Repo memory block that an earlier release generated, so doctor passes after an upgrade. User-edited blocks are never touched. Existing annotations.jsonl rows stay unreviewed digest notes. A JOURNEY.md left by a release before 0.9.7 is ignored and can be deleted. If 0.8 wrote annotations to a custom directory, move that annotations.jsonl to the repository root. Earlier notes are in the git history of this file.
The logbook records what happened; the check verifies what holds
Logbook tells you what history says. promptwheel is the check that verifies whether today's claimed improvement came from the code rather than moving the goalposts.
Apache 2.0.