All MCP Servers
AI & MemoryMCP Registryoci9 toolsB · 71

MCP Memory

io.github.GermaniU · Updated

Local persistent memory for AI agents: SQLite + FTS5 (BM25) lexical search, zero external infra.

At a glance

MCP Memory is an MCP server in the AI & Memory category. It runs locally over stdio via `docker run -i --rm ghcr.io/germaniu/mcp-memory:0.6.0`, and declares no required credentials. It exposes 9 tools, including memory_save, memory_search and memory_update. It scores B (71/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 1GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install MCP Memory in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install MCP Memory in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add mcp-memory -- docker run -i --rm ghcr.io/germaniu/mcp-memory:0.6.0
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. memory_save, memory_search, memory_update). It discovers them automatically.

What does MCP Memory need from you?

Configuration only — Declares config values but no credentials.

  • DB_PATHoptionalEnvironment variable

    Path to the SQLite file inside the container. Keep it under the mounted volume (/data) so memories survive restarts.

Pass secrets through your shell environment rather than committing them into a config file.

What tools does MCP Memory expose? (9)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

What the code can do

Source analysis currently covers npm packages only. This server ships as a container image, whose contents are not readable the same way.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a Docker container with whatever mounts and env you pass it.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 5 days ago — Actively maintained.
  • Repository created 26 days ago — Very new project with little track record yet.
  • 1 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 71

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 5 days ago.

  • Adoption20%9%

    1 stars.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%50%

    No pinned version — installs resolve to whatever is latest at launch.

Documentation

Full README

English · Español

MCP Memory — Memoria local para agentes IA vía MCP

Lleva la memoria de tu agente IA a cualquier máquina. Servidor MCP open source que da memoria persistente con búsqueda léxica (BM25) a Claude Desktop, Claude Code, OpenCode, Cursor, Continue y cualquier cliente compatible con Model Context Protocol. SQLite + FTS5, cero infra externa, 100% en tu hardware.

Tags: mcp-server · ai-agents · sqlite · fts5 · bm25 · claude-code · cursor · opencode · lexical-search · agent-memory · local-first · self-hosted

<sub>El agente guarda algo en una sesión y lo recuerda en otra — mismo archivo SQLite, proceso nuevo. Sin nube, sin vectores, sin servicios extra.</sub>


💡 Por qué existe

Los agentes IA olvidan todo entre conversaciones. Las soluciones existentes son cloud-only, multi-tenant pesado, o están atadas a un único cliente. MCP Memory resuelve esto con tres ideas simples:

  1. Tu memoria, tu máquina. Un solo archivo SQLite local. Cero datos en la nube, cero servicios externos que levantar.
  2. Conectas una vez, funciona en todos lados. Es un servidor MCP estándar — cualquier cliente que hable MCP lo usa sin custom code.
  3. Cero overhead. pip install y tienes 9 tools listas para tu agente en segundos — sin Docker, sin modelos que descargar.

⚡ Quickstart

Hay dos formas de correrlo. Elige una:

| Modo | Cuándo | Cómo arranca | |------|--------|--------------| | stdio | Claude Desktop, Claude Code, Cursor… (lo más simple) | El cliente lanza el proceso él solo. No hay server de fondo ni puerto. | | HTTP | Varios clientes contra un mismo server, Docker, clientes web | Lo arrancas tú y queda escuchando en http://localhost:8765/mcp. |

Opción A — stdio (sin dejar nada corriendo)

Excerpt — the full document is on GitHub.

Maintain MCP Memory? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![MCP Memory on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-germaniu-mcp-memory)](https://mcp-skills-hub.vercel.app/mcps/io-github-germaniu-mcp-memory)

Catalog data refreshed . Something wrong? Report it.