notes-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTES_DB | No | The path to the SQLite database file where notes are stored. | ~/.notes-mcp/notes.db |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_noteC | Create a note. Tags are optional lowercase labels used for filtering. |
| search_notesA | Full-text search over titles, bodies and tags, best match first. Matching words are wrapped in [brackets] in the snippet. Optionally filter by one tag. |
| get_noteB | Return the full text of one note. |
| update_noteA | Change a note. Only the fields you pass are updated; passing tags replaces all tags. |
| delete_noteA | Permanently delete a note. Confirm with the user first. |
| list_tagsA | All tags in use, with how many notes carry each one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| recent_notes | The ten most recently changed notes, as a markdown list. |
TDQS
Scored across 6 tools
Each tool maps to a distinct resource-action pair: create, full-text search, retrieve, update, delete, and tag enumeration. The only near-neighbors (search_notes vs list_tags) are clearly separated by purpose (content matching vs tag inventory). No two tools appear interchangeable.
All names follow a strict snake_case verb_noun pattern (add_note, search_notes, get_note, update_note, delete_note, list_tags). The convention is predictable and the verbs accurately signal semantics (add vs get vs update vs delete).
Six tools is well-scoped for a notes server: full CRUD plus search and tag listing, with no filler or redundant variants. Every tool earns its place in a core workflow.
CRUD, full-text search with tag filtering, and tag inventory cover the essential note lifecycle with no dead ends for typical workflows. Minor gap: there is no plain list_notes for enumerating notes without a search term, and no tag rename/delete operation, though both are largely workable via search and update_note.