Sourcebook
Wire live repo intelligence—conventions, import graphs, blast radius, and git context—into your agent while you change code.
Overview
Sourcebook is an MCP server for the Build phase that exposes live codebase intelligence—conventions, blast radius, import graphs, and git insights—to coding agents.
What is this MCP server?
- Live codebase intelligence: conventions, blast radius, import graphs
- Git insights tied to the repo the agent is working in
- Helps agents estimate change impact before wide edits
- Published MCP server package version 0.9.5 on GitHub maroondlabs/sourcebook
- Developer Tools integration for Claude Code-style workflows
- MCP server version 0.9.5 per server.json
- Capability themes: conventions, blast radius, import graphs, git insights
What problem does it solve?
Agents rename APIs or move modules without seeing import fan-out, style rules, or recent churn, so solo builders merge fixes they did not know they needed.
Who is it for?
Solo developers on non-trivial repos who want impact-aware suggestions before merging agent-generated changes.
Skip if: Empty repos, greenfield one-file scripts, or teams that only need documentation search with no code graph.
What do I get? / Deliverables
After Sourcebook MCP is registered, refactors and feature work can reference dependency graphs, convention hints, and git insights in the same agent session.
- Agent-accessible convention, graph, and blast-radius signals for the active repo
- Richer git-aware context for implementation and review prompts
Recommended MCP Servers
Journey fit
Sourcebook shines while you are actively building and refactoring, when wrong assumptions about imports and conventions cause the most rework. Agent-tooling is the canonical shelf because the server exists to augment coding agents with structured codebase signals, not to ship a customer-facing feature.
How it compares
In-repo codebase intelligence MCP, not an enterprise data catalog like Marmot.
Common Questions / FAQ
Who is Sourcebook MCP for?
Solo and indie builders whose agents need dependency, convention, and git context while editing a real codebase, not just single-file snippets.
When should I use Sourcebook MCP?
Use it during build and ship prep when planning refactors, assessing blast radius, or aligning agent output with repo conventions and recent git activity.
How do I add Sourcebook MCP to my agent?
Install and register the Sourcebook MCP server from the maroondlabs/sourcebook repository following your agent’s MCP config (stdio or documented transport), then enable it for the workspace root.