mcp-apple-notes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_APPLE_NOTES_VERBOSE | No | Enable verbose logging. Set to '1' to see every JXA call before it executes. | |
| MCP_APPLE_NOTES_READ_ONLY | No | Restrict to read-only tools. Set to '1' to disable create, edit, append, move, and delete operations. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index-notesA | Index all Apple Notes for semantic search. Run this first — takes seconds to minutes depending on note count. |
| list-foldersA | List all Apple Notes folders with full paths and note counts |
| list-notesA | List Apple Notes with title, path, and timestamps. Optionally filter by folder path and include note content. |
| search-notesB | Semantic and full-text search over notes. Optionally filter by folder path. |
| get-noteA | Get a note's full content and details by noteId or title. Optionally scope by folder path. If the title is ambiguous, returns a list of matching candidates — retry with noteId or path to disambiguate. |
| create-noteA | Create a new Apple Note with a title and markdown content. Optionally place it in a folder path. |
| edit-noteA | Edit an existing Apple Note's title and/or content. Identify note by noteId or current title. |
| append-to-noteB | Append content to the end of an existing Apple Note. Identify note by noteId or title. |
| move-noteA | Move a note to a different folder. Identify note by noteId or title. Use list-folders to get available paths. |
| delete-noteA | Delete an Apple Note (moves to Recently Deleted). Identify note by noteId or title. |
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 10 tools
Each tool targets a distinct action and resource: indexing, listing folders, listing notes, searching, getting, creating, editing, appending, moving, and deleting. While list-notes with content and get-note overlap slightly, the descriptions clearly differentiate listing summaries versus fetching full details.
All tools follow a consistent snake_case verb_noun pattern: index-notes, list-folders, search-notes, get-note, create-note, etc. This makes the tool set predictable and easy to navigate for an agent.
With 10 tools, the server is well-scoped for Apple Notes management. Each tool covers a necessary operation without bloat, and the count feels appropriate for the domain.
The surface covers the full note lifecycle: index, list, search, get, create, edit, append, move, and delete. Folder listing supports scoping operations, leaving no obvious dead ends for common workflows.