mcp-notes-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTES_FILE | No | Path to the JSON file where notes are stored. Defaults to ~/.mcp-notes/notes.json. | ~/.mcp-notes/notes.json |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_noteB | Save a new note. Returns the note id. Use tags to group related notes. |
| list_notesA | List notes, newest first. Optionally filter by a single tag. |
| search_notesA | Keyword search across note titles, tags and bodies. Returns the best matches with full content. |
| delete_noteA | Permanently delete one note by id. This cannot be undone. |
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 4 tools
Each tool maps to a clearly distinct operation: create, enumerate, keyword-search, and delete. There is no overlap between search_notes and list_notes since one is keyword-based and the other is enumerative with tag filtering, and descriptions make the boundaries explicit.
All tools follow a verb_noun snake_case pattern (add_note, list_notes, search_notes, delete_note), which is highly predictable. The only minor deviation is singular 'note' in add/delete versus plural 'notes' in list/search, but this reflects natural object plurality rather than a convention break.
Four tools is a tight, well-scoped surface for a simple notes server, with each tool earning its place. It sits at the low end of the typical 3-15 range, and the absence of any modification tool makes it feel slightly under-provisioned rather than bloated.
The surface covers create, read/list, search, and delete, but there is no update/edit tool, so an agent cannot modify an existing note's title, body, or tags without deleting and recreating it. Retrieval by id is also only implicitly available via search, leaving a notable lifecycle gap.