dahshanlabs/klypix-mcp

**Every project gets a brain.**
Shared project memory for **Claude Code, Codex, Cursor** and other MCP coding tools. One
brain.klypix file, committed with your code, carries the project's decisions, corrections and open
questions across sessions and between tools. Corrections supersede stale decisions; sessions declare
the files they expect to touch and get warned about same-machine overlap. Versioned in Git. Served
over MCP by a process on your machine. In the standalone setup, brain data stays in your files;
your agent's provider can still receive what the agent reads. Integration depth differs by host — see
Supported hosts.
The **Apache-2.0 engine works without the KLYPIX desktop app or a KLYPIX account**. The optional
Windows workspace lets people inspect the same project brain
beside their files. App-based sharing has its own cloud path; see Security and permissions.
Install · Try your first decision ·
Supported hosts ·
Privacy · Limits · Uninstall
For a team walkthrough, read the shared project memory setup guide.
Choosing an approach? Our memory tools comparison
links each tool's official documentation and discloses that Klypix wrote it.
Real output, not a mockup: both panes run a real MCP client against this server
(docs/demo/ — the GIF is rendered by CI from a scripted tape against this server, not
hand-recorded, and re-rendered when the server's responses change).
With **Node.js 20 or newer**, run this inside your project:
It creates brain.klypix if the project has none, wires the editors it finds on this machine,
registers the .klypix merge driver if this is a git repo, and exits only after a real MCP
handshake has counted the tools that answered.
Host badges name the **integration level**, not a flat "compatible" — the levels and what is
actually tested are in Supported hosts.
> **One project. Many agents. One current understanding.**
Klypix does not launch, run, supervise, or replace your agents. It is not an agent runtime, a model
router, a worktree manager, or a replacement for Git. It holds what the project currently believes.
See the shared project brain in action
Watch how current decisions, corrections, evidence, and active work stay visible to people and
carry forward into supported coding-agent sessions.
**Watch the 2:21 showcase with sound**
---
The problem
You are running more than one coding agent on one codebase — a Claude Code session here, Codex in
another terminal, Cursor open on the side. Context saved in one tool may be missing from the next:
- A new session misses a prior decision, and you explain the same architecture again.
- A decision captured only in a Claude conversation is unavailable to your Codex session.
- One agent implements an approach the team already rejected, because the reason it was rejected
lived in a chat that ended.
- Two sessions start changing the same files and nobody finds out until review.
- Git stores the code history; the reasons behind a change still need to be recorded.
Your agents may run independently. Their project understanding should not.
---
60 seconds: two agents, one project
Illustrative calls and responses: replace /absolute/path/to/project with the same project root
in both sessions (for example, C:/work/api on Windows).
Session A — Claude Code, in your repo:
Session B — Codex, same repo, half a minute later:
Session A gets the same overlap surfaced on its next KLYPIX action. Neither edit is blocked — the
warning is advisory, and both sides only see the overlap because both declared the files they
expected to touch.
Then the brain pushes back before the decision, not after:
And the decision is kept where the next session will find it:
Prove all of this on your own machine, against the exact build you installed, with two real
isolated MCP clients:
It runs in a temporary fixture and touches nothing else. It checks tool discovery, task memory,
truthful peer reporting, overlap surfacing, proactive logging, and in-band delivery of a peer note.
It verifies 15 required coordination behaviours — not every tool, and not the retrieval engine.
---
Quick start
**You need Node.js 20 or newer** (node -v to check). Every way of connecting runs the server with
node — npx, the installed bundle, and the entry KLYPIX's Settings buttons write — and none of them
checks for Node first.
Run this **inside your project**:
One command for supported editors detected on this machine. It finds the project root (walking up,
so running it from src/ is fine), gives the project a brain if it doesn't have one, wires the
agent tools you actually have installed, registers the card-level .klypix merge driver if it's a
git repo, and then **proves the result** before it exits: