bearnotes-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search non-trashed notes by title/body, optionally filtered to a tag (matches the tag and its nested subtags). Empty query = most recent. Returns id, title, tags, pinned, modified. |
| read_noteA | Return a note's {id, title, text, tags, pinned, todo_open, todo_done}. |
| list_tagsA | List every tag with the number of non-trashed notes it holds. |
| get_backlinksA | Bear's [[wiki-link]] graph for a note: |
| create_noteB | Create a new note (its title becomes the H1 line). No token required. |
| append_noteA | Append text to the end of an existing note. |
| prepend_noteB | Prepend text to a note (Bear inserts it just after the title line). |
| replace_noteA | Overwrite a note's ENTIRE text, including its title line — pass the full text as returned by read_note (not body-only), or the title changes. Backs up the current text first to ~/.bear-mcp-backups/. Note the backup is a read-only DB snapshot and may lag edits still open unsaved in Bear's UI. |
| toggle_taskA | Check/uncheck one checkbox line in a note, found by substring |
| open_noteB | Open and focus a note in the Bear app window. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| notes_index | Index of recent non-trashed notes as `- title (id)` lines. |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: reading, searching, listing tags, backlinks, creating, appending, prepending, replacing, toggling tasks, and opening. No two tools have overlapping purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., read_note, search_notes, create_note), making them predictable and easy for an agent to infer.
With 10 tools covering core note operations, tagging, backlinks, and task management, the count is well-scoped for a Bear notes server—neither sparse nor overwhelming.
Covers essential CRUD-like operations (read, create, update via replace, append, prepend), search, tags, backlinks, and task toggling. Minor missing features like explicit delete/trash or tag management are gaps but workable.