icloud-notes-connector
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_accountsA | Lists the Notes accounts configured on this Mac (e.g. iCloud, On My Mac). Use this first if you're not sure which account name to pass to other tools. |
| list_foldersB | Lists the folders within a given Notes account. |
| list_notesA | Lists note titles (and internal ids) in an account, optionally limited to one folder. Does not return note bodies, use read_note for that. |
| search_notesA | Case-insensitive search across note titles and bodies in an account. Returns matching titles with a short snippet. Note: this checks every note in the account, so it can be slow on very large note libraries. |
| read_noteA | Reads the full body of a note by exact title. If multiple notes share that title, the first match is returned, use list_notes to disambiguate by id if needed. |
| create_noteC | Creates a new note with a title and plain-text body in the given account. |
| move_noteA | Moves an existing note to a different folder by exact title. If multiple notes share that title, the first match is moved. |
| update_noteA | Updates the body of an existing note by exact title. Optionally replaces the title too. If multiple notes share that title, the first match is updated. |
| delete_noteA | Deletes an existing note by exact title. If multiple notes share that title, the first match is deleted. This action cannot be undone. |
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 9 tools
Each tool targets a distinct operation (create, move, update, search, read, delete, list accounts, list folders, list notes). Despite multiple tools using exact title matching, their purposes are clearly differentiated and descriptions specify the action (e.g., move folder vs update body). No ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_note, list_folders). The verbs clearly indicate the action, and nouns represent the resource. No mixing of conventions or vague names.
9 tools is appropriate for a note-taking server. It covers core operations (CRUD, search, move, listing of accounts/folders/notes) without being excessive. Each tool serves a clear purpose.
Basic note lifecycle is covered, but there is no way to create a note in a specific folder (must move after) and no folder management tools (create, rename, delete). These are minor gaps; core workflows are functional.