Apple Calendar
PYPI · APPLE-CALENDAR-MCP · 2 COMPONENTS
List, create, update, and delete events in Apple Calendar on macOS.
Available components
Last scanned (21 hours ago)
Scores higher than 93% of PyPI servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to JonathanRReed/Apple-MCPs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 954 tokens (~63/item across 15 items; 13 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 12% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +40
- Injection markers: unverified → pass ▲ security
- Schema quality: 37 → 63 ▼ functional
- Tool coverage: 0% → 12% ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 50 ▲ functional
- Stability: unverified → 0.87 ▲ functional
- Package version: 1.0.5 → 1.1.2 functional
- 14 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Schema quality: 37 → 63 ▼ functional
- Tool coverage: 0% → 12% ▲ functional
- Schema quality: unverified → 50 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.83 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 1.0.5 → 1.1.2 functional
- Package version: 1.0.5 → 1.1.1 functional
- 13 Oct 26 0
- Package version: 1.1.0 → 1.1.1 functional
- 12 Oct 26 −41
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 50 → unverified ▼ functional
- Package version: 1.0.5 → 1.1.0 functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 −1
- Stability: pass → 0.93 functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed pypi/apple-calendar-mcp@1.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | JonathanRReed/Apple-MCPs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/JonathanRReed/Apple-MCPs/.github/workflows/release.yml@refs/tags/v1.1.2 |
| Rekor log index | 3252400598 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:db5720e75fc7ba2896cff5775aed1db3e10a9602edccfadb4d5b5703092ab74f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calendar_create_event Create Event ~181
Create a new event in a specific Apple Calendar calendar. Use the exact calendar_id returned by calendar_list_calendars; a display name can select automation even with native access. Optional alarms: list of {minutes_before: N} or {absolute_iso: ISO datetime}. Automation can add initial display alerts only when no inherited alerts need removal; full alarm editing requires native EventKit access.
| Name | Type | Req | Description |
|---|---|---|---|
| alarms | – | – | – |
| all_day | boolean | – | – |
| calendar_id | string | yes | Select the calendar by name and source in calendar_list_calendars, then pass its calendar_id unchanged. Re-list after Calendar access changes to obtain native IDs when EventKit is available. |
| end_iso | string | yes | – |
| location | – | – | – |
| notes | – | – | – |
| recurrence | – | – | – |
| start_iso | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
calendar_delete_event Delete Event ~25
Delete a calendar event by event_id.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
calendar_get_event Get Event ~28
Fetch full details for a calendar event by event_id.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
calendar_get_prompt Calendar Get Prompt ~33
Fallback prompt rendering tool for tool-only MCP clients.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments_json | – | – | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
calendar_health Calendar Health ~16
Report the active Apple Calendar server configuration.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| access_status | string | yes | – |
| alarm_edit_backend | string | – | – |
| can_edit_existing_alarms | boolean | – | – |
| can_read_events | boolean | yes | – |
| can_write_events | boolean | yes | – |
| capabilities | array | yes | – |
| helper_available | boolean | yes | – |
| helper_compiled | boolean | yes | – |
| ok | boolean | – | – |
| permission_error | – | – | – |
| permission_suggestion | – | – | – |
| safety_mode | string | yes | – |
| server_name | string | yes | – |
| transport | string | – | – |
| version | string | yes | – |
| write_allowed_calendars | array | – | – |
No examples provided.
calendar_list_calendars List Calendars ~41
List available Apple Calendar calendars. Select by name and source, then pass the returned calendar_id unchanged. Re-list after Calendar access changes to refresh identifiers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
calendar_list_events List Events ~110
List calendar events in a time window, optionally filtered to one calendar. Use calendar_id from calendar_list_calendars. Listing through native EventKit returns native event IDs for full alarm edits.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_id | – | – | Select the calendar by name and source in calendar_list_calendars, then pass its calendar_id unchanged. Re-list after Calendar access changes to obtain native IDs when EventKit is available. |
| end_iso | string | yes | – |
| limit | – | – | – |
| start_iso | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
calendar_list_prompts Calendar List Prompts ~21
Fallback prompt discovery tool for tool-only MCP clients.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
calendar_permission_guide Calendar Permission Guide ~21
Explain how to grant Apple Calendar permission on macOS.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
calendar_recheck_permissions Calendar Recheck Permissions ~31
Recheck Calendar access after the user changes macOS permissions, and notify the client that Calendar resources changed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| access_status | string | yes | – |
| alarm_edit_backend | string | – | – |
| can_edit_existing_alarms | boolean | – | – |
| can_read_events | boolean | yes | – |
| can_write_events | boolean | yes | – |
| capabilities | array | yes | – |
| helper_available | boolean | yes | – |
| helper_compiled | boolean | yes | – |
| ok | boolean | – | – |
| permission_error | – | – | – |
| permission_suggestion | – | – | – |
| safety_mode | string | yes | – |
| server_name | string | yes | – |
| transport | string | – | – |
| version | string | yes | – |
| write_allowed_calendars | array | – | – |
No examples provided.
calendar_update_event Update Event ~271
Update one or more fields on an existing calendar event. For full alarm edits, list events using a native calendar_id and pass the returned native event_id. Existing applescript:: IDs continue to use automation after access changes. Optional alarms: list of {minutes_before: N} or {absolute_iso: ISO datetime}; pass [] to clear alarms, omit to leave unchanged. Replacing or clearing existing alarms, or combining explicit alarms with other field edits, requires native EventKit access. Automation rejects combined requests before any mutation, including [] or unchanged field values. Omit alarms for ordinary field edits; alarm-only initial alerts or [] no-ops require all alert collections verified empty.
| Name | Type | Req | Description |
|---|---|---|---|
| alarms | – | – | – |
| all_day | – | – | – |
| calendar_id | – | – | Select the calendar by name and source in calendar_list_calendars, then pass its calendar_id unchanged. Re-list after Calendar access changes to obtain native IDs when EventKit is available. |
| end_iso | – | – | – |
| event_id | string | yes | Event ID returned by calendar_list_events. For full alarm edits, list with a native calendar_id and use the returned native event_id; existing applescript:: IDs use automation. |
| location | – | – | – |
| notes | – | – | – |
| recurrence | – | – | – |
| start_iso | – | – | – |
| title | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_tool_info Get Tool Info ~48
Load the full schema, examples, and metadata for one tool from this server.
| Name | Type | Req | Description |
|---|---|---|---|
| include_examples | boolean | – | – |
| include_schema | boolean | – | – |
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_tools Search Tools ~50
Search this server's tool catalog by keyword, alias, or domain tag.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_tags | – | – | – |
| limit | integer | – | – |
| mode | string | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Apple Calendar MCP server?
Apple Calendar runs locally as a PyPI package, launched with uvx apple-calendar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · apple-calendar-mcp
claude mcp add jonathanrreed-apple-calendar-mcp -- uvx apple-calendar-mcp
What is the Apple Calendar MCP server?
Apple Calendar is an MCP server listed in the public MCP registry as io.github.JonathanRReed/apple-calendar-mcp. List, create, update, and delete events in Apple Calendar on macOS. This page covers its PyPI package (apple-calendar-mcp).
Is the Apple Calendar MCP server safe to use?
Apple Calendar scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Apple Calendar MCP server expose?
Apple Calendar exposes 13 tools: calendar_health, calendar_permission_guide, calendar_recheck_permissions, calendar_list_calendars, calendar_list_events, and 8 more. Their descriptions and schemas cost roughly 876 tokens of context every time the server is loaded.
Is the Apple Calendar MCP server still maintained?
Apple Calendar is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Apple Calendar MCP server under?
Apple Calendar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.