Gives Claude full read/write access to macOS Calendar.app across all configured accounts (iCloud, Google, Exchange). Reads are fast SQL queries against Calendar's local SQLite database, including proper recurring event expansion via the OccurrenceCache table. Writes go through AppleScript so changes sync back to your accounts just like manual edits. Seven tools cover the full lifecycle: list and search events, get event details with attendees, create, update, and delete. Requires Full Disk Access and Automation permissions for the host process. Runs entirely local with no network calls or telemetry. Reach for this when you need Claude to schedule meetings, find conflicts, or manage your calendar without leaving the conversation.
MCP server that gives Claude (and other MCP hosts) full access to Calendar.app on macOS — list, search, create, update, and delete events — across every account configured in Calendar.app (iCloud, Google, Exchange, etc.).
calendar-mcp.mcpb from the latest release.mcpb file — Claude Desktop installs it automaticallynpx @p-l-ta/calendar-mcp
Or install globally:
npm install -g @p-l-ta/calendar-mcp
calendar-mcp
Point your MCP host at the calendar-mcp binary (stdio transport). Example config:
{
"mcpServers": {
"calendar-app": {
"command": "npx",
"args": ["@p-l-ta/calendar-mcp"]
}
}
}
Grant these to the application that runs the MCP host (Claude Desktop, etc.):
| Permission | Where to grant |
|---|---|
| Full Disk Access | System Settings → Privacy & Security → Full Disk Access |
| Automation → Calendar | System Settings → Privacy & Security → Automation |
The MCP server process inherits permissions from the host application that launches it.
| Tool | Description |
|---|---|
list_calendars | List all calendars with name, color, account, and UUID |
list_events | List events in a date range, including recurring-event occurrences |
get_event | Get full details of a single event by UUID, including attendees |
search_events | Search events by text across title, description, and location |
create_event | Create a new calendar event |
update_event | Update properties of an existing event |
delete_event | Permanently delete an event |
list_calendars, list_events, search_events, get_event) — query Calendar's SQLite database directly for fast, structured results across all accounts. Recurring events are expanded correctly via Calendar's OccurrenceCache table.create_event, update_event, delete_event) — driven by AppleScript automation against Calendar.app, so changes sync to all connected accounts (iCloud, Google, Exchange) just as if you'd made them in the app.npm install
npm run dev # tsx watch — live reload
npm run build # compile TypeScript → dist/
npm run mcpb # build Claude Desktop extension → build/calendar-mcp.mcpb
npm run smoke # smoke-test all 7 tools against live Calendar.app data
Note:
npm run smokerequires Terminal.app (or your terminal emulator) to have Full Disk Access, since it reads Calendar.sqlitedb directly.
Interactive MCP testing:
npm run build
npx @modelcontextprotocol/inspector node dist/server.js
calendar-mcp is a local MCP server that runs entirely on your Mac. It has no backend, no telemetry, and makes no network requests of its own.
What it accesses:
~/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb) — read-only, used for list/search queriesWhat it does NOT do:
All calendar data stays on your device and is only passed to the MCP host (Claude Desktop or another client) as part of normal tool responses. You control exactly which tools Claude can invoke.
MIT
com.mcparmory/google-search
io.github.pipeworx-io/brave-search
marcopesani/mcp-server-serper
brave/brave-search-mcp-server
com.mcparmory/google-search-console
acamolese/google-search-console-mcp