Deterministic context selection for AI coding agents. Local memory that compounds across sessions.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
What problem are we solving?
The Problem β AI coding agents waste 40β60% of their context window on irrelevant files. Every session starts cold. Institutional knowledge lives in people's heads and disappears when they leave. There is no risk signal before a merge.
The Solution β CodeLedger is a deterministic context control plane for software development. It scores every file in a repository, selects only what the current task requires, captures outcomes, and promotes successful patterns into reusable institutional memory.
The Intelligence Layer β The Task Intelligence Engine does not start from zero. It is seeded from day one with a curated ontology pack of golden patterns β distilled from peer organizations and leading engineering teams at organizations including Google, SAP, and Salesforce. As your team uses CodeLedger, your own earned patterns layer on top, making the system progressively more tailored to your codebase, your conventions, and your standards.
The Principle β No cloud. No training pipeline. No behavior change required. Engineering management installs it once. Every developer and every AI agent benefits automatically β from collective intelligence on day one, and from your own institutional memory from day two onward.
Logs are history. Ledger is intelligence.
CodeLedger turns every coding action into a persistent, compounding asset.
Without CodeLedger:
With CodeLedger:
This is not another AI tool. This is a Context Control Plane for your repo.
Works with: Claude Code | Cursor | Codex | GitHub Copilot | Gemini CLI | Any CLI-based agent
Over time, your repo builds its own intelligence layer.
CodeLedger helps in two ways:
β‘ Now β Assembles the minimal context needed for your current task. Fewer irrelevant files, fewer retries, faster execution.
π Next β Captures what worked and builds reusable memory so future tasks start smarter. Successful patterns compound into institutional knowledge.
CodeLedger includes an MCP server that gives Claude, Cursor, and Windsurf direct access to your repo's memory:
Tools available to agents:
query_ledger β Search for verified patterns before codingget_active_context β Get the task-specific context bundlerecord_interaction β Report outcomes for memory compoundingMCP integration requires Team or Enterprise tier. See Feature Tiers.
Generate a repo-local engineering dashboard from your Context Ledger:
The dashboard shows: system health, integrity signals, quality metrics, pattern reuse intelligence, and estimated engineering value β all derived from real execution evidence.
Full dashboard requires Team or Enterprise tier. Individual tier receives a placeholder with teaser stats.
Prevent silent merge failures where code compiles but types or config are semantically broken:
Catches removed types with active importers, config fields accessed but missing from defaults, and name collisions across packages.
| Feature | Individual (Free) | Team | Enterprise |
|---|---|---|---|
| Context selection + scanning | β | β | β |
| Prompt coaching (automatic) | β | β | β |
CI enforcement (ci check --json) | β | β | β |
| Local evidence + pattern capture | β | β | β |
| Semantic merge verification | β | β | β |
| Full Engineering Dashboard | π | β | β |
| MCP Server (AI agent memory) | π | β | β |
| Team coordination (claims, leases) | π | β | β |
| Pattern sync (GitHub mirror) | π | β | β |
| Provenance (causal traceability) | π | π | β |
| Audit export (SIEM-ready) | π | π | β |
CodeLedger is built on a local-first Context Ledger:
Your repo becomes an evolving system β not just code.
Download Latest Release Β· npm install -g @codeledger/cli Β· Getting Started Guide Β· CLI Command Reference
Your agent reads the right files first. Every time.
For browser/cloud sessions, the committed .codeledger/bin/ runtime package is what gets executed. codeledger ready initializes the repo, scans it, and deploys the canonical standalone build so the checked-in runtime matches the version you tested locally. Inside a vendored repo, ./.codeledger/bin/codeledger <command> is the easiest interactive entry point.
Once a repo is initialized, CodeLedger can reconcile reality across drift, outcomes, snapshots, handoffs, and release state:
These commands extend CodeLedger's existing verification and memory systems. They do not create a separate ledger or memory store.
Installing CodeLedger gives you the CLI. To use it in a project, initialize that project:
That sets up CodeLedger inside the repo by creating:
.codeledger/ for project-local cache, bundles, sessions, and runtime data.codeledger/bin/ for the vendored standalone runtime.claude/hooks.json for automatic integrationCLAUDE.md so agents know how to use the context bundleYour normal flow after install is:
CodeLedger is just the beginning.
Itβs built on ContextECF β a broader context infrastructure approach for making AI systems deterministic, auditable, and cumulative instead of probabilistic and forgetful.
At the core is a simple idea:
Every interaction with AI should make the system smarter, more reliable, and more accountable over time.
While youβre using CodeLedger for development, the same foundation extends to:
Most AI tools:
ContextECF + CodeLedger:
What youβre building isnβt just output.
Youβre building a long-term context asset for yourself β and potentially your entire organization.
If CodeLedger is helping you, itβs worth a quick share with:
Intelligent Context AI Inc is the creator of CodeLedger and ContextECF.
If your team is exploring AI at scale, agent systems, or enterprise context management:
π© customersuccess@intelligentcontext.ai
π 916-753-7432
CodeLedger helps you capture truth in code.
ContextECF helps you scale that truth across the enterprise.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/codeledger)<a href="https://allmcps.com/mcp/codeledger"><img src="https://allmcps.com/api/badge/codeledger?style=directory" alt="Codeledger on AllMCPs" /></a>