MemoryBridge MCP
Shared AI-agent memory lives in SQLite, syncs across devices through a cloud drive and reaches Claude Code and Cursor over MCP.
- 514 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Stores agent memories and moves them through a cloud drive, with the channel key derived from an open seed by default
- The hook is added to AI client configuration and injects memory into every session
Install
- Works in
Manual install
git clone https://github.com/jiabaobei/memory-bridge.gitThen `cd memory-bridge`, `pip install -e .` and `membridge init`. Do not run `pip install membridge`: it is a different package.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Stores agent memories and moves them through a cloud drive, with the channel key derived from an open seed by default
- The hook is added to AI client configuration and injects memory into every session
This is third-party code. Review the repository files before installing.
What it does
MemoryBridge (`membridge`) keeps agent memory in a local SQLite database and moves it between phone, PC and tablet as incremental packets that are encrypted by default. The same memory is available over MCP in Claude Code, Cursor, Cline, Windsurf, Gemini CLI and other clients. The MCP server exposes three tools: `memory_add` for writing a `fact`, `procedure` or `handover` entry, `memory_search` for hybrid search with scopes such as `tag:dev` and time windows like `at:7d`, and `memory_preload`. There is no tool for changing recorded memories: under the content-freeze principle stored text is never rewritten. `membridge hook --install` adds automatic injection of matching memories at session start.
Who it is for. Developers who work on one project across several devices and AI clients and are tired of re-explaining context to the agent whenever the machine changes.
Good fit when
- A design was discussed on a phone in the morning and has to continue in Claude Code on a laptop in the evening.
- Claude Code, Cursor and Cline should rely on the same project decisions and agreements.
- At the end of the day a handover card is wanted: what is done, what failed, what comes next.
- Matching memories should reach the session on their own, without manual lookup.
Not a fit when
- A cloud drive is forbidden by policy: sync and the first setup go through it.
- A permanent archive with fixed ranking is needed: memory is ranked by heat, and a handover card becomes ordinary after a week.
- Strict protection from outsiders is required: the channel key is derived by default from a publicly described seed.
Example request
Find memory entries about the database schema from the last seven days and write a handover card with what remains.MCP
- Transport
- stdio, http
- Authentication
- not required
Environment variables
`MEMBRIDGE_DB`- Path to the memory database file, for example `D:/mem/my.db`.
`MEMBRIDGE_DEVICE`- Device name in the sync channel, for example "My PC".
Limitations
Install from source only: `pip install membridge` installs a different package with the same name, and the project was never published to PyPI. The `membridge init` setup requires a cloud drive by default, and without it cross-device sync is impossible. The channel key is derived by default from a seed in open source, so use your own `--passphrase` for strong protection. The hook adds an entry to the host configuration and makes a backup before editing. `pyproject.toml` marks the project as Alpha.
How to disable. Remove the hook with `membridge hook --uninstall`, delete the MCP entry from the client (`claude mcp remove memory-bridge` for Claude Code) and turn off scheduled sync. The SQLite database and the cloud-drive channel are deleted separately.
FAQ
Why not install with pip install membridge?
That PyPI name belongs to another project. MemoryBridge was never published to PyPI and has to be installed from a clone with `pip install -e .`.
What does `membridge init` do?
It sets up the cloud channel, detects installed AI clients and wires MCP, schedules sync every 15 minutes and installs a skill for supported platforms. Rerunning it is safe.
How do I connect manually?
For Claude Code: `claude mcp add memory-bridge -- membridge mcp`. For Cursor add a server to `mcp.json` with `command` `membridge` and `args` `["mcp"]`.
What is a handover card?
A `handover` memory with `goal:`, `done:`, `failed:`, `next:` and `refs:` lines. A fresh card is always injected into context and becomes ordinary after 7 days without updates.
Will a model rewrite my memories?
No. The content-freeze principle forbids changing stored text, and MCP has no editing tools.
Discussion
No questions or reviews yet.
Related
MCP serversLocal memory for an agent: hooks record facts from conversations and the MCP server brings them back in later sessions from one SQLite file
LongMemory keeps project memory in local SQLite and serves it to an agent over MCP: decisions, task state, skills and a code graph
Membase keeps one shared memory for AI agents that Claude Code, Cursor and Codex read through MCP, an SDK or the membase command
A local-first MCP memory server for agents: session history, codebase index and a concept graph in one SQLite database
Long-term memory for agents: a remote MCP server, plugins for Claude Code, Cursor and Codex, and an API for your own apps
Long-term memory for Claude Code, Cursor and Codex: the agent saves decisions and finds them again in later sessions
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| MemoryBridge (this card) | no | not required | 514 | |
| Episodic Memory | no | 499 | episodic-memory searches decisions in past conversations; MemoryBridge keeps recorded memories and syncs them across devices | |
| Mem0 | no | 68,887 | mem0 is a memory layer with plugins, a CLI and an SDK; MemoryBridge stays a local SQLite database moved through a cloud drive |
README in short
The README covers sync, encryption, handover cards and automatic injection in detail. Connecting clients takes either `membridge init` or a single `claude mcp add` command.