Memorix
Local shared project memory for coding agents: facts, decisions and commits available through MCP, CLI and hooks in any agent
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Reads project files and git history
- Installs integrations and runs a local memory process
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/memorixDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal
claude mcp add --transport stdio memorix -- npx -y memorix@1.9.6 serveOr add to the file .mcp.json, in the project
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Add to the file ~/.cursor/mcp.json, for all projects
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.
The button opens the agent and offers to add the server. If nothing happens, copy the config below.
Run in a terminal
code --add-mcp '{"name":"memorix","type":"stdio","command":"npx","args":["-y","memorix@1.9.6","serve"]}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"memorix": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the servers key.
Run in a terminal
codex mcp add memorix -- npx -y memorix@1.9.6 serveOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.memorix]
command = "npx"
args = ["-y", "memorix@1.9.6", "serve"]If the file already exists, append the block to the end.
Add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Add to the file ~/.config/devin/mcp_config.json, for all projects
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.
Formerly Windsurf.
Add to the file cline_mcp_settings.json, for all projects
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.
Add to the file .roo/mcp.json, in the project
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
A fork of Roo Code, same .roo folders.
Add to the file opencode.json, in the project
{
"mcp": {
"memorix": {
"type": "local",
"command": [
"npx",
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcp key.
Add to the file ~/.config/zed/settings.json, for all projects
{
"context_servers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the context_servers key.
Add to the file .codeassistant/mcp.json, in the project
{
"mcpServers": {
"memorix": {
"command": "npx",
"args": [
"-y",
"memorix@1.9.6",
"serve"
]
}
}
}If the file already exists, add the server inside the mcpServers key.
Install Memorix: npm install -g memorix, then memorix setup --agent claude --global (swap claude for codex, cursor, copilot and so on).
Other ways from the author
npm install -g memorix
memorix setup --agent claude --globalSwap claude for your agent: codex, cursor, copilot, gemini-cli, opencode, windsurf.
This is third-party code. Review the repository files before installing.
What it does
Memorix gives coding agents a shared project memory that survives new chats, IDE switches and handoffs. The memory sits next to the git project, SQLite is the canonical store, and search runs by keyword and by meaning. It keeps observations, fixes, gotchas and design rationale, and turns commits into engineering facts. One memory pool is reachable through MCP, hooks, CLI, SDK and a bundled terminal agent, and the setup command wires Memorix into your agent.
Who it is for. For developers tired of re-explaining the project to every new agent session.
Good fit when
- A past session figured something out that a new one does not know
- You work across several agents and IDEs on one project
- You need to keep the reasons behind architecture decisions between chats
Not a fit when
- You need cloud-shared team memory rather than local per-project memory
- The project is one-off and memory does not pay off
Example request
Save to project memory why we chose a queue over cron, and surface it next timeLimitations
Memory is local and tied to the git project; cross-device sync is optional and configured separately. The semantic index and LLM-backed memory formation are optional and need their own keys. Installation needs Node.js.
How to disable. Uninstall the package (npm uninstall -g memorix) and remove the added MCP entry from the agent config; the project memory folder can be deleted manually.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Reads project files and git history
- Installs integrations and runs a local memory process
README in short
The README describes Memorix as local shared memory for coding agents that lives under the git project rather than inside one chat window. SQLite is the canonical store, with keyword search and an optional LanceDB semantic index. Memory kinds include observations, long-term memory, code memory, git-commit memory, design rationale and a review-gated knowledge workspace. Install is via npm, and memorix setup wires MCP, rules, hooks and skills into dozens of agents, with stdio as the default transport.
FAQ
Where is data stored?
Locally; the canonical store is SQLite next to the git project. Indexes are rebuildable, and cross-device sync is opt-in.
Is an LLM required?
No. LLM-backed memory formation and embeddings are optional; the basic path runs without an external model.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything