Metadata-Version: 2.4
Name: memory-hive-mcp
Version: 0.1.0
Summary: Local-first personal memory for your AI agents — an MCP stdio bridge to the Hive running on your own machine.
Author: Memory Hive
License-Expression: MIT
Project-URL: Homepage, https://apps.apple.com/app/id6806992983
Project-URL: Repository, https://github.com/330899935/memory-hive-ios
Project-URL: Source, https://github.com/330899935/memory-hive-ios
Keywords: mcp,model-context-protocol,memory,local-first,privacy,ai-agents
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: Operating System :: MacOS
Classifier: Programming Language :: Python :: 3
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Requires-Python: >=3.8
Description-Content-Type: text/markdown
License-File: LICENSE
Dynamic: license-file

# 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](https://modelcontextprotocol.io) 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

```bash
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`):

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

### Environment variables

| Name | Required | Description |
| --- | --- | --- |
| `HIVE_AGENT_ID` | yes | Agent id issued by your own Hive. |
| `HIVE_AGENT_TOKEN` | yes | Access token issued when the agent was registered. Keep it secret. |
| `HIVE_MCP_URL` | no | Hive MCP endpoint. Defaults to `http://127.0.0.1:8768/mcp`. |

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