Developer · Remote MCP server
Memento
Hosted MCP memory for coding agents: persistent across sessions, editable markdown, team sharing.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mementoagi/memento- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-20
- Updated
- 2026-09-20
- Publisher
- mementoagi (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mementoagi) · how
- Website
- mementoagi.com
- Repository
- github.com/mementoagi/memento
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.mementoagi.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Memento
Memento is a remote MCP server: there is nothing to install. Its endpoint is https://api.mementoagi.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 |
|---|---|
| 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 |
| MementoLocal-first, LLM-agnostic memory layer for AI assistants. | Local · stdio |
| MementoAgent memory MCP server with 4-type cognitive memory, hybrid search, and TTL-based forgetting. | Local · stdio |
| 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 |
| MemexZettelkasten-based agent memory system with bidirectional links. | Local · stdio |
| memexLocal MCP memory for coding agents. SQLite on your machine - preferences persist across chats. | Local · stdio |