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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_noteA | 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. |
| get_noteA | Fetch one note by id, with full content. |
| update_noteA | Edit an existing note. Provide the id and at least one of title, content or tags. Tags, if given, replace the existing tags. |
| export_notesA | Return all notes (or only those with one tag) as one Markdown document, newest first. Read-only: nothing is written to disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| review_notes | Ask the model to summarise and organise your notes, optionally only those with one tag. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all-notes | Every note, newest first, as one text document. |
TDQS
Scored across 7 tools
Each tool targets a distinct action on notes: create, read one, list, keyword search, update, delete, and export. The retrieval tools (list, search, export) have clearly differentiated behaviors described explicitly, so an agent can pick correctly.
All seven tools follow a strict verb_noun snake_case pattern (add_note, get_note, list_notes, update_note, delete_note, search_notes, export_notes). No mixing of conventions.
Seven tools is a well-scoped set covering the full note lifecycle plus search and export. Every tool earns its place with no redundant entries.
Complete CRUD coverage (add/get/list/update/delete) plus search and export, leaving no obvious dead ends. Minor extras like tag listing or bulk delete are not essential to the domain.