lcc — Local Context Compiler MCP server
io.github.lucasmartins-ai/lcc·v1.2.0·16 starsCompact agent context verbatim, offline: cut spent tool outputs, recall them by hash.
16 stars179 downloads/wk
Reviews
Write oneNobody has reviewed lcc — Local Context Compiler yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
lcc — Local Context Compiler tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it
- Code scan93 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How lcc — Local Context Compiler compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 90% of 4,460 AI and agents servers
- GitHub stars
- 16
- more than 87% of 2,711 AI and agents servers
- Downloads a week
- 179
- more than 73% of 1,538 AI and agents servers with a package
Install lcc — Local Context Compiler in Claude Code, Cursor or VS Code
claude mcp add lcc -- uvx local-context-compiler
What the publisher says
From the lcc — Local Context Compiler repository's README, as published. We do not edit it. Read it on GitHub
lcc — Local Context Compiler
Compact coding-agent context without summarizing it away. lcc cuts what the model does not need, keeps everything else byte for byte, and writes a receipt.
<!-- mcp-name: io.github.lucasmartins-ai/lcc -->
/compact vs lcc
Claude Code's /compact replaces your session with a summary written by a model. Summaries drop the exact error, path or line the agent needs two turns later. lcc does the opposite: old tool outputs leave the context but stay one recall away, and every user and assistant message is kept as it was.
Measured with lcc measure-session (PyPI 1.2.0, offline, exact o200kbase token count; re-run 2026-10-23). On main, whose stash note now states lines and size, the same session gives 28,983 (−49.2%). That session is one of the best cases. Across all 299 of my long sessions (100+ messages each, 36.3 M tokens) the median cut was 21.8% (middle half 15% to 31%, best 65%), with 0 messages lost (python benchmarks/research/longsessions.py, 2026-10-23, main). These are all my sessions: run it on yours and post the result.
In a pre-registered test on 172 real requests (evidence), an agent answering from the stashed context plus recall did as well as with the full context on file recall (+0.006, 95% CI −0.023 to +0.034) with 36.6% fewer tokens. It called recall for 90% of the questions about removed content. A /compact-style summary of the same sessions got 73% of exact values right (our reimplementation of /compact, written by Opus); full and verbatim context got 98%.
Install
pip install "local-context-compiler[tiktoken]" # the CLI is `lcc`
lcc measure-session "$(ls -t ~/.claude/projects/*/*.jsonl | head -1)" # your latest sessionThe second line reads your most recent Claude Code session, runs every mode offline and prints counts only. Nothing is changed and nothing leaves the machine.
Claude Code plugin (replaces the /compact summary). Function hooks are early access, so this needs Claude Code 2.1.274+ and the flag below:
export CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1
claude plugin marketplace add lucasmartins-ai/lcc
claude plugin install lcc@lcc --config provider=rules --config rulesMode=stashedAllow mcppluginlcclccrecall so the agent can get removed outputs back. When a pass fails or removes too little, the plugin hands over to the built-in summary and says so in a toast. Details: Claude Code guide.
MCP (Claude Code, Cursor, Claude Desktop, any stdio client):
{"mcpServers": {"lcc": {"command": "lcc", "args": ["mcp"]}}}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
lcc — Local Context Compiler: common questions
- Is lcc — Local Context Compiler MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the lcc — Local Context Compiler safety report
- How do I install lcc — Local Context Compiler?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does lcc — Local Context Compiler need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is lcc — Local Context Compiler maintained?
- The last commit was 11 days ago (2026-10-24). The latest release is v1.2.0.
- What can I use instead of lcc — Local Context Compiler?
- Servers from other publishers that do the same job: llmtrim MCP server, Agent Recall MCP server and Total Agent Memory MCP server.
- How does lcc — Local Context Compiler compare with other AI and agents MCP servers?
- safety score 92/100 (higher than 90% of 4,460 AI and agents servers); github stars 16 (more than 87% of 2,711 AI and agents servers); downloads a week 179 (more than 73% of 1,538 AI and agents servers with a package). Full comparison.
Alternatives to lcc — Local Context Compiler
Same job from other publishers: the closest match first, then the best rated.
- llmtrimMCP server and proxy that compresses LLM prompts, tool output, and replies to cut token cost.not reviewedEstablishedA
- Agent RecallCorrection-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.not reviewedEstablishedA
- Total Agent MemoryPersistent local memory for coding agents: temporal knowledge graph, procedural and episodic recallnot reviewedEstablishedA