Local-first AI memory MCP server. Record, recall and consolidate memory on your own machine.
Runs on your machine from its package; the steps are below.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y hypermarrow-mcp
MCP client config
{
"mcpServers": {
"hypermarrow": {
"command": "npx",
"args": [
"-y",
"hypermarrow-mcp"
]
}
}
}Local-first AI memory layer for the Model Context Protocol.
hypermarrow-mcp lets any MCP-compatible client read and write your long-term memory:
record_context – remember a decision, fact, or preferencerecall_memory – retrieve the most relevant past contextconsolidate – merge duplicates and age out stale entriesfile_anchor – map a short name to a local file pathAll memory lives under ~/.hypermarrow/memory.json on your own machine. Nothing is sent to the cloud unless you explicitly set HYPERMARROW_ENDPOINT to your own backend.
npx -y hypermarrow-mcp
Or add to your MCP client config:
{
"mcpServers": {
"hypermarrow": {
"command": "npx",
"args": ["-y", "hypermarrow-mcp"]
}
}
}
Memory data is stored locally. The server only talks to the client over stdio and, optionally, to a user-configured HYPERMARROW_ENDPOINT. No telemetry, no cloud sync by default.