local-memory-mcp
A local MCP server that provides semantic memory storage and retrieval for coding and AI agents, enabling durable context across chat sessions.
README
Local Memory MCP Server for Coding/AI Agents
This project is a local MCP (Model Context Protocol) server that exposes a small set of tools:
memory.search– semantic search over stored memoriesmemory.save– store a new memorymemory.supersede– mark an old memory as supersededmemory.delete– permanently remove a memory by idmemory.ping– sanity check / version output
What you can do with this project
- Keep durable coding context across chat sessions (decisions, preferences, gotchas, API contracts).
- Retrieve relevant past context semantically (not only keyword matching).
- Scope memory per project using
WORKSPACE_KEYwhile keeping one shared local database. - Correct memory over time by superseding outdated entries or deleting irrelevant ones.
- Run everything locally (no external vector DB required).
Typical workflow
- User asks a question in chat.
- Agent calls
memory.searchto fetch relevant context. - Agent answers using retrieved memory + current codebase context.
- New durable insight is stored via
memory.save. - Old memory is updated via
memory.supersedeor removed viamemory.delete.
It uses:
- Bun + TypeScript
- Zvec (
@zvec/zvec) as embedded in-process vector database (docs: https://zvec.org/en/docs/) - Ollama
/api/embedwith embeddinggemma for embeddings (docs: https://docs.ollama.com/capabilities/embeddings, model: https://ollama.com/library/embeddinggemma)
Prerequisites
- Bun installed
- Ollama installed and running locally
Pull the embedding model:
ollama pull embeddinggemma
Install
bun install
Run
bun run start
This runs an MCP server over stdio.
Test
bun run test
Current tests include:
tests/embed.test.ts– validates Ollama embedding response parsing and error handlingtests/memory-db.test.ts– validatessave,search,supersede, anddeleteon the Zvec-backed store
Environment variables
MEMORY_DB_PATH(default./data/memory.zvec)OLLAMA_BASE_URL(defaulthttp://localhost:11434)OLLAMA_EMBED_MODEL(defaultembeddinggemma)EMBEDDING_DIM(default768, must match your embedding model)WORKSPACE_KEY(defaultdefault)
VS Code
Workspace setup
This repo includes .vscode/mcp.json that registers this server:
- command:
bun - args:
run start
You can adjust environment variables in that file.
Always-on across all projects
If you want this MCP server available in all workspaces, add it to your User MCP configuration instead of only .vscode/mcp.json:
- Open Command Palette:
MCP: Open User Configuration - Add a server entry that starts this repo from a fixed directory.
Example (Linux):
{
"servers": {
"local-memory-mcp": {
"type": "stdio",
"command": "bun",
"args": ["--cwd", "/path/to/local-memory-mcp", "run", "start"],
"env": {
"MEMORY_DB_PATH": "/path/to/local-memory-mcp/data/memory.zvec",
"OLLAMA_BASE_URL": "http://localhost:11434",
"OLLAMA_EMBED_MODEL": "embeddinggemma",
"EMBEDDING_DIM": "768",
"WORKSPACE_KEY": "${workspaceFolderBasename}"
}
}
}
}
Notes:
- Use an absolute
MEMORY_DB_PATHso all projects use the same database. WORKSPACE_KEY=${workspaceFolderBasename}keeps memories separated per project automatically.- Enable VS Code setting
chat.mcp.autoStart(Experimental) to auto-start/restart MCP servers when needed.
Docs:
- https://code.visualstudio.com/docs/copilot/customization/mcp-servers
Claude Code
Add this server to Claude Code as a local stdio MCP server.
This repository already includes:
.mcp.jsonfor project-scoped Claude MCP configurationCLAUDE.mdfor memory-first agent behavior guidelines
User scope (all projects)
claude mcp add --transport stdio --scope user \
--env MEMORY_DB_PATH=/absolute/path/to/local-memory-mcp/data/memory.zvec \
--env OLLAMA_BASE_URL=http://localhost:11434 \
--env OLLAMA_EMBED_MODEL=embeddinggemma \
--env EMBEDDING_DIM=768 \
--env WORKSPACE_KEY=default \
local-memory-mcp -- bun --cwd /absolute/path/to/local-memory-mcp run start
Project scope (shared in repository)
claude mcp add --transport stdio --scope project \
--env MEMORY_DB_PATH=./data/memory.zvec \
--env OLLAMA_BASE_URL=http://localhost:11434 \
--env OLLAMA_EMBED_MODEL=embeddinggemma \
--env EMBEDDING_DIM=768 \
--env WORKSPACE_KEY=${PWD##*/} \
local-memory-mcp -- bun run start
Project .mcp.json example:
{
"mcpServers": {
"local-memory-mcp": {
"type": "stdio",
"command": "bun",
"args": ["run", "start"],
"env": {
"MEMORY_DB_PATH": "./data/memory.zvec",
"OLLAMA_BASE_URL": "http://localhost:11434",
"OLLAMA_EMBED_MODEL": "embeddinggemma",
"EMBEDDING_DIM": "768",
"WORKSPACE_KEY": "${PWD##*/}"
}
}
}
}
Notes:
--scope projectwrites to.mcp.jsonin the project root.--scope userstores the server in your user Claude configuration.- Keep all Claude flags before the server name, and put
--before the server command.
Useful commands:
claude mcp list
claude mcp get local-memory-mcp
claude mcp remove local-memory-mcp
Docs:
- https://code.claude.com/docs/en/mcp
Tool usage (examples)
Search
{
"tool": "memory.search",
"arguments": {
"query": "What is our policy for multi-session memory?",
"topK": 8,
"workspaceKey": "my-repo"
}
}
Save
{
"tool": "memory.save",
"arguments": {
"workspaceKey": "my-repo",
"type": "decision",
"summary": "We use zvec with Ollama embeddinggemma for long-term memory.",
"text": "Decision: The Copilot/agent memory sidecar stores vectors in zvec and generates embeddings via Ollama /api/embed using embeddinggemma.",
"tags": ["memory", "zvec", "ollama", "embeddinggemma"],
"importance": 0.8
}
}
Delete
{
"tool": "memory.delete",
"arguments": {
"workspaceKey": "my-repo",
"id": 42
}
}
Implementation notes
- The DB uses one Zvec collection with:
- dense vector field
embedding - scalar fields for metadata (
workspaceKey,type,summary, etc.)
- dense vector field
- KNN queries are executed through Zvec
querySyncwith metadata filters.
Tests
Run all tests:
bun run test
Current test coverage:
tests/embed.test.ts- parses successful Ollama
/api/embedresponses intoFloat32Array - verifies error handling when Ollama returns non-2xx responses
- parses successful Ollama
tests/memory-db.test.ts- validates
save+searchbehavior with workspace/type filtering - validates
supersedebehavior (superseded items are excluded from search) - validates
deletebehavior and returned payload semantics
- validates
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.