Other · Local MCP server
Memento Protocol
Persistent memory for AI agents. Store what matters, recall by meaning, skip the rest.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.myrakrusemark/memento-protocol- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-18
- Updated
- 2026-02-18
- Publisher
- myrakrusemark (GitHub)
- Repository
- github.com/myrakrusemark/memento-protocol
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | memento-mcp | 0.1.1 | stdio |
How to connect Memento Protocol
Memento Protocol runs locally from a Node.js package published to the npm registry: memento-mcp version 0.1.1. 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 memento-mcp@0.1.1. It reads these environment variables: MEMENTO_API_KEY (required, secret), MEMENTO_API_URL (required) and MEMENTO_WORKSPACE (required); set them 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-protocol": {
"command": "npx",
"args": [
"-y",
"memento-mcp@0.1.1"
],
"env": {
"MEMENTO_API_KEY": "<secret>",
"MEMENTO_API_URL": "<value>",
"MEMENTO_WORKSPACE": "<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 other servers
| Server | Runs |
|---|---|
| Melody GenieWrite lyrics in 100+ styles, score them, generate full songs with 4 engines, split stems. OAuth. | Remote · HTTP |
| melta UIAI-Ready design system MCP: melta UI tokens, component contracts, 99 rules, check_html self-verify. | Local · stdio |
| MemdataPersistent memory for AI agents. Store context, retrieve it semantically. | Local · stdio |
| memdslReview-gated declarative long-term memory with bounded read-only MCP access. | Local · stdio |
| MemeoracleMemecoin Intelligence MCP — 9 tools: rug check, momentum, whale watch, 80+ chains. | Remote · HTTP |
| MemfleetShared, governed memory for fleets of AI agents: judged contributions, provenance, operator control. | Remote · HTTP |
| MemharnessBi-temporal, provenance-carrying long-term memory for AI agents, in one SQLite file. | Local · stdio |
| MemkeeperLocal-first memory for AI agents: on-device hybrid retrieval over a single SQLite file. | Local · stdio |