← Back to directory
E

Entroly

Community
Recoverable, auditable context compression for AI agents.
GitHub source repository ↗
★ 431 Stars Category · Dev Tools Very popular
67FMRS · C
Reliability
10/20
Security and permissions
14/20
Maintenance
13/20
Documentation
17/20
Setup experience
13/20

Entroly targets AI agent developers who need context governance rather than another chat runtime. It provides local-first selection, compression, recovery, receipts, and verification through Python, Node/npm, and stdio MCP surfaces. Actual interception depends on the integration path, recovery depends on retained local state, and token or quality claims should be validated on the target workload.

Read the FMRS scoring method →

Entroly is a local Context OS and MCP server that discovers, ranks, deduplicates, and compresses tool output, logs, files, conversations, and RAG context before model requests. Budget-aware selection, content-addressed recovery, and Context Receipts preserve critical evidence while local verification, memory, caching, and cost-observation features provide additional control. The source claims up to 90% reduction in unnecessary tokens on measured workloads, but results depend on the workload and integration path.

Tools

The tool list has not been reviewed yet.

Setup

Install the Python package with pip install -U entroly. Register Entroly as a stdio MCP server using the command entroly with no arguments; entroly init is also documented. For Claude Code, Codex, or OpenClaw, use entroly attach create --client <client> --project . --ttl 4h --install. Run entroly verify-claims and entroly simulate for local checks.

claude_desktop_config.json
{"mcpServers":{"entroly":{"command":"entroly","args":[]}}}

Fit and risk

Best for

  • Large repositories and document collections
  • Multi-turn, log-heavy AI agent sessions
  • Teams requiring evidence traceability, recovery, and audit records
  • Developers who want local processing and control over the model integration path

Not for

  • Small projects or prompts already within budget
  • MCP-only setups that require automatic interception of every model request
  • Tasks that require the full context to remain visible at all times
  • Treating scoped benchmark results as guarantees across all models and production workloads

Required permissions

  • Requires access to configured local project code, documents, logs, or other context data
  • MCP attachments can be scoped by project and grant scope, given an expiry, and revoked
  • Proxy mode requires the user to configure the relevant provider API key; Entroly does not choose the provider or receive its credentials

Risks and side effects

  • Compression can omit relevant evidence; review Context Receipts and verification results
  • Exact recovery depends on retained receipts and the local recovery store; deleting that state removes the recovery path
  • MCP integrations do not automatically intercept every model request; provider savings require routing through the Entroly proxy
  • Unknown or ambiguous structures pass through unchanged, and unsafe overflow may produce HTTP 413
  • README benchmarks are scoped to particular datasets, budgets, models, and versions, not universal guarantees

Troubleshooting

  1. Run entroly verify-claims to check installation, imports, compression, recovery, and engine mode
  2. Run entroly simulate or entroly perf to inspect local token estimates and optimizer latency
  3. Confirm the MCP client uses the stdio command entroly with no arguments
  4. For proxy mode, confirm the application base URL points to localhost:9377 and the upstream provider is configured
  5. If no provider-bound requests are observed, check whether the client bypasses the custom endpoint or is using MCP-only mode
  6. Verify that the receipt and recovery store still exist when exact recovery is required

Use cases

Select and compress repository or document context under a token budget
Compress repetitive terminal, test, and function output while retaining recovery handles
Create Context Receipts recording selected content, omissions, risks, and fingerprints
Recover omitted content exactly and replay committed context
Check answers against supplied evidence with WITNESS
Estimate local token reduction and measure provider-bound request value

Supported clients

Claude DesktopFull support
Claude CodeFull support
Codex CLIFull support
OpenClawFull support
CursorFull support
WindsurfFull support
VS Code MCP clientsFull support
ZedFull support
GitHub Copilot CLIPartial support