Server data from the Official MCP Registry
Shared memory store for AI coding tools with dual-timeline conflict arbitration.
Shared memory store for AI coding tools with dual-timeline conflict arbitration.
Memory Arbiter is a well-structured local MCP server for managing shared memory across AI coding tools. The codebase demonstrates good security practices with proper input validation, graceful degradation, and appropriate permission scoping. Minor code quality concerns around broad exception handling and env var usage do not significantly impact the overall security posture. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
8 files analyzed · 10 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: MEMORY_ARBITER_CLIENT
Environment variable: MEMORY_ARBITER_AGENT_ID
Environment variable: MEMORY_ARBITER_DB_PATH
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-billy12151-memory-arbiter-mcp": {
"env": {
"MEMORY_ARBITER_CLIENT": "your-memory-arbiter-client-here",
"MEMORY_ARBITER_DB_PATH": "your-memory-arbiter-db-path-here",
"MEMORY_ARBITER_AGENT_ID": "your-memory-arbiter-agent-id-here"
},
"args": [
"memory-arbiter-mcp"
],
"command": "uvx"
}
}
}From the project's GitHub README.
mcp-name: io.github.billy12151/memory-arbiter-mcp
A lightweight, fully local MCP Server that gives your AI coding tools a shared memory store with built-in conflict arbitration.
Every tool — ZCode, Codex, Cursor, Claude Code — has its own memory. They don't talk to each other. Memory Arbiter fixes this: one SQLite database, all tools read and write through the same MCP protocol, conflicts are resolved by structured rules (not LLM guesswork).
content, agent_id, workspace, tags, source_type, event_time, ingest_time, confidence, protection_level, and more.user_confirmed > document_extracted > agent_generated > unknown.user_confirmed memories are automatically locked — no agent can overwrite them.sqlite-vec → FTS5 → LIKE → JSONL backup. Never crashes.Requirements: Python 3.11+
# Clone
git clone https://github.com/billy12151/memory-arbiter-mcp.git
cd memory-arbiter-mcp
# Setup
python3.11 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
pip install -e .
# Optional: semantic recall via sqlite-vec
pip install '.[vec]'
# Run
memory-arbiter-mcp
Add to your tool's MCP config (see examples/ for ready-made templates):
{
"mcpServers": {
"memory-arbiter": {
"command": "/path/to/memory-arbiter-mcp/.venv/bin/memory-arbiter-mcp",
"env": {
"MEMORY_ARBITER_CLIENT": "zcode",
"MEMORY_ARBITER_AGENT_ID": "zcode-default",
"MEMORY_ARBITER_DB_PATH": "~/.local/share/memory-arbiter/memory.sqlite3"
}
}
}
}
Change
MEMORY_ARBITER_CLIENTfor each tool (zcode,codex,cursor,claude-code). All tools share the sameDB_PATH— that's the whole point.
⚠️ New session required: MCP servers are loaded at session startup. Already-open sessions won't see the new tools. Start a fresh session after configuring.
| Client | Config Location |
|---|---|
| ZCode | ~/.zcode/v2/ MCP config |
| Codex CLI | ~/.codex/ MCP config |
| Claude Code | .mcp.json in project root |
| Cursor | ~/.cursor/mcp.json |
| Tool | Description |
|---|---|
memory_write | Write a memory (source_type=user_confirmed auto-locks) |
memory_search | Search memories (FTS5 → LIKE fallback) |
memory_compare | Compare two memories, returns explanation only |
memory_arbitrate | Arbitrate conflict, can record result (apply=true) |
memory_confirm | Promote a memory to user-confirmed and locked |
memory_list_conflicts | List unresolved conflicts |
memory_status | Show current mode, degradation status, storage paths |
Moving to a new machine? Just copy the SQLite file:
# Copy the database
cp ~/.local/share/memory-arbiter/memory.sqlite3 /new/machine/~/.local/share/memory-arbiter/
# Reinstall the project (don't copy .venv — rebuild it)
python3.11 -m venv .venv
source .venv/bin/activate
pip install -e .
python3.11 -m pip install -r requirements.txt
python3.11 -m pytest
MIT
一个轻量、完全本地运行的 MCP Server,给你的 AI 编程工具提供共享记忆库,内置冲突仲裁机制。
你同时用 ZCode、Codex、Cursor、Claude Code——每个工具都有各自的记忆,互不相通。Memory Arbiter 解决这个问题:一个 SQLite 数据库,所有工具通过同一个 MCP 协议读写,冲突由结构化规则仲裁,不依赖大模型。
content、agent_id、workspace、tags、source_type、event_time、ingest_time、confidence、protection_level 等。user_confirmed > document_extracted > agent_generated > unknown。user_confirmed 的记忆自动锁定,任何 Agent 都不能自动覆盖。sqlite-vec → FTS5 → LIKE → JSONL 备份,不会崩。要求:Python 3.11+
# 克隆
git clone https://github.com/billy12151/memory-arbiter-mcp.git
cd memory-arbiter-mcp
# 安装
python3.11 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
pip install -e .
# 可选:启用语义召回增强(sqlite-vec)
pip install '.[vec]'
# 启动
memory-arbiter-mcp
在你的工具的 MCP 配置中加入(完整示例见 examples/ 目录):
{
"mcpServers": {
"memory-arbiter": {
"command": "/path/to/memory-arbiter-mcp/.venv/bin/memory-arbiter-mcp",
"env": {
"MEMORY_ARBITER_CLIENT": "zcode",
"MEMORY_ARBITER_AGENT_ID": "zcode-default",
"MEMORY_ARBITER_DB_PATH": "~/.local/share/memory-arbiter/memory.sqlite3"
}
}
}
}
每个工具改一下
MEMORY_ARBITER_CLIENT标识(zcode、codex、cursor、claude-code),共享同一个DB_PATH——这就是跨工具记忆共享的关键。
⚠️ 需要新建会话:MCP Server 在客户端启动时加载,已经打开的会话不会识别新添加的 Server。配置好后请新建一个会话。
| 客户端 | 配置文件位置 |
|---|---|
| ZCode | ~/.zcode/v2/ 下 MCP 配置 |
| Codex CLI | ~/.codex/ 下 MCP 配置 |
| Claude Code | 项目根目录 .mcp.json |
| Cursor | ~/.cursor/mcp.json |
| 工具 | 说明 |
|---|---|
memory_write | 写入记忆(source_type=user_confirmed 自动锁定) |
memory_search | 搜索记忆(FTS5 → LIKE 自动降级) |
memory_compare | 比较两条记忆,只返回解释 |
memory_arbitrate | 仲裁冲突,自动判定胜者(apply=true 时落记录) |
memory_confirm | 用户确认某条记忆,锁定保护 |
memory_list_conflicts | 列出未解决的冲突 |
memory_status | 查看运行状态、模式、降级原因 |
换电脑只需拷贝一个文件:
# 拷贝数据库
cp ~/.local/share/memory-arbiter/memory.sqlite3 新电脑:~/.local/share/memory-arbiter/
# 重新安装项目(.venv 不要拷贝,新机器上重建)
python3.11 -m venv .venv
source .venv/bin/activate
pip install -e .
python3.11 -m pip install -r requirements.txt
python3.11 -m pytest
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.