Memorix
Cross-agent memory bridge with knowledge graph, workspace sync, and auto-memory hooks. Supports Windsurf, Cursor, Claude Code, Codex, and VS Code Copilot.
Memorix
Local-first memory platform for AI coding agents.
Git truth, reasoning memory, and cross-agent recall in one MCP server.
Git Memory · Reasoning Memory · Cross-Agent Recall · Control Plane Dashboard
中文文档 · Quick Start · How It Works · Documentation · Setup Guide
Why Memorix
Most AI coding agents remember only the current thread. Memorix gives them a shared, persistent memory layer across IDEs, sessions, and projects.
What makes Memorix different:
- Git Memory: turn
git commitinto searchable engineering memory with noise filtering and commit provenance. - Reasoning Memory: store why a decision was made, not just what changed.
- Cross-Agent Local Recall: Cursor, Windsurf, Claude Code, Codex, Copilot, Kiro, OpenCode, Gemini CLI, and more can read the same local memory base.
- Memory Quality Pipeline: formation, compaction, retention, and source-aware retrieval work together instead of acting like isolated tools.
Quick Start
Install globally:
npm install -g memorix
Initialize project config:
memorix init
Memorix uses two files with two roles:
memorix.ymlfor behavior and project settings.envfor secrets such as API keys
Choose one runtime mode:
memorix serve
Use serve for normal stdio MCP integrations.
memorix serve-http --port 3211
Use serve-http when you want the HTTP transport, collaboration features, and the dashboard on the same port.
In HTTP control-plane mode, agents should call memorix_session_start with projectRoot set to the absolute path of the current workspace or repo root when that path is available. Git remains the source of truth for the final project identity; projectRoot is the detection anchor that keeps parallel sessions from drifting into the wrong project bucket.
Add Memorix to your MCP client:
Cursor · .cursor/mcp.json
{
"mcpServers": {
"memorix": {
"command": "memorix",
"args": ["serve"]
}
}
}
Claude Code
claude mcp add memorix -- memorix serve
Codex · ~/.codex/config.toml
[mcp_servers.memorix]
command = "memorix"
args = ["serve"]
For the full IDE matrix, Windows notes, and troubleshooting, see docs/SETUP.md.
Core Workflows
1. Store and retrieve memory
Use MCP tools such as:
memorix_storememorix_searchmemorix_detailmemorix_timelinememorix_resolve
This covers decisions, gotchas, problem-solution notes, and session handoff context.
2. Capture Git truth automatically
Install the post-commit hook:
memorix git-hook --force
Or ingest manually:
memorix ingest commit
memorix ingest log --count 20
Git memories are stored with source='git', commit hashes, changed files, and noise filtering.
3. Run the control plane
memorix serve-http --port 3211
Then open:
- MCP HTTP endpoint:
http://localhost:3211/mcp - Dashboard:
http://localhost:3211
This mode gives you collaboration tools, project identity diagnostics, config provenance, Git Memory views, and the dashboard in one place.
When multiple HTTP sessions are open at once, each session should bind itself with memorix_session_start(projectRoot=...) before using project-scoped memory tools.
How It Works
graph TB
A["git commit / agent tool call / manual store"] --> B["Memorix Runtime"]
B --> C["Observation / Reasoning / Git Memory"]
C --> D["Formation + Indexing + Graph + Retention"]
D --> E["Search / Detail / Timeline / Dashboard / Team"]
Memory Layers
- Observation Memory: what changed, how something works, gotchas, problem-solution notes
- Reasoning Memory: why a choice was made, alternatives, trade-offs, risks
- Git Memory: immutable engineering facts derived from commits
Retrieval Model
- Default search is project-scoped
scope="global"searches across projects- Global hits can be opened explicitly with project-aware refs
- Source-aware retrieval boosts Git memories for “what changed” questions and reasoning memories for “why” questions
Documentation
Getting Started
Product and Architecture
Reference
Development
AI-Facing Project Docs
Development
git clone https://github.com/AVIDS2/memorix.git
cd memorix
npm install
npm run dev
npm test
npm run build
Key local commands:
memorix status
memorix dashboard
memorix serve-http --port 3211
memorix git-hook --force
Acknowledgements
Memorix builds on ideas from mcp-memory-service, MemCP, claude-mem, Mem0, and the broader MCP ecosystem.
Star History
License
Servidores relacionados
Scout Monitoring MCP
patrocinadorPut performance and error data directly in the hands of your AI assistant.
Alpha Vantage MCP Server
patrocinadorAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
Sequa MCP
A proxy that connects local STDIO with remote MCP servers, enabling IDEs to use MCP without extra infrastructure.
Universal Crypto MCP
Enable AI agents to interact with any EVM blockchain through natural language.
My First MCP
A Model Context Protocol server implemented in Node.js with Docker support.
Klever VM
MCP server for [Klever](https://klever.org) blockchain smart contract development, on-chain data exploration, and VM interaction. Public remote server available at `https://mcp.klever.org/mcp`.
MCP ZepAi Server
A server for Zep, a long-term memory store for AI applications, requiring a ZEP_API_KEY for access.
Postman MCP Server
Run Postman collections using Newman, with support for environment and global variables.
RenPy MCP
MCP server + visual development tools for Ren'Py visual novel engine. 60 tools, story map, live dashboard, standalone CLI.
Qase
Interact with the Qase API for test management. Requires a QASE_API_TOKEN for authentication.
iOS Simulator
Provides programmatic control over iOS simulators through a standardized interface.
MCP Sourcify Server
Verify and retrieve smart contract source code using the Sourcify API.