Apple Notes MCP 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 |
|---|---|
| list_notesA | List notes, newest first, one line each: "title | folder | modified date | pinned". Returns 50 by default. To find notes by content, use search_notes instead. |
| search_notesA | Full-text search across note titles and bodies. All space-separated words must match (case-insensitive). Each result is "title | folder | modified date" followed by an excerpt around the match, so you often don't need get_note. Returns 20 by default; title matches come first. |
| get_noteA | Get the full content of a note by its title, returned as Markdown. Optionally specify folder to disambiguate. |
| create_noteA | Create a new note in Apple Notes from Markdown content. The first line becomes the title. Optionally specify a target folder (defaults to 'Notes'). |
| update_noteA | Update an existing note in Apple Notes. Deletes the old note and creates a new one with the given Markdown content, preserving the original folder. |
| delete_noteA | Delete a note from Apple Notes by title. Optionally specify folder to disambiguate. The note is moved to Recently Deleted. |
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 6 tools
Each tool targets a distinct action (create/get/list/search/delete/update) on a single resource, the note. The descriptions explicitly clarify the potentially confusable pair list_notes vs search_notes (list by recency, search by content), leaving no misselection risk.
Every tool follows the same verb_noun snake_case pattern (create_note, get_note, list_notes, search_notes, delete_note, update_note). The convention is fully predictable throughout.
Six tools is well-scoped for a note-taking domain, covering the full CRUD lifecycle plus list and search without redundancy. Every tool earns its place.
The surface covers the complete note lifecycle: create, get, list, search, update, and delete, with sensible optional folder handling. No obvious dead ends for core note workflows remain.