calendar-mcp
calendar-mcp
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.).
Prerequisites
macOS (Calendar.app required)
Node.js 20+
An MCP host: Claude Desktop or any stdio MCP client
Installation
Claude Desktop — one-click install (recommended)
Download
calendar-mcp.mcpbfrom the latest releaseDouble-click the
.mcpbfile — Claude Desktop installs it automaticallyGrant the required macOS permissions (see below)
Manual / other hosts
npx @p-l-ta/calendar-mcpOr install globally:
npm install -g @p-l-ta/calendar-mcp
calendar-mcpPoint your MCP host at the calendar-mcp binary (stdio transport). Example config:
{
"mcpServers": {
"calendar-app": {
"command": "npx",
"args": ["@p-l-ta/calendar-mcp"]
}
}
}Required macOS permissions
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.
Tools
Tool | Description |
| List all calendars with name, color, account, and UUID |
| List events in a date range, including recurring-event occurrences |
| Get full details of a single event by UUID, including attendees |
| Search events by text across title, description, and location |
| Create a new calendar event |
| Update properties of an existing event |
| Permanently delete an event |
How it works
Reads (
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'sOccurrenceCachetable.Writes (
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.
Development
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 dataNote:
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.jsPrivacy Policy
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:
Calendar's SQLite database (
~/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb) — read-only, used for list/search queriesCalendar.app via AppleScript — to create, update, and delete events
What it does NOT do:
Collect, store, or transmit any data outside your Mac
Connect to any external server or API
Log calendar data anywhere
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.
License
MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/p-l-ta/calendar-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server