lcc (Local Context Compiler)
Related Servers
Alternatives to lcc (Local Context Compiler)
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceBrings Claude Code's context compaction to any MCP host, enabling agents to gauge context pressure, summarize history, re-hydrate files, and persist rules across session boundaries.19MIT
- AlicenseAqualityBmaintenanceEnables local LLM chat sessions to continue indefinitely by automatically compacting context and storing permanent memory on disk, with recall across all past sessions.41MIT
- AlicenseNot gradedqualityBmaintenanceProvides deterministic context compaction and safety gating for AI agents, preserving original messages verbatim while dropping irrelevant ones and flagging destructive commands.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to deterministically shrink multi-turn conversation history and prompts by stripping verbose boilerplate and filler tokens while preserving critical tool parameters and named entities. This lets users cut inference costs by roughly 40-60% without losing essential context, running either as a native MCP server over JSON-RPC stdio or as an importable zero-dependency Python module.7MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible developer environments to shrink verbose tool outputs—test logs, git diffs, directory listings, and file dumps—before they reach the context window, preserving compiler errors, failure signatures, and decisive anchors. It runs either as direct callable tools or as a transparent proxy wrapping other MCP servers such as filesystem, git, or terminal providers.1MIT
- AlicenseNot gradedqualityBmaintenanceCompresses multi-turn conversation history by stripping verbose boilerplate and filler tokens while preserving critical tool parameters and named entities, deterministically cutting inference costs by 40-60%. Runs as a zero-dependency Python MCP server or importable module, compatible with Claude Desktop, Cursor, and other MCP runtimes.7MIT
TDQS
Scored across 7 tools
Each tool has a distinct role in a coherent pipeline (compact for context blocks, compact_transcript for session transcripts, inspect/prepare/explain for diagnostics, recall for stash retrieval, intake for triage). The main risk is compact vs compact_transcript and inspect vs prepare, which overlap conceptually, but the descriptions clearly delineate scope and inputs.
All tools use a consistent lowercase verb pattern (compact, inspect, prepare, explain, recall, intake), with snake_case only for the compound compact_transcript. No mixed conventions or vague naming.
Seven tools is well-scoped for a context compiler, and each tool maps to a distinct stage (compaction, diagnostics, retrieval, intake) with no redundant entries.
The surface covers the core lifecycle: intake, inspection, preparation, compaction, explanation, and retrieval of stashed content. Minor gaps exist (e.g. no explicit way to list or enumerate stashed items before recalling, or a config/status tool), but core workflows are covered.