Codeledger MCP server

CodeLedger

Give AI coding agents the right repo context before they start - then verify what changed.

CodeLedger is local-first context control for AI coding agents. It scans a repository, selects a bounded task-relevant set of files, and writes an evidence-backed context bundle before the agent begins work.

Works with Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and other CLI or MCP-compatible coding agents.

Try It

npm install -g @codeledger/cli
cd your-project
codeledger ready --task "Fix null handling in user service"

CodeLedger initializes the repo if needed, refreshes the index, and creates the task-specific bundle at .codeledger/active-bundle.md. Your agent reads that artifact first so it starts with the files most relevant to the task.

Runtime analysis is local by default. Installing or updating may fetch packages or release artifacts from npm and GitHub Releases; CodeLedger runtime analysis does not send your source code through CodeLedger telemetry by default.

Example Benchmark

Example result from a mid-sized Node.js service. Results vary by repository, task, agent, and scenario.

Do not take the benchmark on faith - measure CodeLedger on your own repo:

codeledger compare \
  --scenario .codeledger/harness/scenarios/auth-rate-limit.json \
  --guided

If CodeLedger improves your coding-agent workflow, star the repo to follow releases and help other developers discover it.

Start Here

• Getting Started
• CLI Reference
• How It Works
• MCP Server
• Feature Tiers
• Security
• Contributing
• Latest Release
• npm package

How It Works

structure, churn, tests, contracts, and task keywords.

1. CodeLedger scans the repo for deterministic local signals such as dependency

changed and whether the selected context was useful.

1. It ranks and packs a bounded set of task-relevant files.
2. It writes .codeledger/active-bundle.md for your coding agent.
3. After work, verification, receipts, and session summaries help show what

Same task plus same repo state produces the same file ranking behavior.

Core Capabilities

inference, bounded budgets, blast-radius hints, and co-change context.

• Give agents the right context: deterministic file selection, scope

and handoff/recovery commands.

• Keep work continuous: session summaries, checkpoints, mid-session refine,

detection, and multi-agent conflict checks.

• Keep agents inside the task: scope contracts, intent governance, loop

exports, and release evidence.

• Prove what happened: review intelligence, receipts, provenance, audit

For the full command surface, see the CLI Reference.

Agent Integration

Claude Code can use CodeLedger hooks after codeledger ready initializes the repo. Cursor, Codex, GitHub Copilot, Gemini CLI, Aider, Windsurf, and other agents can read CLAUDE.md plus .codeledger/active-bundle.md, or use the repo-local wrappers when available.

CodeLedger also includes an MCP server for supported tiers:

codeledger mcp start
codeledger mcp status

See MCP Server and Feature Tiers for setup and tier details.

Trust And Verification

Shortened. The full README is on GitHub.