Bear Notes 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 |
|---|---|
| search_bear_notesB | Search Bear App notes Args: query: Text to search for (searches in title and content) tag: Tag to filter by (without # symbol) limit: Maximum number of results Returns: List of matching notes with metadata |
| get_bear_noteB | Get a specific Bear note by ID Args: note_id: Bear note's unique identifier Returns: Complete note content with metadata |
| list_bear_tagsB | List all tags from Bear App notes Returns: Sorted list of all tags found in notes |
| find_kubernetes_examplesC | Find Kubernetes manifest examples in Bear notes Args: resource_type: Kubernetes resource type to search for (deployment, service, configmap, etc.) Returns: Notes containing Kubernetes examples |
| find_code_examplesC | Find code examples in Bear notes Args: language: Programming language (python, javascript, go, etc.) topic: Topic to search for (docker, api, database, etc.) limit: Maximum number of results Returns: Notes containing code examples with extracted code blocks |
| find_notes_by_titleC | Find notes by title Args: title_query: Title text to search for exact_match: Whether to match title exactly or use partial matching Returns: Notes matching the title criteria |
| get_recent_notesC | Get recently modified notes Args: days: Number of days to look back limit: Maximum number of results Returns: Recently modified 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 7 tools
Most tools have distinct purposes, but there is some overlap between find_notes_by_title and search_bear_notes, as both search for notes based on text criteria. However, the descriptions clarify that find_notes_by_title focuses on title matching while search_bear_notes searches both title and content, reducing confusion.
All tool names follow a consistent verb_noun pattern with snake_case, such as find_code_examples, get_bear_note, and list_bear_tags. This uniformity makes the tool set predictable and easy to understand.
With 7 tools, the server is well-scoped for managing Bear notes, covering key operations like searching, retrieving, and listing without being overwhelming. Each tool serves a clear purpose, making the count appropriate for the domain.
The tool set provides strong coverage for reading and searching notes, including specific use cases like code and Kubernetes examples. However, it lacks write operations (e.g., create, update, or delete notes), which could limit full lifecycle management, though this may be intentional for the server's design.