A lightweight, local-first persistent memory server for AI tools. Stores structured memory entries in SQLite and exposes them over both the Model Context Protocol (MCP) and a plain REST HTTP API
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mini-memory-mcp": {
"args": [
"tsx",
"/absolute/path/to/mini-memory-mcp/server/index.ts",
"--stdio"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A lightweight, local-first persistent memory server for AI tools. Stores structured memory entries in SQLite and exposes them over both the Model Context Protocol (MCP) and a plain REST HTTP API. Comes with a React UI for browsing and managing memories in the browser.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / ai-ml
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
An autonomous agent that conducts deep research on any data using any LLM providers
🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration
MCP Security Weekly
Get CVE alerts and security updates for Mini Memory Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A lightweight, local-first persistent memory server for AI tools. Stores structured memory entries in SQLite and exposes them over both the Model Context Protocol (MCP) and a plain REST HTTP API. Comes with a React UI for browsing and managing memories in the browser.
namespace:value convention (e.g. project:myapp, lang:typescript)mini-memory-mcp/
├── server/
│ ├── index.ts # Entry point — stdio or HTTP mode
│ ├── db.ts # SQLite init, WAL, FTS5 schema & triggers
│ ├── memory-store.ts # CRUD + FTS search logic
│ ├── routes.ts # Express REST router (/api/memories)
│ └── mcp-tools.ts # MCP tool definitions (memory_list/create/read/update/delete/search)
├── ui/
│ └── src/
│ ├── api.ts # Typed fetch helpers
│ ├── hooks/useMemories.ts # State, debounced search, CRUD
│ └── components/ # MemoryList, MemoryCard, MemoryForm, SearchBar
├── data/
│ └── mini-memory.sqlite # Auto-created on first run
└── package.json
# Install server dependencies
npm install
# Install UI dependencies
cd ui && npm install
npm start
Server starts on port 5172.
GET http://localhost:5172/http://localhost:5172/api/memorieshttp://localhost:5172/mcpnpm run start:mcp
The process speaks the MCP protocol over stdin/stdout. No HTTP server is started.
With the HTTP server already running:
cd ui
npm run dev
UI starts on port 5173 and proxies /api requests to the server on port 5172.
Open http://localhost:5173 in your browser.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"mini-memory-mcp": {
"command": "npx",
"args": ["tsx", "/absolute/path/to/mini-memory-mcp/server/index.ts", "--stdio"]
}
}
}
Or with npm run start:mcp:
{
"mcpServers": {
"mini-memory-mcp": {
"command": "npm",
"args": ["run", "start:mcp"],
"cwd": "/absolute/path/to/mini-memory-mcp"
}
}
}
claude mcp add mini-memory-mcp -- npx tsx /absolute/path/to/mini-memory-mcp/server/index.ts --stdio
Add to .vscode/mcp.json:
{
"servers": {
"mini-memory-mcp": {
"type": "stdio",
"command": "npx",
"args": ["tsx", "/absolute/path/to/mini-memory-mcp/server/index.ts", "--stdio"]
}
}
}
First start the server in HTTP mode (npm start), then point your MCP client at:
http://localhost:5172/mcp
The server follows the MCP Streamable HTTP spec: send a POST with no mcp-session-id header to initialize a session, then include the returned session ID in all subsequent POST/GET/DELETE requests.
| Tool | Description |
|---|---|
memory_list | List all memories, newest first. Filter by tags. Call at session start. |
memory_create | Create a new memory (title, content, optional tags) |
memory_read | Read full content of a single memory by ID |
memory_update | Partially update a memory — only changed fields needed |
| `memor |