MCP Notes Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_noteA | Add a new note or todo item to the store. Use this whenever the user wants to remember something, jot down a task, or create a todo. |
| list_notesA | List all saved notes/todos. Optionally filter to only show items that are still open (not done) or only completed ones. |
| search_notesA | Search notes by a keyword. Returns any note whose text contains the query (case-insensitive). |
| complete_noteA | Mark a note/todo as done, by its id. |
| delete_noteA | Permanently delete a note/todo by its id. |
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 5 tools
Each tool has a clear, distinct purpose (add, list, search, complete, delete) with no overlapping functionality. An agent can easily distinguish them.
All tools follow a consistent verb_noun pattern (e.g., add_note, delete_note) with no deviations, making the naming predictable.
5 tools is well-suited for a notes server, covering essential operations without being overly sparse or bloated.
The set covers basic CRUD operations but lacks an update tool for editing note content, which is a notable gap. Users must delete and re-add to modify text.