
Sourcebook
io.github.maroondlabsPublished by GitHub account maroondlabsv0.9.5Updated Oct 24, 2026
Live codebase intelligence for AI agents: conventions, blast radius, import graphs, git insights.
Overview
Local MCP server that gives an AI assistant live codebase intelligence: repo structure, import graphs, blast radius, conventions and git co-change data.
- What you can do
- Query repository structure, conventions and a Repo Truth Map for the project directory
- Inspect import graphs, hub files and the blast radius of a change
- Look up git co-change companions and which files historically change together
- Check a diff for completeness: missing test files, sibling modules and related config
- Run AI-assisted semantic analysis of a diff when an Anthropic API key is configured
- When to use it
- Useful when an assistant edits code in a git repository and you want it to know which other files a change probably touches, or to check a diff for missing tests and dependents before committing. Best suited to TypeScript/JavaScript, Python and Go projects.
- Requirements
- Runs locally over stdio, started with npx sourcebook serve and pointed at a project directory. Needs Node.js and a local git repository with history. The AI semantic layer requires the ANTHROPIC_API_KEY environment variable; the rules-based layer needs no configuration.
Installation
In SourceWeft
- Open Sourcebook in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
sourcebook
Catches the files your AI agent forgot to change.
A safety layer for code changes. sourcebook analyzes git diffs for completeness — flags files that should've been modified but weren't. Rules-based structural detection plus AI-powered semantic analysis. Zero false positives on clean diffs.
What It Catches
Your AI agent changed the handler. Did it update the test? The sibling module? The config that references the old value?
sourcebook checks your diff against the repo's actual structure:
- Missing test files — source file changed, test file didn't
- Sibling modules — files that import or are imported by what you changed
- Co-change companions — files that historically change together in git commits
- Hub file blast radius — you touched something with 50+ dependents
With --ai: cross-module semantic relationships, field renames that need migrations, stale validation logic.
Key Stats
Four Surfaces
1. CLI
Run it on any diff. No setup required.
2. Claude Code Hooks
One command wires up pre-commit hooks. Agent edits a file, sourcebook checks the diff, agent sees what's missing — all before the commit lands.
3. MCP Server
Published on the official MCP registry. Agents can query repo structure, blast radius, conventions, and co-change data on demand.
Add to your MCP client:
4. GitHub App (coming soon)
Automated completeness checks on every pull request. Join the waitlist.
Commands
How It Works
Layer A — Rules-based (no LLM, <1 second)
- Co-change analysis — mines git history for files that change together. If you touched
auth.tsand it changes withsession.tsin 88% of commits, sourcebook flagssession.ts. - Test file detection — maps source files to test files via naming conventions and co-change history.
- Import graph — builds a dependency graph and checks whether files that import (or are imported by) your changed files also need updates.
- Hub detection — flags when you've modified a file with high fan-in (many dependents). These changes have blast radius.
Layer B — AI-powered (~$0.012/run)
Sends the diff plus dependency context to Claude Sonnet. Catches semantic relationships Layer A can't see — field renames that need migrations, validation logic that assumes old schemas, cross-module dependencies with no import link.
Every AI suggestion requires a dependency citation. Hallucinated file paths are filtered out. The completeness gate ensures zero false positives: if the diff is actually complete, Layer B stays silent.
Configuration
No other configuration needed. sourcebook reads your repo's git history and file structure directly.
Language Support
Research
Built on real benchmarks, not vibes:
- Check validation results — methodology and accuracy data
- Benchmark: 19 tasks, 10 repos, 4 languages — controlled agent performance testing
- Why auto-generated context makes agents worse — the ETH Zurich finding that shaped our approach
License
BSL-1.1 — source-available, free to use, cannot be offered as a hosted service. Converts to MIT on 2030-03-25. See LICENSE for details.
sourcebook.run · GitHub · npm · @maroond_
Source: README.md at commit d289440
Tools
0Version history
1- v0.9.5LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.