Apple Calendar
MCP server for Apple Calendar on macOS.
Provides access to calendars and events through EventKit. Keep Calendar as the system of record while enabling agents to read, create, update, and delete events.
When to use
- Calendar-only workflows
- EventKit-backed calendar access without the all-in-one server
- Tighter app-level separation for scheduling
What It Does
- Discover and list calendars
- Create, read, update, and delete events
- Tool discovery helpers
search_toolsandget_tool_infofor context-constrained clients - Today resources and planning prompts
- Health checks that distinguish empty results from blocked access
- Read fallback through Calendar.app automation when native EventKit reads are blocked on supported local setups
- Permission recovery:
calendar_permission_guide,calendar_recheck_permissions
Install On This Mac
Quick start (uvx, from PyPI)
With uv installed:
uvx apple-calendar-mcp
No clone, no venv management.
From a clone
git clone https://github.com/JonathanRReed/Apple-MCPs.git
cd Apple-MCPs
uv sync --all-packages
This builds one workspace environment with every server's entry point in .venv/bin (for example .venv/bin/apple-calendar-mcp). You can also point an MCP client at Apple-Calendar-MCP/start.sh, which prefers uv run and falls back to a plain venv bootstrap (Python 3.11+ required).
Install In AI Agents
Generic MCP client config
{
"mcpServers": {
"apple-calendar": {
"command": "uvx",
"args": ["apple-calendar-mcp"],
"env": {
"APPLE_CALENDAR_MCP_SAFETY_MODE": "safe_manage"
}
}
}
}
Running from a clone instead? Use /path/to/Apple-MCPs/Apple-Calendar-MCP/start.sh as the command with empty args.
Claude Code example
claude mcp add --transport stdio --scope project apple-calendar -- uvx apple-calendar-mcp
Safety Modes
safe_readonlysafe_managefull_access
Transport
stdio is the default and recommended transport. Set APPLE_CALENDAR_MCP_TRANSPORT=streamable-http (with optional APPLE_CALENDAR_MCP_HOST and APPLE_CALENDAR_MCP_PORT) to serve Streamable HTTP instead.
macOS Permissions
- Calendar access is required
calendar_healthreportsaccess_status, read access, and write access so agents can detect blocked permissions before treating an empty window as real data
Launch Checklist
- Add
uvx apple-calendar-mcp(or a clone'sApple-Calendar-MCP/start.sh) to your MCP client - Reload or reconnect the client so the Calendar tool surface is loaded into context
- Call
calendar_healthfirst - If access is blocked or
access_statusisnot_determined, callcalendar_permission_guide - After changing macOS permissions, call
calendar_recheck_permissions
Prompting Notes
tools/listreturns the full Calendar tool surface. Context-constrained clients can usesearch_toolsfirst, thenget_tool_infofor the Calendar tool they need.- Before creating events, confirm the date, time, duration, and title with the user
- Use Calendar for scheduled time blocks, meetings, and appointments
Related
Release files for apple-calendar-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apple_calendar_mcp-1.0.3.tar.gz | 28.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apple_calendar_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.5 kB
Release files / apple_calendar_mcp-1.0.3.tar.gz
| Download URL | apple_calendar_mcp-1.0.3.tar.gz |
|---|---|
| Size | 28.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9416ed6d21c443f09f1e5a842c1eaecc09788646b327e78948659bc85d96fafc
|
|
BLAKE2b-256 checksum How to use checksums |
a5f06b725e91ff480a6031cd4d7bb2ba3de473d2d34e4ccd5afc9ed348411673
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logRelease files / apple_calendar_mcp-1.0.3-py3-none-any.whl
| Download URL | apple_calendar_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 25.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38f66d54004543da82018dc98049480fd68120fdc35690bb3bef950d81cbd894
|
|
BLAKE2b-256 checksum How to use checksums |
352f89bd023f9d12e7da0cc0723ab99de7f184ab21ac3282780203c274785485
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency log