English Français العربية

Calendar.app

Official registry Search and web

List, search, and manage calendar events via macOS Calendar.app across all configured accounts.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @p-l-ta/calendar-mcp
Claude Code 
claude mcp add calendar-app -- npx -y @p-l-ta/calendar-mcp@1.0.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "calendar-app": {
            "command": "npx",
            "args": [
                "-y",
                "@p-l-ta/calendar-mcp@1.0.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. calendar-mcp
  2. Prerequisites
  3. Installation
  4. Required macOS permissions
  5. Tools
  6. How it works
  7. Development
  8. Privacy Policy
  9. License

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

  1. Download calendar-mcp.mcpb from the latest release
  2. Double-click the .mcpb file — Claude Desktop installs it automatically
  3. Grant the required macOS permissions (see below)
Manual / other hosts
npx @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"]
    }
  }
}

Required macOS permissions

Grant these to the application that runs the MCP host (Claude Desktop, etc.):

PermissionWhere to grant
Full Disk AccessSystem Settings → Privacy & Security → Full Disk Access
Automation → CalendarSystem Settings → Privacy & Security → Automation

The MCP server process inherits permissions from the host application that launches it.

Tools

ToolDescription
list_calendarsList all calendars with name, color, account, and UUID
list_eventsList events in a date range, including recurring-event occurrences
get_eventGet full details of a single event by UUID, including attendees
search_eventsSearch events by text across title, description, and location
create_eventCreate a new calendar event
update_eventUpdate properties of an existing event
delete_eventPermanently 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's OccurrenceCache table.
  • 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 data

Note: npm run smoke requires 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

Privacy 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 queries
  • Calendar.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

Frequently asked questions

What is Calendar.app?

List, search, and manage calendar events via macOS Calendar.app across all configured accounts.

How do I install Calendar.app?

It runs on your machine. In Claude Code: claude mcp add calendar-app -- npx -y @p-l-ta/calendar-mcp@1.0.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Calendar.app need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Calendar.app open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Calendar.app?

It is published by p-l-ta. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.