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 |
|---|---|
| create_noteB | Create a new Markdown note Args: title: Note title content: Note content tags: Optional comma-separated list of tags Returns: Confirmation message of note creation |
| list_notesC | Get a list of all notes Args: tag: Optional tag filter Returns: List of notes with titles and dates |
| read_noteC | Read the contents of a note Args: filename: Note filename (with .md extension) Returns: Note content |
| search_notesC | Search for text within notes Args: query: Search query Returns: List of notes containing the query |
| update_noteC | Update the content of an existing note Args: filename: Note filename content: New content (will be appended) Returns: Confirmation message of update |
| delete_noteC | Delete a note Args: filename: Note filename Returns: Confirmation message of deletion |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_notes_prompt | Create a summarization prompt for all notes Returns: A prompt containing all notes for analysis |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_all_notes | Retrieve all notes as a single resource Returns: Combined contents of all notes |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: create, delete, list, read, search, and update notes. The descriptions reinforce these distinctions, making it easy for an agent to select the correct tool for any note-related operation without confusion.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_note, delete_note, list_notes). This uniformity enhances readability and predictability, allowing agents to easily infer functionality from the naming convention.
With 6 tools, the server is well-scoped for managing notes, covering essential CRUD operations and additional utilities like search. Each tool earns its place without being excessive or insufficient for the domain, aligning with typical small to medium-sized tool sets.
The tool set provides complete CRUD coverage (create, read, update, delete) along with listing and search capabilities, ensuring no dead ends for note management. There are no obvious gaps, as all core lifecycle operations for a notes domain are adequately covered.