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_tools and get_tool_info for 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

uvx apple-calendar-mcp

git clone https://github.com/JonathanRReed/Apple-MCPs.git
cd Apple-MCPs
uv sync --all-packages

Install In AI Agents

{
  "mcpServers": {
    "apple-calendar": {
      "command": "uvx",
      "args": ["apple-calendar-mcp"],
      "env": {
        "APPLE_CALENDAR_MCP_SAFETY_MODE": "safe_manage"
      }
    }
  }
}

claude mcp add --transport stdio --scope project apple-calendar -- uvx apple-calendar-mcp

Safety Modes

• safe_readonly
• safe_manage
• full_access

Calendar allowlists

Set these environment variables in your MCP client's configuration, then restart the server:

For an assistant that may read your schedule but only write to a dedicated calendar:

{
  "APPLE_CALENDAR_MCP_SAFETY_MODE": "safe_manage",
  "APPLE_CALENDAR_MCP_WRITE_ALLOWED_CALENDARS": "AI Planning"
}

Leaving either allowlist unset or empty applies no restriction from that list. When both are set, writes must pass both; safe_readonly blocks all writes regardless of either list. Moving an event checks both the source and destination calendar. A write with an unresolved target is rejected when an allowlist is configured.

Names are exact, case-sensitive matches after trimming configuration whitespace. Every calendar with a matching name is included, so use unique calendar names for security-sensitive scopes. calendar_health reports the configured write allowlist.

These are policies enforced by the Python MCP server, not a macOS sandbox. Direct use of the native helper or bridge library does not enforce them. macOS permissions still apply, and your MCP client may send returned data to its model provider.

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_health reports access_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's Apple-Calendar-MCP/start.sh) to your MCP client
• Reload or reconnect the client so the Calendar tool surface is loaded into context
• Call calendar_health first
• If access is blocked or access_status is not_determined, call calendar_permission_guide
• After changing macOS permissions, call calendar_recheck_permissions

Prompting Notes

• tools/list returns the full Calendar tool surface. Context-constrained clients can use search_tools first, then get_tool_info for 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

• Apple-Tools-MCP