Local-MCP-Memory MCP server
Commit Nov 9, 2026Provides a persistent multi-agent memory and coordination engine that lets AI agents store, retrieve, and share contextual knowledge using SQLite.
Also known as coderooz/Local-MCP-Memory-Server
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 9, 2026
- License
- MIT
What is Local-MCP-Memory MCP?
Local-MCP-Memory provides a persistent multi-agent memory and coordination engine that lets AI agents store, retrieve, and share contextual knowledge using SQLite.
Summary generated from the project's README
About Local-MCP-Memory MCP server
Providing a shared context layer for multiple AI agents is what this server enables through a persistent coordination engine. It allows developers to store, retrieve, and rank contextual knowledge using an embedded SQLite database with full-text indexing. By using better-sqlite3, the system functions locally without requiring an external database server, making it suitable for private development environments.
Users can manage complex workflows by utilizing tools for task orchestration, issue tracking, and resource locking to prevent agent conflicts. The server supports a wide range of AI coding agents including Claude Desktop, Cursor, Windsurf, Cline, and Roo Code. It also features an external MCP server registry that allows for proxying calls to third-party servers using AES-256-GCM encrypted credentials.
Setup is handled via a global CLI that automates configuration across supported clients. Developers can interact with the system through 63 specialized tools, ranging from context management like store_context to project intelligence functions like create_project_map. The architecture supports both stdio for direct agent connection and an HTTP API for web dashboard access.
What you can do with it
- 1Maintaining long-term project contextDevelopers can instruct an AI to save important project details that persist across different chat sessions.
- 2Automating task and issue managementAn AI client can create, assign, and track the progress of specific development tasks or bugs.
- 3Centralizing third-party MCP toolsYou can register and connect to other MCP servers through this central registry to manage multiple toolsets.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
MCP_AGENTMCP_DB_PATHMCP_MASTER_SECRETMCP_PROJECTMCP_SCOPE
| Name | Description | |
|---|---|---|
| MCP_AGENT | — | |
| MCP_DB_PATH | — | |
| MCP_MASTER_SECRET | — | |
| MCP_PROJECT | — | |
| MCP_SCOPE | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablecoderooz/local-mcp-memory-server is public and reachablegithub.com/coderooz/local-mcp-memory-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-09github.com/coderooz/local-mcp-memory-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubLocal MCP Memory Server
Local MCP Memory Server is a persistent multi-agent memory and coordination engine implementing the Model Context Protocol (MCP). Powered by embedded SQLite (better-sqlite3), it provides AI agents and humans with a shared, persistent context layer featuring full-text search, soft resource locks, project descriptors, task orchestration, issue tracking, and external MCP server proxying.
- Current Version:
v2.6.0 - Documentation Hub: docs/README.md
- Official Web Docs: https://coderooz.github.io/Local-MCP-Memory-Server/
Key Capabilities
- Persistent Agent Memory: Store, retrieve, update, and rank context entries across agent sessions with full SQLite FTS5 full-text indexing.
- Multi-Agent Coordination: Prevent conflicts using soft resource locks (
acquire_resource_lock,release_resource_lock) and live activity streams (record_activity). - Task & Issue Management: Priority scoring, dependency tracking, and capability-aware task auto-assignment.
- External MCP Server Registry: Register, connect, discover, and proxy calls to third-party MCP servers with AES-256-GCM encrypted credentials at rest.
- CLI & Auto-Configuration: Automated setup for 8 AI coding agents (Antigravity, OpenCode, Codex, Claude, Cursor, Windsurf, Cline, Roo Code).
- Embedded Zero-Config Storage: Uses local SQLite via
better-sqlite3with Write-Ahead Logging (WAL) and enforced foreign key constraints. No external database server required. - Security & Access Control: Dual JWT and programmatic API-key authentication for HTTP APIs, loopback binding by default, and fail-closed local execution sandboxing.
Quickstart
Option 1: Global CLI Auto-Configuration (Recommended)
Initialize the database and automatically configure all installed AI coding agents:
npx local-mcp-memory init
Or install globally:
npm install -g local-mcp-memory
local-mcp-memory init
Installation Source Note:
- npm Registry:
npm install -g local-mcp-memory- GitHub Release (Direct): You can also install directly from the tagged GitHub release via:
npm install -g https://github.com/coderooz/Local-MCP-Memory-Server.git#v2.6.1
The init command automatically:
- Detects your operating system and Node.js environment (
>=22.0.0). - Creates the per-user application directory (
~/.local-mcp-memoryor%LOCALAPPDATA%\local-mcp-memory) and initializes the SQLite database (mcp-memory.db). - Auto-generates persistent security secrets (
MCP_MASTER_SECRETand JWT signing secret). - Auto-detects and configures all 8 supported AI coding agents:
- Google Antigravity (
mcp_config.json) - OpenCode (
opencode.json) - OpenAI Codex CLI (
config.toml) - Claude Desktop (
claude_desktop_config.json) - Cursor (
mcp.json) - Windsurf (
mcp_config.json) - Cline (
cline_mcp_settings.json) - Roo Code (
mcp_settings.json)
- Google Antigravity (
- Preserves existing configuration comments and keys using an AST-safe parser, creating timestamped
.bakbackups.
Run system diagnostics anytime to verify your environment:
local-mcp-memory doctor
Option 2: Local Developer Setup
Clone the repository and run the server locally:
git clone https://github.com/coderooz/Local-MCP-Memory-Server.git
cd Local-MCP-Memory-Server
npm install
Configure your local environment (.env):
cp .env.example .env
# Runtime database location (defaults to local data directory)
MCP_DB_PATH=./data/mcp-memory.db
# Optional port override (default is dynamic allocation 47000-47020)
PORT=3799
# Project and agent context
MCP_PROJECT=local-mcp-memory
MCP_AGENT=antigravity
MCP_SCOPE=project
# Optional master encryption secret for MCP registry tokens (AES-256-GCM)
MCP_MASTER_SECRET=your-32-byte-master-secret-here
Start the MCP stdio server:
npm start
Start the HTTP API server with optional Web Dashboard:
npm run start:api
# Or start with visual dashboard:
npm run start:dashboard
Run the automated test suite (249 passing assertions):
npm test
CLI Command Summary (17 Commands)
The local-mcp-memory CLI provides complete management and data operations:
| Command | Category | Description |
|---|---|---|
init |
Setup | Initialize storage and auto-configure AI agent clients |
start |
Lifecycle | Start the MCP server in foreground or background |
stop |
Lifecycle | Stop running MCP server processes gracefully |
status |
Lifecycle | Check server health, active PID, and listening port |
doctor |
Diagnostics | Run comprehensive system and agent configuration diagnostics |
config |
Configuration | View or modify global configuration (path, get, set) |
update |
Maintenance | Verify database schema migrations and installation status |
uninstall |
Maintenance | Safely remove MCP server from agent configurations |
migrate |
Migration | Read-only inspection or execution of MongoDB-to-SQLite migration |
search <query> |
Data | Query stored memory using SQLite FTS5 full-text search |
store <content> |
Data | Store durable context or memory entry |
create-task <title> |
Data | Create a project-scoped coordination task |
list-tasks |
Data | List project tasks with optional status filtering |
create-issue <title> |
Data | Log an issue, bug, or coordination blocker |
list-issues |
Data | List open and resolved issues |
list-agents |
Data | List registered agents and active heartbeat statuses |
health |
Diagnostics | Probe the HTTP API server health endpoints |
For complete syntax, options, and PowerShell / POSIX examples for all 17 commands, see CLI Reference.
Core MCP Tools (63 Tools Discovered)
When connected to an AI agent via MCP, local-mcp-memory exposes 63 tools, including:
- Context & Memory:
store_context,search_context,update_context,get_connected_context,delete_context - Project Intelligence:
get_project_descriptor,set_project_descriptor,create_project_map,fetch_project_map - Coordination & Locks:
acquire_resource_lock,release_resource_lock,fetch_resource_locks,record_activity,fetch_activity - Tasks & Issues:
create_task,fetch_tasks,assign_task,update_task,create_issue,resolve_issue,fetch_issues - Agent Registry:
register_agent,heartbeat_agent,list_agents - External MCP Registry:
register_mcp_server,connect_mcp_server,discover_mcp_tools,proxy_mcp_call,get_mcp_health
For full integration details, client configuration snippets, and tool parameters, see MCP Integration Guide.
Documentation Directory
| Document | Purpose |
|---|---|
| Documentation Hub | Centralized index of all user and developer documentation |
| CLI Reference | Complete reference for all 17 CLI commands with copy-pasteable examples |
| Configuration Guide | Exhaustive reference of environment variables and configuration files |
| MCP Integration Guide | Client setup instructions for all 8 supported AI coding agents |
| Security Policy | Security model, JWT/API-key auth, AES-256-GCM encryption, and reporting |
| Contributing Guide | Guidelines for developers, PR lifecycle, and coding standards |
| Testing Guide | Instructions for running unit, conformance, resilience, and chaos tests |
| Adding an MCP Tool | Step-by-step developer guide for creating and registering new MCP tools |
| Adding an Agent Adapter | Guide for extending CLI init to support new AI agent clients |
License
This project is licensed under the MIT License.
Local-MCP-Memory MCP questions
What databases does this server use?
It uses an embedded SQLite database via better-sqlite3 with Write-Ahead Logging (WAL) and enforced foreign key constraints.
How can I prevent conflicts between multiple agents?
You can prevent conflicts using soft resource locks and live activity streams.
Does it require an external database server?
No, it uses local SQLite storage with zero configuration required.