hypermarrow-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hypermarrow-mcp Remember that I prefer dark mode in code editors."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
HyperMarrow MCP Server
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 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
npx -y hypermarrow-mcpOr add to your MCP client config:
{
"mcpServers": {
"hypermarrow": {
"command": "npx",
"args": ["-y", "hypermarrow-mcp"]
}
}
}Related MCP server: mcp-memory-system
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.
Available Tools
4 toolsconsolidateA
Merge duplicate memory entries and age out entries older than 90 days. Returns a short summary.
Inputs: no named parameters.
file_anchorA
Anchor a short name to an absolute local file path so future queries can resolve "the spec" to the real document.
Inputs: name (required), path (required).
recall_memoryA
Recall the most relevant stored contexts given a query. Returns up to 5 ranked entries.
Inputs: query (required).
record_contextB
Capture a piece of local working context (a decision, a fact, a preference) into persistent memory. Nothing is uploaded to the cloud unless HYPERMARROW_ENDPOINT is set.
Inputs: context (required), tags.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose: writing context, recalling it, maintaining memory, and resolving path anchors. No two tools overlap in function.
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.
Four tools tightly cover the server's memory-management scope without redundancy or bloat.
The core write/read/maintenance lifecycle is covered, including path anchoring. Explicit per-entry update/delete is absent, but consolidate handles duplication and aging.
Maintenance
Related MCP Connectors
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Hosted agent memory: store, search, and recall facts across sessions from any MCP client.
Cross-tool persistent memory and context for AI assistants over MCP.
Cross-session memory for AI agents with a Source Receipt for every memory, over MCP.
Related MCP Servers
- AlicenseCqualityBmaintenanceProvides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.3192 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI clients with a persistent, readable and writable long-term memory layer over MCP, enabling creation, retrieval, tagging, updating, and deletion of memories across sessions.49 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent local memory management, including semantic recall, knowledge graph traversal, and automatic memory consolidation, enabling structured long-term memory across MCP clients.Apache 2.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables LLM clients to manage hierarchical working, dialogue, and episodic memories with decay-aware consolidation, hybrid lexical/vector retrieval, knowledge-graph expansion, and semantic caching over MCP.MIT