Shared local knowledge vault MCP server for Claude Desktop (Chat + Code)
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.
claude-desktop-bridge.mcpb from Releases.~/.claude-bridge/vault.db.| Tool | Description |
|---|---|
save_note | Save a new note (title, content, optional tags, optional project) |
get_notes | Retrieve notes by id, tags, or project, most recent first |
search_notes | Full-text search over note titles and content |
update_note | Update an existing note's title, content, tags, or project |
delete_note | Permanently delete a note by id |
Notes carry an optional project field, so work across multiple codebases stays separated — each project's notes filter independently.
Talk normally in either tab — Claude calls the tools on its own when useful. You never invoke anything manually.
my-repo codebase; use Claude-Desktop-Bridge with project: 'my-repo'."| Surface | Works out of the box? |
|---|---|
| Claude Desktop — Chat tab | ✅ Yes |
| Claude Desktop — Code tab (local sessions) | ✅ Yes |
Standalone claude CLI (terminal, Desktop not required) | ⚠️ Needs one extra step |
| Claude Code on the Web / cloud sessions | ❌ Not available (local-only server) |
The standalone CLI doesn't read Desktop's extension config. Register it explicitly:
# macOS or WSL — imports every MCP server Desktop has configured
claude mcp add-from-claude-desktop
# Any platform, including Linux — register this repo's built server:
claude mcp add --scope user claude-desktop-bridge -- node /path/to/claude-desktop-bridge/server/index.js
--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.
npm install
npm run build # bundles src/index.ts -> server/index.js
npm run pack # produces claude-desktop-bridge.mcpb
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).
~/.claude-bridge/vault.db (local SQLite). Uninstalling the extension keeps the file; notes persist until deleted via delete_note or by removing the file.Open an issue to discuss before a PR. Edit src/index.ts — server/index.js is generated. PRs must pass npm ci + npm test.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y claude-desktop-bridgeMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-kimiguel-claude-desktop-bridge": {
"command": "npx",
"args": [
"-y",
"claude-desktop-bridge"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceclaude-desktop-bridgenpmio.github.KiMiGuel/claude-desktop-bridge works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.