Memento MCP server
com.runmemento/memento·v0.9.2·24 starsLocal-first, LLM-agnostic memory layer for AI assistants.
24 stars75 downloads/wk
Reviews
Write oneNobody has reviewed Memento yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Memento 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-27 · same rubric, same numbers if you re-run it
- Code scan11 source files scanned15/25
- –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 133 days ago8/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Findings (2)
- mediumnpm install lifecycle script present
install.script - mediumnpm install lifecycle script present
install.scriptpackage.json: …ildinfo", "test": "vitest run", "postinstall": "node ./scripts/postinstall.mjs" } }…
How Memento compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 25% of 4,460 AI and agents servers
- GitHub stars
- 24
- more than 90% of 2,711 AI and agents servers
- Downloads a week
- 75
- more than 56% of 1,538 AI and agents servers with a package
Install Memento in Claude Code, Cursor or VS Code
Runs npx -y @psraghuveer/memento on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add memento -- npx -y @psraghuveer/memento
What the publisher says
From the Memento repository's README, as published. We do not edit it. Read it on GitHub
A local-first, LLM-agnostic memory layer for AI assistants runmemento.com
Every AI session starts the same way: re-explaining your preferences, your project's conventions, the decisions you made last week, the dead-ends to avoid. Each tool solves this in its own siloed way (CLAUDE.md, .cursorrules, copilot-instructions.md, ChatGPT Memory) — but you, the human, are the one constant. Your memory shouldn't fragment across vendors.
Memento is one place where that memory lives. It runs an MCP server over a local SQLite file, so any MCP-capable AI assistant — Claude Desktop, Claude Code, Cursor, GitHub Copilot, Cline, OpenCode, Aider, a research bot, a custom agent — can read and write durable, structured memory about you, your work, and your decisions. Local-first, no outbound network calls by default, no vendor lock-in.
A fresh chat with no prior context — Memento supplies the memory of what was decided last week.
Quickstart
Three steps from zero to a working memory layer:
1. Run init (interactive on a TTY)
npx @psraghuveer/memento initCreates the database under the XDG default ($XDGDATAHOME/memento/memento.db, typically ~/.local/share/memento/memento.db on POSIX), runs migrations, and — on a TTY — walks you through four one-keystroke setup questions:
- Your preferred name. Stored as the user.preferredName config key so memories read "Raghu prefers …" instead of "The user prefers …".
- Install the bundled skill? One y/N. Copies skills/memento/ into ~/.claude/skills/ for clients that load Anthropic-format skills.
- Seed with a starter pack? Pick one of four bundled packs (engineering-simplicity, pragmatic-programmer, twelve-factor-app, google-sre) so your store has useful memories on day one. Skip to start empty.
- Auto-install the persona snippet? Detects AI clients on your machine and writes a marker-wrapped block to each one's user-scope custom-instructions file (~/.claude/CLAUDE.md for Claude Code, ~/.config/opencode/AGENTS.md for OpenCode, ~/Documents/Cline/Rules/memento.md for Cline). Idempotent and removable. UI-only clients (Cowork, Claude Desktop, Claude Chat, Cursor User Rules) get printed paste instructions instead.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Memento: common questions
- Is Memento MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Memento safety report
- How do I install Memento?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Memento need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Memento maintained?
- The last commit was 171 days ago (2026-05-17). The latest release is v0.9.2.
- What can I use instead of Memento?
- Servers from other publishers that do the same job: Agent Recall MCP server, Basic Memory MCP server and agent-device MCP server.
- How does Memento compare with other AI and agents MCP servers?
- safety score 65/100 (higher than 25% of 4,460 AI and agents servers); github stars 24 (more than 90% of 2,711 AI and agents servers); downloads a week 75 (more than 56% of 1,538 AI and agents servers with a package). Full comparison.
Alternatives to Memento
Same job from other publishers: the closest match first, then the best rated.
- Agent RecallCorrection-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.not reviewedEstablishedA
- Basic MemoryLocal-first knowledge management with bi-directional LLM sync via Markdown files.not reviewedWidely usedB
- agent-deviceOpen source device layer for AI agents: control mobile, web, TV, and desktop apps over MCPnot reviewedWidely usedA
- HOL GuardLocal-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.not reviewedEstablishedA
- Agent-Native ChatMinimal chat-first app with durable threads, actions, and the app-agent loopnot reviewedEstablishedA