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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesC | List all notes or notes from a specific account/folder. |
| search_notesB | Search for notes containing the specified text. |
| read_noteC | Read the content of a specific note by name. |
| create_noteB | Create a new note with the specified title and content. |
| update_noteC | Update the content of an existing note. |
| delete_noteC | Delete a note by name. |
| list_accountsB | List all available Notes accounts. |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: create_note, delete_note, list_accounts, list_notes, read_note, search_notes, and update_note all target specific, non-conflicting operations. An agent can easily distinguish between them based on their names and descriptions.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_note, delete_note, list_accounts, list_notes, read_note, search_notes, and update_note. This uniformity makes the set predictable and easy to navigate for an agent.
With 7 tools, the server is well-scoped for managing Apple Notes, covering essential operations like CRUD, listing, and searching. Each tool serves a clear purpose without redundancy, fitting within the typical 3-15 tool range for such a domain.
The tool set provides complete CRUD/lifecycle coverage for notes (create, read, update, delete), along with listing accounts and notes, and searching. There are no obvious gaps, enabling agents to perform all core workflows without dead ends.