Memorix MCP Server

Local-first shared memory layer for AI coding agents across MCP clients, Git history, reasoning context, and project sessions. The memorix mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

• memorix CLI is the direct command surface for setup, memory search/store, Git Memory, import/export, dashboard, orchestration, diagnostics, and automation
• memorix serve is the stdio MCP bridge used by IDEs and coding agents. Its default tool profile is micro, so agents see only the compact core tool set
• memorix background start / memorix serve-http run the HTTP service for a shared endpoint, dashboard, Docker, or multiple clients
• Node.js >=22.18.0
• Git, because project identity is derived from the real Git root
• ~/.memorix/config.toml for global defaults

Its toolset

Everything the assistant can do here goes through one of these:

• Capabilities — Memorix is more than a memory store. It also installs agent integrations, keeps useful work events, turns commits into project facts, exposes a local
• Uninstall — memorix uninstall reports MCP config entries for manual cleanup instead of silently editing every MCP file it finds

Configuration

You will need one environment variable: MINIMAX_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

The server ships on npm as memorix, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Memorix's toolset — Capabilities, Uninstall — is a fair guide to whether it matches your workflow. It is maintained by avids2; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Memorix's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the memorix mcp server does with a few real requests.