# Apple Calendar [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/mgcrea/cupertino  
**GitHub Stars:** 5  
**npm Downloads (last month):** 1282  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/apple-calendar-2

## Description
Search, read and act on Apple Calendar — ranges, free-time lookup, writes off by default

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "apple-calendar": {
    "command": "npx",
    "args": ["-y","@mgcrea/mcp-apple-mail"]
  }
}
```

## Documentation

## What Apple Calendar does

The Apple Calendar MCP server connects an MCP-compatible agent to the Calendar app already configured on a Mac. It provides calendar operations for inspecting events across date ranges, searching calendar data, and locating available time. The Calendar surface contains 10 tools and also includes write capabilities, although those mutating tools are disabled by default.

This package is one surface in the Cupertino project, which provides separate MCP servers for several Apple apps. Loading the Calendar surface independently lets a host expose only the calendar tools needed by an agent rather than the full set of Apple app integrations.

## How it works

The server brokers access to Apple Calendar through the app's scripting interface and the shared Cupertino core. An MCP host starts the server, and the server translates agent requests into calendar operations on the Mac. The repository describes shared handling for the Apple-event boundary, TCC-aware errors, and a read-only SQLite component.

Calendar writes are controlled per surface. When writes are disabled, the mutating tools are not registered with the MCP host, so an agent cannot discover or invoke them. Enabling writes makes those tools available and allows the agent to perform supported calendar changes.

## Setup and configuration

The npm package can be launched with `npx`, or the project can be built from source and started using the Calendar package's compiled CLI. A source installation requires cloning the repository, running `pnpm install`, and running `pnpm build`; the host can then be configured with an absolute path to `packages/calendar/dist/cli.js`.

The repository also provides a signed Cupertino app that can broker the servers through one application-level permission grant. Install it with Homebrew using the project's cask, then configure the host to use the app's bridge when that permission model is preferred. Running the package directly instead grants the required macOS permission to the process that launches it, such as an editor or terminal.

The Apple Calendar MCP server requires macOS Calendar access and does not require a license key. Writes must be enabled explicitly according to the project's configuration process; the default is read-only operation.

## Tools and capabilities

The Calendar surface supports:

- Querying events over date ranges
- Searching calendar data
- Looking up free time
- Performing calendar writes when the write gate is enabled
- Exposing 10 Calendar-focused MCP tools through its own server

These capabilities suit agents that need schedule context, such as checking commitments before drafting a plan or finding open time for a proposed meeting.

## Limitations and notes

The Apple Calendar MCP server is unofficial and is not affiliated with Apple. It operates on the calendars available through Apple Calendar on the local Mac, rather than providing a standalone hosted calendar service.

Permission behavior depends on how the server is launched. Direct npm execution assigns macOS access to the launching host process, while the signed Cupertino app is designed to hold one Full Disk Access grant for its bridged surfaces. The server should therefore be configured with the permission model appropriate to the deployment.

Calendar writes are not available by default. Agents that need only schedule inspection can leave the write gate closed, while workflows that change calendar data must enable it deliberately.

_Full upstream README: https://allmcps.com/mcp/apple-calendar-2/readme_