Holographic Memory MCP
Persistent local memory for AI agents through the Model Context Protocol. The server stores memories on your machine and supports stdio and streamable HTTP transports.
Website · Documentation · Source · License
Run
Python 3.9 or newer is required for this launcher. Run it directly with uvx:
uvx holographic-memory-mcp
The default stdio transport works with MCP clients that launch a local command. To share one server between clients, use streamable HTTP:
uvx holographic-memory-mcp --transport http
The HTTP endpoint defaults to http://127.0.0.1:8765/mcp. See the MCP guide for client configuration, storage locations, encryption, authentication, and available flags.
What the server provides
| Tool | Purpose |
|---|---|
remember |
Save or update a memory. |
recall |
Find memories relevant to a query. |
search |
Search with explicit filters and ranking options. |
get, list |
Read one memory or page through a store. |
forget |
Delete selected memories. |
stats, export |
Inspect and export a store. |
The server also exposes memory resources and prompts. Memories persist across client sessions. By default, recall uses lexical search; semantic recall requires a build configured with a local embedding model.
Launcher and binary
The package installs a small Python launcher. On first run, it downloads the matching prebuilt hms-mcp binary from the GitHub release and verifies its SHA-256 against a checksum table shipped in the package. The server itself runs locally; the launcher needs network access for that first binary download.
Set HMS_MCP_BINARY to run your own hms-mcp build. HMS_MCP_CACHE_DIR changes the download cache. The MCP guide covers the server's HMS_MCP_* configuration variables.
The same launcher is available on npm.
1 maintainer
Metadata
1 maintainer
Release files for holographic-memory-mcp 0.1.1
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 | |
|---|---|---|---|---|
| holographic_memory_mcp-0.1.1.tar.gz | 8.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| holographic_memory_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.4 kB
Release files / holographic_memory_mcp-0.1.1.tar.gz
| Download URL | holographic_memory_mcp-0.1.1.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e635d9b4e8a00b978a464dd580528ac0dab9619f303931d50ce5be3063ed26e
|
|
BLAKE2b-256 checksum How to use checksums |
e8ad7c293fa6801254f10f401d4616f7d7e58d07f3279a071119fc3ff3fe9a54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logRelease files / holographic_memory_mcp-0.1.1-py3-none-any.whl
| Download URL | holographic_memory_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
737b1ffd67b9a1cabb31d67256070dbb25adf33fbf39ef5dfa8cd14bffccd0d9
|
|
BLAKE2b-256 checksum How to use checksums |
32e3572825985ff0e522cf703d024ed7948ca47d56630f94bceac951370b2587
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logSecurity for holographic-memory-mcp 0.1.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for holographic_memory_mcp-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.
Transparency logA 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.
