Bear MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_bear_tokenB | Set the Bear app token for accessing existing notes. Get your token from Bear → Help → Advanced → API Token |
| check_bear_setupB | Check if Bear is properly configured and test the connection |
| create_noteC | Create a new note in Bear and return its ID |
| get_noteC | Get the content of a specific note |
| search_notesC | Search for notes and return results with metadata (requires token) |
| get_tagsB | Get all tags from Bear (requires token) |
| add_textB | Append or prepend text to an existing note |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: add_text modifies note content, check_bear_setup handles configuration, create_note and get_note manage note lifecycle, get_tags retrieves metadata, search_notes finds notes, and set_bear_token handles authentication. The descriptions make it easy to distinguish between them.
All tools follow a consistent verb_noun pattern using snake_case: add_text, check_bear_setup, create_note, get_note, get_tags, search_notes, set_bear_token. The naming is predictable and readable throughout the set.
With 7 tools, this is well-scoped for a Bear note-taking server. It covers core operations (create, read, update via add_text, search) and necessary setup/authentication without being overwhelming or too sparse.
The toolset provides strong coverage for note management: create, read, update (via add_text), search, and tag retrieval. Minor gaps include no explicit delete_note or update_note (beyond add_text), but agents can work around this, and the surface supports core workflows effectively.