apple-calendar-jxa-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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calendar_calendarsA | Reads all calendar collections (name, account, id, writable). Use this first to discover exact calendar names before filtering or creating events. Note: several calendars can share the same name across accounts — disambiguate with the id. |
| calendar_eventsA | Manages Apple Calendar events: read, create, update, delete. Recommended format: 'YYYY-MM-DD HH:mm:ss' (local time, e.g. '2026-07-14 09:00:00'). 'YYYY-MM-DD' also works. Reading defaults to today + 14 days. Attendee participation (accept/decline invitations) cannot be changed — this is an Apple platform limitation; attendee statuses are readable. |
| calendar_free_slotsA | Finds free time slots across calendars in a date range — e.g. to plan a call or a week. Busy times are taken from all (or selected) calendars; all-day events and events marked "free" are ignored by default. Recommended format: 'YYYY-MM-DD HH:mm:ss' (local time, e.g. '2026-07-14 09:00:00'). 'YYYY-MM-DD' also works. |
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 3 tools
Each tool serves a clearly distinct purpose: listing calendars, managing events, and finding free slots. No overlapping functionality.
All tool names follow a consistent 'calendar_' prefix followed by a plural noun ('calendars', 'events', 'free_slots'), maintaining uniform snake_case.
Three tools cover the essential calendar operations (discovery, event CRUD, and free time lookup) without being too few or too many for the domain.
Covers core workflows (list calendars, manage events, find free slots). Minor gap: no tool to create or delete calendars, though that may be intentional for safety.