MCP Bear
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_ROUTE | No | Override the default Bear database path by setting this environment variable. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_notesB | Get all notes from Bear |
| get_tagsB | Get all note tags. You can search notes by tags with get_notes_like |
| get_notes_likeB | Get notes that include a specific text string |
| create_noteB | Create a new note in Bear |
| add_textC | Add text to an existing note |
| add_tagsC | Add tags to an existing note |
| trash_noteC | Move a note to trash |
| open_noteC | Open a specific note in Bear |
| search_bearC | Open Bear and show search results for a term |
| get_note_by_idC | Get a specific note by its unique identifier |
| get_notes_by_tagB | Get all notes with a specific tag |
| get_archived_notesC | Get all archived notes |
| archive_noteC | Archive a note |
| unarchive_noteC | Unarchive a note |
| open_tagB | Open Bear and show all notes with a specific tag |
| rename_tagB | Rename a tag across all notes |
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 16 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, 'add_tags' and 'add_text' are clearly different operations on notes, while 'get_notes_by_tag' and 'get_notes_like' target different filtering criteria. The descriptions make each tool's specific function immediately apparent.
All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., 'create_note', 'get_notes_by_tag', 'archive_note'). The naming is predictable and readable, with verbs like 'add', 'get', 'open', 'rename', 'search', and 'trash' used appropriately across the set.
With 16 tools, this is well-scoped for a note management server like Bear. Each tool earns its place by covering distinct operations such as CRUD for notes, tag management, archiving, and search, without feeling bloated or insufficient for the domain.
The tool set provides complete coverage for note management in Bear. It includes full CRUD operations (create, read, update via add_tags/add_text, delete via trash_note), lifecycle management (archive/unarchive), tag operations (get, rename), and comprehensive search capabilities (by ID, tag, text, or general search). No obvious gaps exist for typical agent workflows.