KLYPIX Shared Project Memory runs on your own machine — the client starts it, so there is no endpoint to ping. 1 204 installs a week from npm. Last commit 31 Oct 2026.
Shared project memory for Claude Code, Codex and Cursor: decisions, corrections, overlap warnings.
We read the source, 3 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
if (!ps && (name === 'sudo' || name === 'doas')) {
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(process.execPath, [
const entry = path.join(base, f);
Object.entries(process.env).filter(([, value]) => typeof value === 'string'),
world.innerHTML = frag.join('') + `<svg id="edges" width="1" height="1"><defs>${markers}</defs>${paths.join('')}</svg>`;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch KLYPIX Shared Project Memory and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add klypix-mcp -- npx -y klypix-mcp
{
"mcpServers": {
"klypix-mcp": {
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}
[mcp_servers.klypix-mcp]
command = "npx"
args = ["-y", "klypix-mcp"]
{
"mcpServers": {
"klypix-mcp": {
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}
{
"servers": {
"klypix-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"klypix-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
KLYPIX_VAULT (Alternative to --vault: absolute path to the folder holding your .klypix canvases. The --vault argument takes precedence).
Automatic project memory for Claude Code and Cursor; Codex and Claude Desktop over MCP.
Shared memory and delegation for Codex, Cursor, Claude Code, and OpenCode.
Shared, project-aware memory for Claude Code, Codex, and other agents with human review.
Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.
Persistent, governed institutional memory for Claude Code — specs, decisions, learnings.
Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.
Shared project memory for coding agents: decisions, lessons, guardrails and tasks per repository.
One shared, versioned memory for Claude Code, Cursor, Codex and every MCP agent. Local and offline.
Answers built from our own checks of this server.