MCP.Market

KLYPIX Shared Project Memory MCP server

by dahshanlabs·io.github.dahshanlabs/klypix-mcp·v1.110.0·10 stars

Shared project memory for Claude Code, Codex and Cursor: decisions, corrections, overlap warnings.

B71/100grade B
What users say
No reviews yet
Be the first
Safety scan
B71/100

not scanned yet

Adoption
Growing

10 stars1.9k downloads/wk

Reviews

Write one

Nobody has reviewed KLYPIX Shared Project Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

KLYPIX Shared Project Memory tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How KLYPIX Shared Project Memory compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
71/100
higher than 36% of 48,255 servers
GitHub stars
10
more than 88% of 28,688 servers
Downloads a week
1,880
more than 95% of 12,191 servers with a package

Release history: 18 versions in the registry since 2026-09-16, latest 2026-10-31, typically one every 1 day.

Install KLYPIX Shared Project Memory in Claude Code, Cursor or VS Code

Runs npx -y klypix-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add klypix-mcp -- npx -y klypix-mcp
Add to Cursor

What the publisher says

From the KLYPIX Shared Project Memory repository's README, as published. We do not edit it. Read it on GitHub

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; Klypix uploads nothing (your agent's provider still receives what the agent reads). Integration depth differs by host — see Supported hosts.

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).

Run this inside your project:

npx klypix-mcp install

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

KLYPIX Shared Project Memory: common questions

Is KLYPIX Shared Project Memory MCP server safe?
Mostly: it is graded B (71/100). Read the KLYPIX Shared Project Memory safety report
How do I install KLYPIX Shared Project Memory?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does KLYPIX Shared Project Memory need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is KLYPIX Shared Project Memory maintained?
The last commit was 21 days ago (2026-10-14). The latest release is v1.110.0.
What can I use instead of KLYPIX Shared Project Memory?
Servers from other publishers that do the same job: Memorix MCP server, Claudexor MCP server and State Memory MCP server. Compare all KLYPIX Shared Project Memory alternatives.
How does KLYPIX Shared Project Memory compare with other MCP servers?
safety score 71/100 (higher than 36% of 48,255 servers); github stars 10 (more than 88% of 28,688 servers); downloads a week 1,880 (more than 95% of 12,191 servers with a package). Full comparison.

Alternatives to KLYPIX Shared Project Memory

Same job from other publishers: the closest match first, then the best rated.

All KLYPIX Shared Project Memory alternatives →
  • Memorix
    Local-first project memory with legacy MCP and 2026 discovery compatibility.
    B
  • Claudexor
    Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.
    A
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Tradememory Protocol
    Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents.
    B