Share project conventions across every coding agent without rewrites

You explain the same monorepo layout to Cursor, Claude Code, and Codex on day 1 and forget which one knows what. Project context persists across agents and across days.

Memorix (MCP server) — Use Cases, Install & Live Demo

Why use it

Key features

Cross-agent: works with Claude Code, Cursor, Codex, Windsurf, Gemini CLI, OpenCode, Antigravity, Trae
Append-only with revision history
Tag-based recall (project, language, decision)
Local SQLite backend; optional cloud sync
Tiny — single Node binary
MIT

Live Demo

What it looks like in practice

memorix-mcp.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "memorix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memorix"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "memorix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memorix"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "memorix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memorix"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "memorix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memorix"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "memorix-mcp",
      "command": "npx",
      "args": [
        "-y",
        "memorix"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "memorix-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "memorix"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add memorix-mcp -- npx -y memorix

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Memorix

Capture architectural decisions as queryable memories

👤 Tech leads, staff engineers ⏱ ~20 min intermediate

When to use: You make a call ('we don't use Redux, just zustand') and want it to stick.

Flow

Log the decision

Save decision: 'Use zustand, not Redux. Reason: simpler API, smaller bundle.' Tag: state-management.✓ Copied

→ Decision saved with tag
Verify enforcement

Whenever Claude is about to import redux in this repo, reject and quote the decision.✓ Copied

→ Subsequent imports are flagged with the saved reason

Outcome: An ADR-light log that agents actually read.

Pitfalls

Memorix is per-user; team-wide ADRs need cloud sync or a checked-in mirror — Use --export ./adr.json and commit; teammates --import to sync

Combine with: github

Hand off a debugging session to another agent

👤 Devs who switch between models mid-task ⏱ ~10 min intermediate

When to use: Claude has been debugging for 2h and you want to swap to Codex without re-explaining everything.

Flow

Snapshot

Snapshot current debugging context: hypothesis, what we ruled out, next step.✓ Copied

→ Snapshot saved with tag debug-session-<id>
Pick up elsewhere

(in Codex) — Load debug session and continue from where Claude left off.✓ Copied

→ Codex summarizes the snapshot and proposes next step

Outcome: Painless agent swap mid-task.

Pitfalls

Snapshot is too vague; new agent restarts from scratch — Memorix's snapshot tool prompts for: hypothesis, evidence, next-step — fill all three

Combinations

Pair with other MCPs for X10 leverage

memorix-mcp + github

Mirror memories to a checked-in adr.json file for team sharing

Export memories tagged 'adr' to /docs/adr.json and commit.✓ Copied

memorix-mcp + filesystem

Backup the local Memorix DB

Copy ~/.memorix.db to /backups/$(date +%F)/.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
save	content: str, tags: str[]	Persist a fact / decision / snapshot	free
recall	query?, tags?, limit?	Bring relevant context into the current task	free
update	id, content	Correct or refine an existing memory	free
decay	older_than_days	Periodic cleanup	free

Cost & Limits

What this costs to run

API quota: Local SQLite — bound by disk
Tokens per call: 100–500 per recall
Monetary: Free; cloud sync (if used) varies
Tip: Run decay weekly so recall queries return tight, recent context, not 6-month-old debug notes

Security

Permissions, secrets, blast radius

Credential storage: Local SQLite by default; cloud sync needs API key

Data egress: Local-only by default

Memories may contain secrets (e.g. 'we use API key XYZ') — review before exporting / committing

Troubleshooting

Common errors and fixes

Recall returns nothing relevant

Check tags match — Memorix uses tag filters AND fuzzy text

Verify: Run with no filter to see all memories

DB locked error

Multiple agents writing simultaneously — Memorix uses WAL; ensure version >= 0.4

Import fails

Mismatched schema between exporting and importing version — upgrade both first

Alternatives

Memorix vs others

Alternative	When to use it instead	Tradeoff
doobidoo/mcp-memory-service	You want richer features like knowledge graph and consolidation	Heavier; Memorix is intentionally minimal
OpenAI Memory / Anthropic Memory	You only use one provider	Locked to that provider; Memorix is cross-agent

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Memorix

Why use it

Key features

Live Demo

What it looks like in practice

Install

Pick your client

Use Cases

Real-world ways to use Memorix

Prerequisites

Flow

Pitfalls

Flow

Pitfalls

Flow

Pitfalls

Combinations

Pair with other MCPs for X10 leverage

Tools

What this MCP exposes

Cost & Limits

What this costs to run

Security

Permissions, secrets, blast radius

Troubleshooting

Common errors and fixes

Alternatives

Memorix vs others

More

Resources