Claude-Desktop-Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_noteA | Save a new note to the shared knowledge vault. Use for research findings, decisions, or context worth persisting across chat and code sessions. Pass |
| get_notesA | Retrieve notes from the vault by id, by tag, by project, or the most recently updated ones. Use this for browsing/listing, not free-text search (use search_notes for that). |
| search_notesA | Full-text search over note titles and content. Use this to find relevant past notes by keyword before starting new research. |
| update_noteA | Update an existing note's title, content, tags, and/or project. |
| delete_noteA | Permanently delete a note from the vault by id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: save creates, get_notes lists/retrieves by metadata, search_notes handles full-text lookup, update edits, and delete removes. The boundary between get_notes and search_notes is explicitly clarified in the descriptions.
All tools follow a clear verb_note/notes pattern with lowercase snake_case. The only minor inconsistency is singular 'note' for create/update/delete versus plural 'notes' for read/search, but the convention remains predictable.
Five tools is a well-scoped set for a note vault, covering all essential operations without redundancy or bloat. Each tool serves a necessary function.
The tool surface provides full CRUD coverage for notes, plus search for discovery. There are no obvious missing operations for the stated domain of persisting and retrieving shared notes.