Hive Memory Enterprise MCP
Python MCP server for Cursor, Claude Code, and other agents. Connects to a self-hosted Hive Memory API with PII masking, governance tools, and FinOps feedback.
Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
Cursor configuration
{
"mcpServers": {
"hive-memory": {
"command": "uvx",
"args": ["hive-memory-mcp"],
"env": {
"HIVE_MEMORY_BACKEND_URL": "https://hive.yourcompany.com/api/v1",
"HIVE_API_KEY": "hm_live_..."
}
}
}
}
Environment variables
| Variable | Required | Description |
|---|---|---|
HIVE_MEMORY_BACKEND_URL |
Yes | API base URL (e.g. http://localhost:8000/api/v1) |
HIVE_API_KEY |
Yes* | Service account API key (hm_live_...) |
HIVE_MEMORY_API_KEY |
Alt | Same as HIVE_API_KEY |
ENTERPRISE_WEBHOOK_URL |
No | Slack/Discord webhook (server-side on API, not MCP) |
* Required for remote/production APIs. Local dev may use JWT from dashboard only for the web UI; MCP always needs an API key.
Local development
cd mcp-server-enterprise
uv sync
export HIVE_MEMORY_BACKEND_URL=http://localhost:8000/api/v1
export HIVE_API_KEY=hm_live_your_key
uv run python main.py
Tools
save_team_memory— save gotcha with PII sanitization + audit logsearch_team_memories— vector search with utility boostrecord_memory_feedback— FinOps ROI ledgermoderate_team_memory— approve / deprecate / editscan_duplicate_memories/merge_duplicate_memoriesget_analytics_and_roirun_memory_decay_auditsynthesize_team_knowledge
Troubleshooting
- 401 Unauthorized — check API key scopes (
memories:read,memories:write,governance:read) - TLS errors — ensure VPS certificate is valid; corporate proxy may need
HTTP_PROXY - Connection refused — verify
HIVE_MEMORY_BACKEND_URLand that the backend is reachable from your machine
Metadata
Release files for hive-memory-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hive_memory_mcp-0.1.0.tar.gz | 7.3 kB | Without provenance | Details for hive_memory_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hive_memory_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for hive_memory_mcp-0.1.0-py3-none-any.whl |
Total release size: 16.8 kB
Release files / hive_memory_mcp-0.1.0.tar.gz
| Download URL | hive_memory_mcp-0.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91ed20b8ad5eb48e17bfc75999effb091dea7bbbf1b12d41fccbd616c6ff62fb
|
|
BLAKE2b-256 checksum How to use checksums |
ec45e6e0bda8003ca371886d6e2641f1b8bf9f7fc1369d478e7889c76138aad4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Release files / hive_memory_mcp-0.1.0-py3-none-any.whl
| Download URL | hive_memory_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc67a976876a6637a43effa42f2b108258b79c0d2784fe6657bbea3d6670f4c0
|
|
BLAKE2b-256 checksum How to use checksums |
8ed492541bb182c3766f4f404ba4bdcc858cdc3267676cd24448d4774b0564a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for hive-memory-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.