
Ctxfile
dev.ctxfilePublished by ctxfile.devv0.6.0Updated Oct 24, 2026
Local-first MCP server that snapshots your project's working state into one context object.
Overview
Local-first MCP server that snapshots a project's working state into one context object so any MCP agent can load it in a single call.
- What you can do
- Snapshot a project into one structured context object: plan docs, ranked key files within a token budget, git state, optional Notion pages and local-LLM summary
- Save and resume sessions: store an agent-written summary and hand merged, provenance-labeled history to the next agent
- Manage threads: durable identities for a piece of work, with a handoff mode that enforces a complete takeover package
- Import assistant memory into global or per-project scope, with approval for instructions and identity
- Post, list and update tasks that one agent leaves for another, pending your approval
- Ingest context from any harness through a schema-enforced door, and export a static artifact for cloud agents and…
- When to use it
- Useful when you work across several AI agents or editors and keep re-explaining the plan, key files and git state at every cold start. It lets one agent save a session and another pick it up, and gives hosted or CI agents a portable context artifact.
- Requirements
- Runs as a local stdio process, typically via npx from the npm package ctxfile; Node 20 or newer (22 or newer on Windows). The Claude Desktop bundle is macOS Apple Silicon only. Optional NOTION_TOKEN enables the Notion connector; other connectors activate only when configured.
Installation
In SourceWeft
- Open Ctxfile in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ctxfile
One context, every agent, all local.
[CI] [npm] [Apache-2.0] [MCP] [GitHub stars]
Website · Docs · Quickstart · Clients · The .ctxfile convention · Security
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.
30-second quickstart
Every client on your machine at once
Or tell any coding agent: "Set up ctxfile for me by following https://ctxfile.dev/setup.md".
Claude Code (as a plugin, or one command)
Cursor (.cursor/mcp.json in your project, or ~/.cursor/mcp.json globally)
Codex CLI
Claude Desktop (no terminal needed): download ctxfile-macos-arm64.mcpb and drag it into Settings → Extensions. The bundle carries a compiled native module, so it is macOS (Apple Silicon) only for now; on Windows or an Intel Mac, add the stdio JSON above to claude_desktop_config.json instead.
Every other client: ctxfile is a standard stdio server, so npx -y ctxfile is the whole command. One-click install links and copy-paste setup for VS Code, Windsurf, Zed, Cline, Gemini CLI, OpenCode, Warp, Goose, LM Studio, Kiro, JetBrains, Visual Studio, Amp, OpenClaw, Hermes, and more are on the per-client tabs at ctxfile.dev/docs/clients.
Then, in your agent: "load my context" (or call get_context). Requires Node ≥ 20 (≥ 22 on Windows).
Make it automatic
You stop typing "save this." One command installs a skill that teaches any agent, while doing its normal work, when to checkpoint context and to announce every save (never silent, paused any time, reviewable always):
It renders from one canonical spec into whatever each harness reads: an Agent SKILL.md for Claude Code, OpenCode, OpenClaw, and Hermes (one portable file across all four skill systems), a Cursor rule, and managed GEMINI.md / AGENTS.md blocks. Details at ctxfile.dev/docs/automatic.
It follows you into the chat tabs, too
The same context your CLI and editor agents load over MCP can travel to web chatbots. Connect Grok, ChatGPT, Claude web, or Perplexity to your encrypted Sync vault as a custom MCP connector, or ctxfile export and paste the envelope into any prompt box (Gemini, and anything else). Walkthrough: ctxfile.dev/docs/webchat.
Private by default
This is the part we care about most, so it goes first:
- The default path makes zero network calls. Files and git only.
- Secret-looking content (cloud keys, tokens, private keys, JWTs,
password=assignments) is redacted before it enters the snapshot..env*, key files, and credential files are never read at all. - Core is read-only over your project. It never writes to your repo, your git state, or anything else.
- No telemetry by default. An anonymous weekly install ping exists, and it is opt-in only.
- Network connectors (Notion, local Ollama summarization, Sync) activate only when you explicitly configure them.
The full model, including what Pro and Sync add and what they can never see, is documented at ctxfile.dev/security.
What it does
The monorepo
Open core, honestly
Everything in this repo is Apache-2.0 and works standalone, forever. The paid Pro add-on (a separate, closed package) adds session connectors that read your recent sessions from Claude Code, Cursor, Codex CLI, OpenCode, Gemini CLI, Aider, OpenClaw, and Hermes Agent, encrypted cross-session memory, multi-provider consult (Anthropic, OpenRouter for hundreds of models on one key, any OpenAI-compatible endpoint, or local Ollama), AI-distilled prompt Playbooks, and local voice capture. Licensing is an Ed25519-signed key verified offline. No phone-home, ever. Pro funds the open-source work.
Contributing
We want your issues, your PRs, and your weird harness reports. Start with CONTRIBUTING.md. Every ingested format, every MCP client quirk, every redaction gap you find makes the whole thing better.
- Bugs and features: issues
- Questions and show-and-tell: discussions
- Security reports: SECURITY.md (please do not open public issues for vulnerabilities)
Star history
If ctxfile saves you a cold start, a star is how other people find it.
[Star history chart]License
Apache-2.0. "ctxfile" and the ctxfile logo are trademarks of ctxfile; the license covers the code, not the name.
Source: README.md at commit fc1dcca
Tools
0Version history
2- v0.6.0LatestSep 26, 2026
- v0.5.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts