MCP.so
Sign In

ctxfileVerifiedFeatured

@ctxfile

About ctxfile

Local-first MCP server that snapshots your project's working state into one context object. Open-core, privacy-first.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ctxfile": {
      "command": "npx",
      "args": [
        "-y",
        "ctxfile"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is ctxfile?

One context, every agent, all local.

You work with more than one AI agent — Claude Code in the terminal, Cursor in the editor, a chat tab for thinking. Each one starts cold, because your working state (the plan, the key files, the git state, what you decided an hour ago) lives in your head and in scrollback.

ctxfile is a local-first MCP server that snapshots your project's working state into one structured context object, and hands it to any MCP agent in a single call. Save a session in one agent, continue it in another. Nothing leaves your machine.

Quickstart

Claude Code

claude mcp add ctxfile -- npx -y ctxfile

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "ctxfile": { "command": "npx", "args": ["-y", "ctxfile"] }
  }
}

Why ctxfile

  • Local-first & private by default. Zero network calls unless you explicitly configure them. Your files, git state, and context never leave your machine.
  • Read-only over your project. ctxfile snapshots; it never writes to your repo or git state.
  • One context, every agent. Save a session in one MCP client, continue it in another — the same plan, files, and decisions travel with you.
  • Cross-provider threads & handoff. Pick up a thread across different agents and providers.
  • Redaction built in. Secrets and denied paths (.env*, keys, credentials) are never read.
  • Open-core. Apache-2.0 core, published to npm as ctxfile.

Links

Comments

More Memory & Knowledge MCP servers