memory-hive-mcp

Local-first personal memory for your AI agents — an MCP stdio bridge to the Hive running on your own machine.

memory-hive-mcp is a thin Model Context Protocol bridge. It lets any MCP-capable host (Claude Desktop, Cursor, and friends) read and write your memory — stored on your computer, by your Hive, and never uploaded anywhere.

This package contains no memory engine. It only relays MCP protocol traffic to the Hive app already running on your machine (127.0.0.1:8768). Your data never passes through this bridge as stored state, and nothing leaves your computer.

Install

pip install memory-hive-mcp

Requires Python 3.8+. No third-party dependencies.

This installs the command memory-hive-mcp. (Note: an unrelated project also owns the plain hive-mcp name on PyPI — that is not us.)

Prerequisite: a running Hive

memory-hive-mcp talks to the Hive on your own machine. Get it from the Mac App Store:

https://apps.apple.com/app/id6806992983

Then register an agent inside the Hive (POST /api/agent/register) to obtain an agent_id and access_token.

Configure your MCP host

Add the server to your host's MCP config. For Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "hive-memory": {
      "command": "memory-hive-mcp",
      "env": {
        "HIVE_AGENT_ID": "your-agent-id",
        "HIVE_AGENT_TOKEN": "your-access-token"
      }
    }
  }
}

Environment variables

Why a bridge, not a bundle

Your memory should have exactly one writer: the Hive on your machine. This bridge therefore speaks protocol and nothing else — no data files are opened, no state is cached, no engine is duplicated. That keeps your memory single-sourced, local, and under your control.

License

MIT