Skip to main content
mcpSource-backed
Headroom logo

Headroom MCP Server

Local-first context compression MCP server for reducing tool outputs, logs, files, RAG chunks, and agent context before they reach the model.

by Tejas Chopra · submitted by oktofeesh1·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://headroom-docs.vercel.app/docs/mcp, https://github.com/headroomlabs-ai/headroom
Brand
Headroom
Brand domain
headroom-docs.vercel.app
Brand asset source
brandfetch
Safety notes
Compression can omit details from the active model context; use retrieval tools when exact logs, code, or evidence matter., Do not treat compressed summaries as authoritative for security, legal, financial, or incident-response decisions without checking originals., Local memory and reversible compression stores should be protected, purged, or excluded from backups when they contain sensitive data., Evaluate compression behavior on your own task types before relying on it for critical workflows.
Privacy notes
Tool outputs, logs, source files, prompts, RAG chunks, and conversation context may be stored locally for compression and retrieval., Local stores can include secrets, customer data, stack traces, repository paths, and proprietary code unless filtered upstream., If using proxy or provider integrations beyond local MCP tools, review which data is forwarded to external model providers.
Author
Tejas Chopra
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup.

0/5 ready
Install & runtime2Network & hosting1General210 minutes

Safety & privacy surface

Safety & privacy surface

4 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, third-party handling.

5 areas
  • SafetyData retentionCompression can omit details from the active model context; use retrieval tools when exact logs, code, or evidence matter.
  • SafetyGeneralDo not treat compressed summaries as authoritative for security, legal, financial, or incident-response decisions without checking originals.
  • SafetyData retentionLocal memory and reversible compression stores should be protected, purged, or excluded from backups when they contain sensitive data.
  • SafetyGeneralEvaluate compression behavior on your own task types before relying on it for critical workflows.
  • PrivacyLocal filesTool outputs, logs, source files, prompts, RAG chunks, and conversation context may be stored locally for compression and retrieval.
  • PrivacyCredentials & tokensLocal stores can include secrets, customer data, stack traces, repository paths, and proprietary code unless filtered upstream.
  • PrivacyThird-party handlingIf using proxy or provider integrations beyond local MCP tools, review which data is forwarded to external model providers.

Safety notes

  • Compression can omit details from the active model context; use retrieval tools when exact logs, code, or evidence matter.
  • Do not treat compressed summaries as authoritative for security, legal, financial, or incident-response decisions without checking originals.
  • Local memory and reversible compression stores should be protected, purged, or excluded from backups when they contain sensitive data.
  • Evaluate compression behavior on your own task types before relying on it for critical workflows.

Privacy notes

  • Tool outputs, logs, source files, prompts, RAG chunks, and conversation context may be stored locally for compression and retrieval.
  • Local stores can include secrets, customer data, stack traces, repository paths, and proprietary code unless filtered upstream.
  • If using proxy or provider integrations beyond local MCP tools, review which data is forwarded to external model providers.

Prerequisites

  • Python 3.10 or newer.
  • Headroom package installed with MCP support.
  • Local disk space for reversible compression, memory, and retrieval stores.
  • MCP client such as Claude Code, Codex, Cursor, Aider, or another compatible host.
  • Team agreement on what content can be compressed, stored, and retrieved by an agent.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Full copyable content
{
  "mcpServers": {
    "headroom": {
      "command": "headroom",
      "args": ["mcp", "serve"]
    }
  }
}

About this resource

Content

Headroom is a context compression layer for AI agents. Its MCP mode exposes tools for compressing large inputs, retrieving originals when needed, and inspecting savings. The project is designed for tool outputs, logs, files, RAG chunks, and conversation history in coding-agent workflows.

The repository describes Headroom as local-first and reversible: originals are stored locally so a model can retrieve more detail when a compressed result is not enough.

Source Review

These sources were reviewed on 2026-06-05. Prefer live docs for current MCP commands, package extras, supported agents, storage behavior, and retrieval semantics.

Features

  • MCP tools for compression, retrieval, and savings stats.
  • Compression for logs, tool outputs, files, RAG chunks, code, JSON, and prose.
  • Reversible compression with local storage of originals.
  • Agent wrappers for Claude Code, Codex, Cursor, Aider, Copilot CLI, and OpenClaw.
  • Proxy and SDK modes for non-MCP integrations.
  • Cross-agent memory and deduplication features.

Installation

Install the Python package with MCP support:

pip install "headroom-ai[mcp]"
headroom mcp install

Use the current project docs for the exact MCP install or serve command for your client. A typical stdio server configuration shape is:

{
  "mcpServers": {
    "headroom": {
      "command": "headroom",
      "args": ["mcp", "serve"]
    }
  }
}

Use Cases

  • Compress large command output before it fills the model context window.
  • Let an agent inspect logs while keeping originals retrievable.
  • Reduce repeated RAG chunks or file reads during codebase exploration.
  • Track context savings and compression behavior during long coding sessions.
  • Share compressed context across compatible local agent workflows.

Safety and Privacy

Compression trades context volume for abstraction. For debugging, security review, and incident work, retrieve and inspect originals before drawing final conclusions. Protect local storage because it may contain exactly the sensitive material that was removed from the active prompt.

Duplicate Check

Existing context-window optimizer entries cover agent behavior and workflow guidance. No chopratejas/headroom MCP entry or source URL was found in content/mcp.

Source citations

Add this badge to your README

Show that Headroom MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/headroom-mcp-server.svg)](https://heyclau.de/entry/mcp/headroom-mcp-server)

How it compares

Headroom MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Source provenance, Submitter).

Field

Local-first context compression MCP server for reducing tool outputs, logs, files, RAG chunks, and agent context before they reach the model.

Open dossier

Local-first context-engineering MCP server and CLI that gives Claude token-efficient file reads, shell-output compression, code search, graph queries, persistent session memory, context packaging, verification tools, and dashboard-style token accounting through a single Rust binary.

Open dossier

ButlerBrain hosted MCP server providing persistent memory for AI assistants so Claude can store and recall context across sessions via api.butlerbrain.ai.

Open dossier

MCP server for context-window optimization that routes large tool outputs through sandbox tools, indexes session state, and helps agents retrieve only the context they need.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedSource-backedSubmission linkedSource submissionSource-backed
SubmitterDiffersoktofeesh1oktofeesh1kiannidevoktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandHeadroom logoHeadroomLeanCTX logoLeanCTXContext Mode logoContext Mode
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorTejas ChopraYves GudeButlerBrainmksglu
Added2026-06-052026-06-062026-06-142026-06-05
Platforms
Harness
Source repo
Safety notesCompression can omit details from the active model context; use retrieval tools when exact logs, code, or evidence matter. Do not treat compressed summaries as authoritative for security, legal, financial, or incident-response decisions without checking originals. Local memory and reversible compression stores should be protected, purged, or excluded from backups when they contain sensitive data. Evaluate compression behavior on your own task types before relying on it for critical workflows.LeanCTX can read local files, run shell commands invoked through its tools, cache outputs, install shell/editor hooks, and persist session state. Review generated MCP and shell-hook changes before enabling them across all agents or shells. Keep path jail enforcement enabled for normal use, and allow extra roots only when a project genuinely needs them. Disable or restrict command-execution and unsafe I/O tools for regulated repositories, untrusted workspaces, or shared team environments. Treat compressed shell output and cached reads as summaries; switch to full reads or raw command output when exact source text matters.Persistent memory can retain incorrect or outdated facts until explicitly updated or deleted. Memory write tools may store sensitive information if prompts include secrets or credentials. Shared ButlerBrain workspaces can expose memories to other authorised users in the same account. Review memory contents periodically to prevent unbounded accumulation of stale context.Context Mode encourages agents to execute scripts and route large outputs through sandbox tools; review allowed commands and workspace boundaries. Hook-based installs can affect tool routing automatically. Verify the installed hooks and settings before using it in shared or sensitive workspaces. Indexed session state can influence future retrieval and continuity; purge state when switching projects, clients, or sensitivity levels. Do not rely on compressed or searched summaries for high-stakes decisions without inspecting original files or outputs.
Privacy notesTool outputs, logs, source files, prompts, RAG chunks, and conversation context may be stored locally for compression and retrieval. Local stores can include secrets, customer data, stack traces, repository paths, and proprietary code unless filtered upstream. If using proxy or provider integrations beyond local MCP tools, review which data is forwarded to external model providers.Local code, file paths, command output, search terms, session notes, context packages, knowledge graph data, token metrics, and dashboard statistics can be sent to the MCP client and model. LeanCTX stores local stats and session state under its own configuration/data directories; protect these files if they contain project decisions, findings, or sensitive paths. Secret-like paths are blocked or role-gated by default according to upstream security docs, but users should still avoid prompting agents to read credentials, private keys, tokens, or ignored files. The upstream security policy describes optional update checks and opt-in anonymous stats sharing; disable network checks when working in confidential or offline environments.Memories you save are stored on ButlerBrain infrastructure under its privacy and retention terms. Do not store passwords, API keys, health records, or other regulated data in assistant memory. Exported memory dumps may contain personal preferences; treat them as confidential user data.Context Mode can index file edits, git operations, tasks, errors, user decisions, local files, and command output in SQLite/FTS5 stores. Indexed data may include source code, logs, secrets accidentally printed to terminal, customer data, repository paths, and private prompts. Local analytics and statusline data can reveal workflow patterns, tool usage, and project activity.
Prerequisites
  • Python 3.10 or newer.
  • Headroom package installed with MCP support.
  • Local disk space for reversible compression, memory, and retrieval stores.
  • MCP client such as Claude Code, Codex, Cursor, Aider, or another compatible host.
  • npm for the `lean-ctx-bin` package, or another upstream-supported install path such as release binaries, Homebrew, Cargo, or AUR.
  • A local repository workspace where LeanCTX is allowed to read files, run configured shell commands, and store session metadata.
  • Review of generated MCP client config, shell hooks, per-project `.lean-ctx.toml`, and global `~/.config/lean-ctx/config.toml`.
  • Explicit allow-listing for any paths outside the current project root that LeanCTX should be permitted to access.
  • ButlerBrain account with memory storage enabled for your workspace.
  • Claude Pro, Team, or Enterprise with Connectors support, or Claude Code with HTTP MCP transport.
  • Data retention policy review before storing customer PII or regulated data in persistent memory.
  • Understanding of what should and should not be remembered across sessions.
  • Node.js 22.5 or newer, or Bun for supported installs.
  • MCP client such as Claude Code, Gemini CLI, VS Code Copilot, Cursor, Codex, or another supported host.
  • Optional Claude Code plugin marketplace support for automatic hooks and slash commands.
  • Team agreement on what files, command outputs, and session events may be indexed locally.
Install
pip install "headroom-ai[mcp]" && headroom mcp install
npm install -g lean-ctx-bin
claude mcp add --transport http butlerbrain https://api.butlerbrain.ai/mcp
claude mcp add context-mode -- npx -y context-mode
Config
{
  "mcpServers": {
    "headroom": {
      "command": "headroom",
      "args": ["mcp", "serve"]
    }
  }
}
{
  "mcpServers": {
    "lean-ctx": {
      "command": "lean-ctx",
      "env": {
        "LEAN_CTX_IO_BOUNDARY_MODE": "enforce",
        "LEAN_CTX_NO_UPDATE_CHECK": "1"
      }
    }
  }
}
{
  "mcpServers": {
    "butlerbrain": {
      "url": "https://api.butlerbrain.ai/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "context-mode": {
      "command": "npx",
      "args": ["-y", "context-mode"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.