mcp-notes-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NOTES_DB | No | Path to the SQLite database file used for storing notes. Overrides the default location. | ~/.mcp-notes/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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_noteA | Save a new note with a title, an optional body and optional tags. |
| search_notesA | Full text search over titles and bodies, newest ranking first, optionally narrowed to one tag. Every word is a prefix match. |
| list_notesA | List notes by last change, optionally filtered by tag. |
| get_noteA | Read one note in full by its id. |
| update_noteA | Change title, body or tags of a note. Omitted fields stay as they are. |
| delete_noteB | Delete a note by id. |
| list_tagsA | All tags in use with the number of notes carrying each. |
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 maps to a distinct action and resource: CRUD operations on notes, search, and tag listing. There is no overlap or ambiguity between tools.
All tools follow a clear verb_noun pattern: add_note, search_notes, list_notes, get_note, update_note, delete_note, list_tags. Singular/plural variation is natural and does not harm predictability.
Seven tools is a well-scoped size for a notes server. Each tool serves a necessary purpose without redundancy or bloat.
The note lifecycle is fully covered with create, read, list, update, and delete, plus search and tag management. There are no obvious dead ends or missing core operations.