Claude Apple Calendar integration over MCP

Can Claude connect to Apple Calendar?

Yes. This connection reaches iCloud calendars through CalDAV, so the relevant data must be in iCloud. A calendar stored only on a Mac is a different data source. You do not need to keep that Mac running for the AIPx connection.

Give the agent a bounded date window and time zone. “What is free tomorrow?” needs the intended calendar and local day, not an assumption based on the agent’s system clock. Check the calendar identifier before creating or moving an event.

For a scheduling task, read existing events first and propose the target time separately. An app-specific password provides provider access; it is not a per-agent read-only scope. AIPx can hide writes for a planning agent while allowing a scheduling assistant to propose changes.

Apple Calendar MCP options

Apple’s app-specific password guidance explains the credential requirement. The iCloud calendar MCP project and Apple Calendar MCP project are separate community options. Neither makes this adapter an Apple-authored MCP server.

Local automation may suit a calendar that never leaves your Mac. AIPx adds another service holding the app-specific credential and processing calendar data, in return for remote access shared among approved agents.

How to connect Apple Calendar to Claude

Use your Apple Account email and an app-specific password generated after enabling two-factor authentication. Do not enter your primary Apple Account password into the agent config.

1. Open the AIPx dashboard, choose Apple Calendar under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Apple Calendar; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Apple Calendar

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Apple Calendar is the only service you need.

Apple Calendar MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Use /mcp for AIPx authorization, then list iCloud calendars and check the intended calendar ID. Read a short date window before event creation. Claude Code MCP setup covers client registration.

Apple Calendar MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

Complete Cursor sign-in and read events for an explicit local date and time zone. Keep event changes hidden for a planning-only job. See Cursor MCP setup for configuration scope.

Apple Calendar MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Apple Calendar credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

ChatGPT can use this iCloud endpoint where custom MCP is permitted. It does not gain local Mac calendar access, and writes need their own rules. ChatGPT MCP setup explains account, client and administrator conditions.

Scope Apple Calendar per agent

A daily planner needs calendar discovery and event reads. Hide create_event and update_event for that agent. A scheduling assistant can keep those tools on Confirm, showing the destination calendar, start, end and time zone before asking for client approval.

These recommendations are separate from the general Allow-for-read and Confirm-for-write defaults. If the client does not honor Confirm, use Hide. MCP permissions describes the actual tool boundary; a polite prompt alone does not revoke write access.

Connect Apple Calendar to ChatGPT

Add the AIPx endpoint through custom MCP only when your ChatGPT account, supported client and workspace policy allow it. There is no universal promise that every free or mobile account supports that flow. The ChatGPT guide has the current requirements.

Use Apple Calendar and Google Calendar in one agent

Connect Google Calendar separately, then ask for overlaps with both account names and a time zone. Keep both read-only while choosing a slot. Things 3 can receive a follow-up task after approval, and Granola or Fireflies can supply meeting notes.

iCloud event and calendar limits

Do not assume full Apple Calendar parity for recurrence rules, time-zone edge cases or conflict handling. Use small changes and verify the resulting event in the calendar. Date-window queries are bounded; a short response is not necessarily the entire calendar history.

If authentication fails, check the account email and app-specific password rather than trying the primary password. Revoking the app-specific credential will remove provider access until you reconnect. AIPx does not synchronize iCloud and Google calendars simply because both are connected.

Browse all MCP integrations to choose another connection for this agent.

The Apple Calendar connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.