Developer · Local MCP server
Memento
Local-first, LLM-agnostic memory layer for AI assistants.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.runmemento/memento- Version
- 0.9.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-17
- Updated
- 2026-05-17
- Publisher
- com.runmemento
- Namespace
- Namespace verified by the MCP Registry via the domain runmemento.com · how
- Website
- runmemento.com
- Repository
- github.com/veerps57/memento.git
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @psraghuveer/memento | 0.9.2 | stdio |
How to connect Memento
Memento runs locally from a Node.js package published to the npm registry: @psraghuveer/memento version 0.9.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @psraghuveer/memento@0.9.2. It reads the environment variable MEMENTO_DB; set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"memento": {
"command": "npx",
"args": [
"-y",
"@psraghuveer/memento@0.9.2"
],
"env": {
"MEMENTO_DB": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Mem0 CloudA hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):... | Remote · HTTPLive check: ✓ handshake |
| MemAuthorityGit-backed long-term memory authority for AI agents via MCP. | Local · stdio |
| MemCellLiving memory for AI coding agents: recall before acting, report outcomes so confidence is earned. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MemdocsGit-native project memory for AI assistants with audit compliance. | Local · stdio |
| MementoAgent memory MCP server with 4-type cognitive memory, hybrid search, and TTL-based forgetting. | Local · stdio |
| MementoHosted MCP memory for coding agents: persistent across sessions, editable markdown, team sharing. | Remote · HTTPLive check: sign-in required |
| memexPersistent memory for AI agents - semantic + recency search, ONNX embeddings, Docker Compose. | Local · HTTP |
| MemexOne searchable memory of your Claude.ai chats and Claude Code sessions, served over MCP. | Local · stdio |