notes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTES_MCP_DIR | No | Directory where notes are stored. Defaults to ~/.notes-mcp/. |
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteA | Create a new note with a title, markdown body, and optional tags. |
| update_noteA | Update an existing note by id. Only the fields you pass are changed. |
| delete_noteA | Permanently delete a note by id. |
| get_noteA | Retrieve a single note by id, including its full body. |
| search_notesA | Search notes by free-text query (all terms must match) and/or a tag. Returns matching notes newest-first. |
| list_tagsA | List every tag currently in use across all notes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_tag | Collect all notes carrying a given tag and ask the model to summarize them. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct operation: create, update, delete, get, search, and list tags. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (create_note, update_note, delete_note, get_note, search_notes, list_tags). This makes the API predictable and easy to navigate.
Six tools is an appropriate scope for a notes management server, covering core CRUD, search, and tag listing without unnecessary bloat or sparse coverage.
The tool surface provides complete CRUD for notes (create, read, update, delete) plus search and tag listing. A minor gap is the lack of an explicit 'list all notes' tool, but search_notes likely can serve this purpose with empty query.