MCP.so
Sign In

Macbook Calendar Mcp Server

@jayaprakashnarayana

About Macbook Calendar Mcp Server

An MCP (Model Context Protocol) server that securely integrates with the native macOS Calendar application. It allows AI models to read events and create new events securely using AppleScript without complex dependencies.

Basic information

Category

Productivity

Transports

stdio

Publisher

jayaprakashnarayana

Submitted by

Jay Naguboina

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mac-calendar": {
      "command": "uvx",
      "args": [
        "--from",
        "mac-calendar-mcp",
        "mac-calendar-mcp"
      ]
    }
  }
}

Tools

6

Overview

What is Macbook Calendar Mcp Server?

A native, zero-dependency bridge between Claude (or any MCP client) and your local macOS Calendar app. Your calendar data never leaves your machine, unlike cloud-based integrations that require OAuth or expose iCloud data.

How to use Macbook Calendar Mcp Server?

No complex installation is required. Add the following configuration to your claude_desktop_config.json file under mcpServers: use the uvx command with the provided Git repository and module name.

Key features of Macbook Calendar Mcp Server

  • 100% local and private – no cloud relays or iCloud passwords.
  • Zero configuration – uses calendars visible in macOS Calendar app.
  • Prompt injection protection through parameterized argv shells.
  • Native macOS TCC support requiring manual permission grant.
  • Tools: list_calendars, get_events, and add_event.

Use cases of Macbook Calendar Mcp Server

  • List all calendars available on your Mac.
  • Fetch events within a specific date range for a given calendar.
  • Securely create new calendar events with title, dates, location, and description.
  • Privacy-focused workflow without exposing calendar data to third-party APIs.

FAQ from Macbook Calendar Mcp Server

How does this server differ from Google Calendar or iCloud integrations?

It operates entirely locally using macOS Apple Events, with no OAuth tokens, no cloud relays, and no requirement to expose private iCloud data.

What permissions does the server need?

The first run requires manually granting UI permission via macOS Transparency, Consent, and Control (TCC). Nothing can access your calendar silently.

Can my calendar data be sent to an external server?

No, all data is read and written locally on your Mac. Your calendar data never leaves your machine.

Are there any runtime dependencies?

None beyond macOS and an MCP client. The server is a zero-dependency solution.

Does it work with MCP clients other than Claude?

Yes, it is designed as a bridge for any MCP client, though the quick setup example shows Claude Desktop configuration.

Comments

More Productivity MCP servers