Memkeeper MCP server
io.github.teflon07/memkeeper·v0.5.3·2 starsLocal-first memory for AI agents: on-device hybrid retrieval over a single SQLite file.
2 stars
Reviews
Write oneNobody has reviewed Memkeeper yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Memkeeper tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 32 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Memkeeper compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 35% of 802 Databases servers
- GitHub stars
- 2
- more than 60% of 602 Databases servers
Install Memkeeper in Claude Code, Cursor or VS Code
claude mcp add memkeeper -- docker run -i --rm ghcr.io/teflon07/memkeeper:0.5.3
What the publisher says
From the Memkeeper repository's README, as published. We do not edit it. Read it on GitHub
Most software has the memory of a goldfish. This one doesn’t.
memkeeper
Local-first memory for AI agents. A fast, embeddable memory engine that stores, ranks, and retrieves an agent's durable context, entirely on your machine, with no required network or LLM calls.
Memkeeper is the open-source, local-first control plane that AI agents run on: durable memory, project context, coordinated task handoffs, and deny-by-default permissions, all deterministic and on your own machine. This repo is the memory engine at its core.
ℹ️ Generated release mirror. This repo is generated from a private
development repo and published as releases. The main branch may be
regenerated, so pin to tagged releases (or the release artifacts) rather
than to arbitrary main commits — tagged releases are stable. See
CONTRIBUTING.md for how to contribute; issues, security
reports, and design feedback are the best paths today.
semantic embeddings and a cross-encoder reranker.
- Local-first. A single SQLite database. No server, no cloud, no telemetry.
- Fast at prompt time. Deterministic BM25/FTS retrieval with optional ONNX
retention model that promotes recurring, high-signal memories to a durable tier.
- Durable by design. Atomic writes, schema-versioned storage, and a
Real CLI output, formatted for readability via scripts/mkfmt. The search query shares no keywords with the memory it surfaces.
Status: pre-release (v0.5.3). APIs and the wire protocol may change before 1.0.
Quickstart
# Install the latest release binary (macOS arm64 / Linux x86_64) to ~/.local/bin.
# It's self-contained — nothing else to install.
curl -fsSL https://raw.githubusercontent.com/teflon07/memkeeper/main/install.sh | bash
# Optional, one-time: fetch on-device semantic models. Lexical search works without it.
memkeeper pull-models
# Create a store, remember something, search it back.
memkeeper init
memkeeper remember --json '{"content":"memkeeper stores memories in a local SQLite database"}'
memkeeper search --json '{"query":"where are memories stored","limit":3}'That's the whole install: a self-contained binary, no runtime network/LLM/API key. Prefer not to pipe a script to your shell? Grab a binary from the releases page and verify its .sha256, or build from source. The store defaults to ~/.memkeeper/store.sqlite when --store is omitted; a --json value can also be @ or - (stdin) instead of an inline string, which avoids shell-quoting pitfalls (handy in Windows PowerShell).
Upgrade from v0.2.x
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Memkeeper: common questions
- Is Memkeeper MCP server safe?
- Mostly: it is graded B (75/100). Read the Memkeeper safety report
- How do I install Memkeeper?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Memkeeper need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Memkeeper maintained?
- The last commit was 72 days ago (2026-08-24). The latest release is v0.5.3.
- What can I use instead of Memkeeper?
- Servers from other publishers that do the same job: Remem MCP server, open-memex MCP server and SAME - Stateless Agent Memory Engine MCP server.
- How does Memkeeper compare with other Databases MCP servers?
- safety score 75/100 (higher than 35% of 802 Databases servers); github stars 2 (more than 60% of 602 Databases servers). Full comparison.
Alternatives to Memkeeper
Same job from other publishers: the closest match first, then the best rated.
- RememLocal-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.not reviewedEstablishedB
- open-memexLocal-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.not reviewedGrowingB
- SAME - Stateless Agent Memory EnginePersistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.not reviewedGrowingB
- remem-mcp — Local-first MCP Memory + CodeGraph + WikiLocal-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.not reviewedGrowingB
- sqlite-graph-memoryRecall over your markdown notes: vector search plus your [[wikilinks]] as a graph, in SQLite.not reviewedGrowingA