hypermarrow-mcp
by qianqiuwanzi
README.md
# HyperMarrow MCP Server
> Local-first AI memory layer for the [Model Context Protocol](https://modelcontextprotocol.io/).
**hypermarrow-mcp** lets any MCP-compatible client read and write your long-term memory:
- `record_context` – remember a decision, fact, or preference
- `recall_memory` – retrieve the most relevant past context
- `consolidate` – merge duplicates and age out stale entries
- `file_anchor` – map a short name to a local file path
All 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.
## Install
```bash
npx -y hypermarrow-mcp
```
Or add to your MCP client config:
```json
{
"mcpServers": {
"hypermarrow": {
"command": "npx",
"args": ["-y", "hypermarrow-mcp"]
}
}
}
```
## Product
- Homepage: https://hm.qianshi.cool/
- Company: 千视科技 (qianshi.cool)
## Privacy
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.
TDQS
A3.9/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a distinct purpose: writing context, recalling it, maintaining memory, and resolving path anchors. No two tools overlap in function.
Naming Consistency4/5
record_context and recall_memory follow verb_noun, file_anchor is a compound noun, and consolidate is a bare verb. Mostly consistent but slightly mixed.
Tool Count5/5
Four tools tightly cover the server's memory-management scope without redundancy or bloat.
Completeness4/5
The core write/read/maintenance lifecycle is covered, including path anchoring. Explicit per-entry update/delete is absent, but consolidate handles duplication and aging.