KLYPIX Shared Project Memory
Shared project memory in a committed file for Claude Code, Codex and Cursor sessions
- Pricing
- Open source
- Platforms
- CLI, macOS, Windows
- Runs
- Locally
- Version
- 1.112.1
- Listing updated
- 3 days ago
About KLYPIX Shared Project Memory
KLYPIX Shared Project Memory is an open-source MCP server for knowledge and memory. It runs locally on your machine and is started by your AI client.
State lives in one brain.klypix file that is committed with the code, so decisions, corrections and open questions travel through git instead of a hosted service. A correction replaces the old decision but keeps it as history, and people can open the same file and edit it. A managed block is also written into AGENTS.md or CLAUDE.md so tools that only read instruction files still see the brief.
When two sessions name the same file, both receive a heads-up, including across git worktrees of one repository since version 1.112.0. It warns and never blocks an edit. A separate check command exits 1 when a live session on the machine is working on a given file, which suits pre-edit hooks or pre-commit steps. Notes and handoff cards let a closed session leave instructions for the next one.
The README says the engine runs with no account, makes no network calls and sends no telemetry, though your agent's own model provider still receives what it reads. Six tools are on by default and the rest are enabled with a flag or the KLYPIX_TOOLS variable. It needs Node.js 20 or newer and is MIT licensed.
Install
Run in a terminal
claude mcp add klypix-mcp -- npx -y klypix-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"klypix-mcp": {
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"klypix-mcp": {
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"klypix-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"klypix-mcp": {
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"klypix-mcp": {
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}Configuration
KLYPIX_VAULTAlternative to --vault: absolute path to the folder holding your .klypix canvases. The --vault argument takes precedence.
Tools this server provides (6)
Taken from the project documentation; the running server may differ.
- brain_sync
- Syncs the project brain at the start of a session or plan.
- brain_note
- Adds a note to the brain.
- brain_ask
- Asks the brain a question.
- brain_message
- Leaves a message for another session.
- brain_handoff
- Creates a handoff card for the next session.
- brain_rules
- Manages project rules.
What it does
- Committed brain file
- Keeps decisions, corrections and open items in one mergeable file in your repo.
- Overlap warnings
- Tells both sessions when they plan to touch the same file, across worktrees.
- Session handoffs
- Leaves notes and next-step cards for later sessions, even closed ones.
- File check command
- Exits non-zero when a live session is working on a file, for hooks and CI.
- Lessons as rules
- Turns repeated mistakes into approved rules that warn while planning, editing and committing.
- Works offline
- Runs without an account or app, with no network calls from the engine.
Good for
- Start every agent session from what the project already decided
- Avoid two agents editing the same file in different worktrees
- Hand unfinished work from one session to the next
- Block or warn on edits in a pre-commit hook when a session owns a file
- Record a correction once so agents stop repeating it
Pricing
Open source
MIT; local workspace and shared brain free; Cloud plan pricing not yet published
Prices change. Check klypix.com before you buy.
KLYPIX Shared Project Memory FAQ
Does it need an account?
No. The README says it runs without the app and without an account on Linux, macOS and Windows.
How many tools are on by default?
Six: brain_sync, brain_note, brain_ask, brain_message, brain_handoff and brain_rules; others are enabled with a flag.
Does it block edits?
No. It warns about overlap and rule hits; a rule stops a change only if you configure it to.
What does the paid side cover?
The pricing page says the local workspace and shared brain are free; Cloud adds storage and included AI after beta.
What do I need to install it?
Node.js 20 or newer; run npx klypix-mcp install in your project.
Is KLYPIX Shared Project Memory free?
Yes. KLYPIX Shared Project Memory is open source, so you can use and self-host it for free.
How do I add KLYPIX Shared Project Memory to Claude Code?
Run this command in your terminal: claude mcp add klypix-mcp -- npx -y klypix-mcp
What are the best alternatives to KLYPIX Shared Project Memory?
The closest alternatives to KLYPIX Shared Project Memory are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to KLYPIX Shared Project Memory

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools