Memory Bridge MCP
Unified MCP memory server — bridges Mind (concept graph) and Honcho (semantic vector) memory with episodic timeline and LLM synthesis into a single MCP query surface.
pip install memory-bridge-mcp
What it does
Memory Bridge exposes 8 MCP tools that let any MCP-compatible agent (Claude Code, Codex, etc.) store and recall memories across three memory systems:
| Tool | Purpose |
|---|---|
bridge_remember |
Store a memory — auto-routes short facts to Mind, long content to Honcho |
bridge_recall |
Unified recall across both systems with Reciprocal Rank Fusion |
bridge_status |
Combined health report for all memory systems |
bridge_episode_record |
Record a structured session episode |
bridge_episode_recall |
Search episodic timeline by text, time, and tags |
bridge_timeline |
Chronological view of all session episodes |
bridge_synthesize |
Cortex Accelerator — synthesize knowledge across all memory |
bridge_contradictions |
Detect contradictory memories |
Quick start
# Install
pip install memory-bridge-mcp
# Run as MCP server (stdio)
memory-bridge
The server speaks the MCP protocol over stdio. Configure it as an MCP server in your agent's config:
{
"mcpServers": {
"memory-bridge": {
"command": "memory-bridge"
}
}
}
Memory systems
Mind (concept graph)
A local, zero-dependency concept graph with spreading-activation recall, Ebbinghaus forgetting, and dream consolidation. Stored in .mind/graph.json in the working directory. The vendored mind.py module handles all graph operations.
Honcho (semantic vector)
An optional semantic vector store running on http://127.0.0.1:8000. Provides embedding-based similarity search. If Honcho is unavailable, the bridge falls back to Mind only.
Episodic (session timeline)
A JSONL-based append-only log of structured session episodes. Stored in .memory-bridge/episodes.jsonl. Supports text search, time-range filtering, tag filtering, and session filtering.
Synthesis (Cortex Accelerator)
Optionally uses a local Ollama instance (http://127.0.0.1:11434) to synthesize related memories into concise summaries. Falls back to extractive key-sentence selection when LLM is unavailable.
Configuration
The server reads these environment variables:
| Variable | Default | Description |
|---|---|---|
HONCHO_BASE_URL |
http://127.0.0.1:8000/v3 |
Honcho API endpoint |
OLLAMA_BASE_URL |
http://127.0.0.1:11434 |
Ollama API endpoint |
OLLAMA_SYNTHESIS_MODEL |
qwen3:8b |
Model for LLM synthesis |
Architecture
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Agent │ │ Agent │ │ Agent │
│ (Claude, │ │ (Codex, │ │ (any MCP) │
│ Codex, ...) │ │ ...) │ │ │
└──────┬───────┘ └──────┬───────┘ └──────┬───────┘
│ │ │
└────────────────────┼────────────────────┘
│ MCP stdio
┌───────▼────────┐
│ Memory Bridge │
│ MCP Server │
└───┬────┬────┬──┘
│ │ │
┌─────────┘ │ └──────────┐
▼ ▼ ▼
┌──────────┐ ┌──────────┐ ┌──────────────┐
│ Mind │ │ Honcho │ │ Episodic │
│ Graph │ │ Vector │ │ Timeline │
│ (local) │ │ (HTTP) │ │ (JSONL) │
└──────────┘ └──────────┘ └──────────────┘
Zero dependencies
The core server uses only the Python standard library. No pip dependencies required. The vendored mind.py module is also zero-dependency.
License
MIT
Metadata
Release files for memory-bridge-mcp 1.2.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 |
|---|---|---|---|---|
| memory_bridge_mcp-1.2.0.tar.gz | 40.4 kB | Without provenance | Details for memory_bridge_mcp-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| memory_bridge_mcp-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for memory_bridge_mcp-1.2.0-py3-none-any.whl |
Total release size: 77.7 kB
Release files / memory_bridge_mcp-1.2.0.tar.gz
| Download URL | memory_bridge_mcp-1.2.0.tar.gz |
|---|---|
| Size | 40.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37a0958292fdae8865b9784289164086eecb020760038cbe57a76558ef3bafe6
|
|
BLAKE2b-256 checksum How to use checksums |
756ddfd38b3f59d1fd531e5a382fa2fc122cefd1b30f663e8032d4243de793b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.9
|
Release files / memory_bridge_mcp-1.2.0-py3-none-any.whl
| Download URL | memory_bridge_mcp-1.2.0-py3-none-any.whl |
|---|---|
| Size | 37.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c29a7ef4298861355cd1e9d602dee737189a31b1d7d39523afcaa14069a68550
|
|
BLAKE2b-256 checksum How to use checksums |
d55da37c58f9c06a65995b66d336a0e9db0f88a3501ec2f9f2e488366dc8e938
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.9
|
Security for memory-bridge-mcp 1.2.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.