Apple Calendars MCP server

Provides a TypeScript-based server for reading, creating, updating, and deleting macOS calendar events through a local HTTP bridge, enabling seamless scheduling and calendar management for desktop applications.
Back to servers
Setup instructions
Provider
Nikhil Sonti
Release date
Mar 09, 2025
Language
TypeScript
Package
Stats
3.1K downloads
3 stars

This MCP server provides a standardized interface for AI models to interact with Apple Calendars on macOS. It enables AI systems to access and manipulate calendar data through a consistent protocol, allowing for calendar management capabilities.

Prerequisites

Installation

  1. Clone this repository
  2. Install dependencies:
    npm install
    
  3. Build the TypeScript code:
    npm run build
    

Starting the Server

  1. Ensure the Calendar API Bridge is running on port 8080
  2. Start the MCP server:
    npm start
    

Available Tools

The MCP server provides several tools for AI models to work with calendar data:

  • getCalendars: List all available calendars
  • getCalendarEvents: Get events from a specific calendar
  • createCalendarEvent: Create a new event in a calendar
  • updateCalendarEvent: Update an existing event
  • deleteCalendarEvent: Delete an event from a calendar

Working with Dates

When creating or updating calendar events, you can use any of these date formats:

Supported Date Formats

  • ISO8601 with milliseconds and Z timezone (recommended):

    2025-03-09T10:00:00.000Z
    
  • ISO8601 without milliseconds:

    2025-03-09T10:00:00
    
  • ISO8601 with space instead of T:

    2025-03-09 10:00:00
    
  • ISO8601 with forward slashes:

    2025/03/09 10:00:00
    

The Calendar API Bridge handles these date formats automatically, giving you flexibility when working with calendar events.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "apple-calendar-mcp" '{"command":"npm","args":["start"]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "apple-calendar-mcp": {
            "command": "npm",
            "args": [
                "start"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "apple-calendar-mcp": {
            "command": "npm",
            "args": [
                "start"
            ]
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later