List, search, and manage calendar events via macOS Calendar.app across all configured accounts.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"calendar-app": {
"args": [
"@p-l-ta/calendar-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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.).
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@p-l-ta/calendar-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @p-l-ta/calendar-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.
MCP Security Weekly
Get CVE alerts and security updates for io.github.p-l-ta/calendar-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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