Claude Memory Bridge
Share context and memories between Claude Code and Claude Desktop
Ask AI about Claude Memory Bridge
Powered by Claude Β· Grounded in docs
I know everything about Claude Memory Bridge. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
claude-memory-bridge
MCP server that bridges Claude Code's file-based memory system to Claude Desktop, enabling two-way context sharing between clients.
What it does
Claude Code stores memories as markdown files with YAML frontmatter in ~/.claude/projects/. This server exposes those memories β plus an inbox system and project status dashboard β as MCP tools that Claude Desktop can call.
Memory reading
Discover projects, list memories by type, and search with weighted relevance scoring across all projects or filtered to one.
Inbox
A cross-client messaging system. Claude Desktop creates inbox items (TODOs and notes) that Claude Code surfaces on session start via a shell hook. Items have status tracking (pending β in_progress β completed | dismissed), priority levels, and tags.
Memory writing
Claude Desktop can write memories in Claude Code's native format β markdown with YAML frontmatter β and automatically update the project's MEMORY.md index.
Project status
Aggregates a live snapshot of any project: memory counts by type, pending inbox items, current git branch, active branches, and recent commits.
Setup
Prerequisites
- Node.js >= 20
- Claude Code (memories in
~/.claude/projects/)
Install
npm install
npm run build
Configure Claude Desktop
Add to your Claude Desktop MCP config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"claude-memory-bridge": {
"command": "node",
"args": ["/absolute/path/to/claude-memory-bridge/dist/index.js"]
}
}
}
Inbox session hook (optional)
To have Claude Code surface pending inbox items on session start, add a hook to your Claude Code settings (~/.claude/settings.json):
{
"hooks": {
"SessionStart": [
{
"type": "command",
"command": "/absolute/path/to/claude-memory-bridge/scripts/check-inbox.sh"
}
]
}
}
Tools
| Tool | Description |
|---|---|
list_projects | Discover all projects with memories |
read_memories | List memories, optionally filtered by project and type |
search_memories | Weighted relevance search across memories |
create_inbox_item | Create a TODO or note in a project's inbox |
list_inbox_items | List inbox items with optional filters |
search_inbox | Search inbox items with relevance scoring |
update_inbox_item | Update status, priority, title, body, or tags |
delete_inbox_item | Permanently remove an inbox item |
create_memory | Write a memory file in Claude Code's native format |
get_project_status | Live summary: memories, inbox, git activity |
Resources
| Resource | Description |
|---|---|
project-status://{project} | Live project status as a readable resource |
How it works
Claude Code encodes project paths as directory slugs under ~/.claude/projects/ β for example, /Users/kelly/code/my-project becomes -Users-kelly-code-my-project. The server resolves these slugs back to real filesystem paths by walking the directory tree, handling ambiguities where both / and . encode to -.
Memories live in ~/.claude/projects/<slug>/memory/*.md. Inbox items live in ~/.claude/projects/<slug>/inbox/*.md. Both use YAML frontmatter for structured metadata.
License
MIT
