
Claude Desktop Bridge
io.github.KiMiGuelPublished by GitHub account KiMiGuelv1.0.0Updated Oct 24, 2026
Shared local knowledge vault MCP server for Claude Desktop (Chat + Code)
The publisher's own server: Claude Platform Docs
Overview
A local MCP server that gives Claude Desktop's Chat and Code tabs a shared, persistent SQLite note vault the assistant can save, search and update.
- What you can do
- Save new notes with title, content, optional tags and an optional project label, and update an existing note's fields later. Retrieve notes by id, tag or project, most recent first. Run full-text search over note titles and content. Permanently delete a note by id. Keep notes separated per project so work across codebases stays apart.
- When to use it
- Useful when you switch between Claude Desktop's Chat and Code tabs and want context, decisions or snippets to carry over instead of being re-derived. Also handy for keeping per-project notes across several codebases.
- Requirements
- Runs as a local process on the user's machine, installed as a Claude Desktop extension; Desktop supplies its own Node runtime, so end users need no Node install. Building from source needs Node.js 22+. The vault is a local SQLite file, by default under the home directory, and its location can be set with the VAULT_DIR environment variable. No network access and no authentication.
Installation
In SourceWeft
- Open Claude Desktop Bridge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Claude-Desktop-Bridge
Local MCP server that gives Claude Desktop's Chat and Code tabs a shared, persistent note vault. Claude pulls only what it needs via five tools — save_note, get_notes, search_notes, update_note, delete_note — instead of re-deriving context after every tab switch.
Install
- Download
claude-desktop-bridge.mcpbfrom Releases. - Drag it onto the Claude Desktop window — or Settings → Extensions → Advanced settings → Install Extension…
- No configuration. The vault lives at
~/.claude-bridge/vault.db.
Tools
Notes carry an optional project field, so work across multiple codebases stays separated — each project's notes filter independently.
Use it
Talk normally in either tab — Claude calls the tools on its own when useful. You never invoke anything manually.
- Proactive, not automatic-automatic. Claude decides what's worth saving or searching — it's not logging every message. Say "remember this for later" when you want something kept.
- Tag by project when working across codebases, so a search in one repo's context doesn't surface another's notes.
- Chat tab "Projects" don't auto-link to a Code tab folder. Put it in that Project's Custom Instructions: "This project corresponds to the
my-repocodebase; use Claude-Desktop-Bridge withproject: 'my-repo'."
Where this works
The standalone CLI doesn't read Desktop's extension config. Register it explicitly:
--scope user makes it available in every terminal project. It reads the same ~/.claude-bridge/vault.db as the Desktop extension, so notes are shared.
Want notes to cost fewer tokens? cdb-companion compresses content before it hits
save_note/update_note.
Building from source
Requires Node.js 22+ (built-in node:sqlite). Claude Desktop's own Node runtime runs the extension — end users need no Node install. Gates: npm ci + npm test (see .github/workflows/npm-project.yml).
Configuration
- Vault →
~/.claude-bridge/vault.db(local SQLite). Uninstalling the extension keeps the file; notes persist until deleted viadelete_noteor by removing the file. - Network → none. No server component, no outbound requests, no analytics or telemetry.
Contribute
Open an issue to discuss before a PR. Edit src/index.ts — server/index.js is generated. PRs must pass npm ci + npm test.
License
MIT
Source: README.md at commit 419827a
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Claude integrations
Claude Platform Docs
com.claude.platformOfficial publisher
Remote MCP server that lets an assistant search and read the Claude Platform documentation and API reference.

Insta Edits for Claude
Published by GitHub account faisalkhanzemi
Bridge that lets Claude drive the full 274-tool editor in Instagram Edits for Mac, keeping the tool list in sync as projects open.

Claude Checkpoint Mcp
Published by GitHub account daniel-munoz
Local MCP server that saves Claude Code session state to a checkpoint file in the project and reloads it as a compact resume brief.

Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen
Published by GitHub account spk-c
Qwen DAP MCP — C/C++ Debugger for Claude Code, Codex & Qwen's local MCP server; no sign-in required; STDIO; 18 tools.

AVE for Claude Code — Local Video Editing
Published by GitHub account lemberalla
Local AVE timeline editing and exports for Claude Code only. Existing AVE connection required.