hypermarrow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERMARROW_ENDPOINT | No | Optional custom backend endpoint. If set, the server will send memory data to this endpoint instead of (or in addition to) storing locally. By default, all memory lives under ~/.hypermarrow/memory.json and nothing is sent to the cloud. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| recall_memoryA | Recall the most relevant stored contexts given a query. Returns up to 5 ranked entries. |
| consolidateA | Merge duplicate memory entries and age out entries older than 90 days. Returns a short summary. |
| file_anchorA | Anchor a short name to an absolute local file path so future queries can resolve "the spec" to the real document. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.