MCP server: One MCP server.

Hypermarrow

@qianqiuwanziRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

Local-first AI memory MCP server. Record, recall and consolidate memory on your own machine.

AI memoryv0.1.1MITJavaScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: creates or changes data: records, files, settings.

What it costs

Free

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).

npmhypermarrow-mcpv0.1.1

Run

npx -y hypermarrow-mcp

MCP client config

{
  "mcpServers": {
    "hypermarrow": {
      "command": "npx",
      "args": [
        "-y",
        "hypermarrow-mcp"
      ]
    }
  }
}
README1 min read

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 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

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.

Similar modules

Browse AI memory