mcpbeat Sign in

KLYPIX Shared Project Memory MCP Server

by dahshanlabs Your server? Claim it
local only

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.

Installs per day peak 502 · avg 127 · +469% w/w
a month agotoday
1 204
Installs / week
npm · klypix-mcp
10
Stars
1 open issue
31 Oct 2026
Last commit
73 releases in 90 days
Apache-2.0
License
JavaScript

What the code does

We read the source, 3 d ago · rules 995398eba69f

Evidence

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')) {
Capabilities

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.

We found things in this code

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.

Three servers free · no card

Connect this server

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.

run in your terminal
claude mcp add klypix-mcp -- npx -y klypix-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "klypix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "klypix-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.klypix-mcp]
command = "npx"
args = ["-y", "klypix-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "klypix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "klypix-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "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).

Alternatives to KLYPIX Shared Project Memory

same job, measured the same way
jevmem
by avinash-jetwani

Automatic project memory for Claude Code and Cursor; Codex and Claude Desktop over MCP.

213 installs/wk local only
Agent Cowork Memory
by rxthlessbeats

Shared memory and delegation for Codex, Cursor, Claude Code, and OpenCode.

343 installs/wk local only
Global Agent Memory
by ozankasikci

Shared, project-aware memory for Claude Code, Codex, and other agents with human review.

110 installs/wk local only
Engrm
by dr12hes

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.

947 installs/wk local only
Oneda
by freeelatech

Persistent, governed institutional memory for Claude Code — specs, decisions, learnings.

answering
Brain Memory
by brainmemory

Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.

answering
RepoMemory
by repomemory

Shared project memory for coding agents: decisions, lessons, guardrails and tasks per repository.

5 tools answering
Make0 Brain
by make0-official

One shared, versioned memory for Claude Code, Cursor, Codex and every MCP agent. Local and offline.

2 230 installs/wk local only

KLYPIX Shared Project Memory — questions

Answers built from our own checks of this server.

Why is there no uptime for KLYPIX Shared Project Memory?
KLYPIX Shared Project Memory runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package klypix-mcp was installed 1 204 times last week.
How do I connect KLYPIX Shared Project Memory?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls klypix-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use KLYPIX Shared Project Memory?
The npm package klypix-mcp was installed 1 204 times in the last week. Week over week that is +469%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is KLYPIX Shared Project Memory open source?
Yes — it is published under the Apache-2.0 licence, written in JavaScript, 10 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.