notes-mcp
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 |
|---|---|
| list_notesA | List all notes with their folder and timestamps. Fast; does not read note content. Recently Deleted is excluded by default. |
| list_foldersA | List all Notes folders with note counts. Recently Deleted is excluded by default. |
| search_notesA | Full-text search across note titles and body text. Returns metadata, not content. |
| read_noteA | Read a note's full content. Checklist items appear as ◦ (unchecked), ✓ (checked), and ⁃ marks an ordinary bullet. Each checklist item also reports its nesting depth. This is the only way to observe checked state. |
| read_checklistA | Read just the checklist items of a note, with checked state, indices, and nesting depth (0 = top level). |
| create_noteA | Create a note. Markdown is converted by Notes itself, so '- [ ] item' becomes a real checklist item and '- [x] item' a checked one. |
| append_to_noteA | Append Markdown to the end of a note, leaving existing content untouched. '- [ ] item' becomes a real checklist item. |
| replace_note_contentA | Replace a note's entire body with new Markdown, keeping its id, folder and creation date. Refuses if the note has attachments or tables unless force is set. |
| clear_checklistA | Uncheck every checklist item in a note, leaving the items themselves in place. Use this to reset a recurring checklist, e.g. after a workout. |
| check_all_itemsC | Check every checklist item in a note. |
| set_checklist_itemsA | Check, uncheck, or toggle specific checklist items, selected either by index (from read_checklist) or by matching their text. |
| create_folderC | Create a new folder. |
| move_noteC | Move a note to a different folder. |
| delete_noteA | Delete a note. It goes to Recently Deleted and can be restored. Requires confirm: true so it cannot fire accidentally. |
| check_setupA | Verify Notes automation access and that the bridge shortcuts are installed. |
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 15 tools
Most tools have distinct purposes, but read_note and read_checklist both expose checklist state, and the trio of clear_checklist, check_all_items, and set_checklist_items operate on checklists in overlapping ways. Descriptions clarify the differences, so ambiguity is low but not zero.
All tool names use lowercase snake_case with a clear verb_noun pattern (e.g., read_note, create_folder, list_notes). The pattern is consistent across the entire set, with only minor variations like append_to_note, which still follows the same structural style.
With 15 tools, the server sits at the upper boundary of the ideal range but remains well-scoped. Every tool covers a distinct operation relevant to notes and folder management, and none feel redundant or unnecessary.
The note lifecycle is well covered with create, read, append, replace, and delete, and checklist operations are comprehensive. However, folder management is incomplete—there is no way to rename or delete folders—and there is no direct way to restore notes from Recently Deleted, which is a minor gap.