memory-bridge
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@memory-bridgePromote 'Use pnpm, not npm' to the frontend namespace"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
memory-bridge
Cross-project memory sharing for Claude Code and Cowork. Stop teaching Claude the same thing twice.
Claude's memory is project-isolated. Teach it "use pnpm" in project A, repeat yourself in project B. memory-bridge adds a shared layer — namespaces — between global and project scope. Solves #36561 and #39195.
Global ~/.claude/CLAUDE.md (Claude native)
Namespace ~/.claude/shared-memory/<ns>/*.md (memory-bridge)
Project ~/.claude/projects/<proj>/memory/*.md (Claude native)Install
Claude Code (one command)
claude mcp add memory-bridge -- uvx claude-memory-bridgeDone. No clone, no config files. Requires uv (curl -LsSf https://astral.sh/uv/install.sh | sh).
Cowork Desktop
Add to your config file (Settings > Developer > Edit Config):
{
"mcpServers": {
"memory-bridge": {
"command": "uvx",
"args": ["claude-memory-bridge"]
}
}
}Requires uv. Then restart Cowork.
Manual install (advanced)
git clone https://github.com/LewenW/claude-memory-bridge.git
cd claude-memory-bridge
pip install -e .
python scripts/install.pyRelated MCP server: Central Brain
Tools
Tool | What it does |
| Search across all projects and shared namespaces |
| Move a memory from project to shared namespace |
| Copy a memory to specific projects |
| Browse namespace contents |
| Create, delete, subscribe, unsubscribe |
| Find duplicates, stale entries, broken indexes |
Quick start
In a Claude Code or Cowork session:
# Create a namespace
"Create a shared namespace called 'frontend' for React conventions"
# Share knowledge
"Promote 'Use pnpm, not npm' to the frontend namespace"
# Subscribe a project
"Subscribe my dashboard project to the frontend namespace"
# Search across everything
"Search memories for pnpm"Client compatibility
Client | Auto | Manual |
Claude Code (CLI) | Yes | Yes |
Cowork — Code mode | Yes | Yes |
Cowork — Cowork mode | :( | Yes — mention "memory-bridge" or tool name |
Cowork mode loads the MCP tools but doesn't inject server instructions, so Claude won't use them unprompted. Workaround: say "use search_memories" or mention "memory-bridge". This will work automatically once Cowork supports MCP instructions.
How it works
Reads/writes Claude's native
~/.claude/projects/*/memory/*.mddirectly — no databaseShared memories in
~/.claude/shared-memory/<namespace>/registry.jsontracks namespace subscriptionsWord-boundary TF-IDF search scoring
Trigram Jaccard similarity for duplicate detection (threshold 0.45)
Uninstall
claude mcp remove memory-bridge # Claude CodeOr remove the memory-bridge entry from your Cowork config file.
Project structure
src/memory_bridge/
├── server.py MCP server, 6 tools
├── config.py Paths + constants
├── models.py Dataclasses
├── store/
│ ├── base.py MemoryStore interface
│ └── filesystem.py File I/O + keyword search
└── engine/
├── retriever.py Cross-project search
├── promoter.py Project → namespace promotion
├── namespace_manager.py Namespace CRUD
└── health_analyzer.py Dedup + staleness + index auditLicense
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityDmaintenanceGives Claude Code long-term memory that persists across sessions via hybrid BM25 and vector semantic search, with multi-project isolation.Last updated288MIT
- Alicense-qualityDmaintenanceProvides persistent memory for Claude Code, automatically extracting and surfacing relevant context from past sessions to avoid re-explaining issues and decisions.Last updatedMIT
- Alicense-qualityCmaintenanceUnified memory and agent bridge for Claude Code, enabling cross-tab messaging, shared context, session checkpoints, and semantic memory across sessions.Last updated21MIT
- Alicense-qualityCmaintenanceCross-project memory for Claude Code, enabling local semantic recall and secure, git-versioned markdown storage of reusable knowledge across repositories.Last updatedMIT
Related MCP Connectors
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Persistent context for Claude. Your AI always knows your projects and next actions across sessions.
Cross-AI personal memory. Save once in ChatGPT, recall in Claude, Mistral, Grok, or any MCP client.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LewenW/claude-memory-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server