CalendarMCP

ai.calendarmcpPublished by calendarmcp.aiOfficial publisherv1.0.0Updated Oct 25, 2026

Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Communication & Collaboration

Server details

Identifier: ai.calendarmcp/server
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to calendarmcp.ai, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.calendarmcp%2Fserver.svg)](https://sourceweft.com/mcp/ai.calendarmcp%2Fserver?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted Google Calendar MCP server that lets an AI assistant read, create, update and delete calendar events across connected Google accounts.

What you can do: List and read events across one or all connected calendars, including full event details and calendar permissions lists, with free/busy queries to find open slots before booking. Create events, including from natural-language quick-add, and partially update or delete existing events. Manage attendees by adding or removing them from events. Batch-update up to 50 events in one concurrent call, useful for renaming recurring meetings.
When to use it: Use it when you want an assistant to answer schedule questions, find free time, and book or change meetings in Google Calendar without running your own server or setting up Google Cloud credentials. It suits hosted MCP clients and users with several Google accounts or Google Advanced Protection.
Requirements: A remote MCP endpoint reached over HTTP; no local package or Docker. A Google account connected through OAuth (or service-account sharing for Advanced Protection users) and an API key from the provider's dashboard, sent as a bearer token in the Authorization header. Network access to the hosted service; rate limit of 60 requests per minute per key.

Before you install

The service is hosted and not open source, so Google account access and calendar data pass through a third party rather than staying on your machine. The API key is a secret sent in the Authorization header and should be kept private. Tools can create, update, delete and batch-modify events and change attendees, so an assistant can alter real calendars; per-calendar read/write permissions should be set in the dashboard. A free tier is offered with paid plans announced.

Installation

In SourceWeft

Open CalendarMCP in the dashboard and add it to a workspace.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.calendarmcp%2Fserver/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "calendarmcp": {
      "type": "http",
      "url": "https://calendarmcp.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

CalendarMCP

The hosted Google Calendar MCP server. Connect any AI agent to your Google Calendar in about two minutes. No self-hosting, no Docker, no credentials.json.

[Website] [Docs] [Status]

What this is

CalendarMCP is a hosted Model Context Protocol (MCP) server for Google Calendar. Connect your Google account once, get an API key, and any MCP-compatible client (Claude Desktop, Claude Code, Claude.ai, Cursor, OpenClaw, Continue, Cline, Windsurf, Goose, Zed, ChatGPT custom GPTs, n8n, etc.) can read and write your calendar.

This repo is the public docs, manifest, and client examples for the service. The hosted service is not open source. If you want a self-hosted alternative, the most popular OSS option is nspady/google-calendar-mcp and we recommend it for users who want OAuth tokens to never leave their machine.

What CalendarMCP gives you that self-hosted MCPs do not

Zero setup. One Google OAuth click. No credentials.json, no Google Cloud Console, no Docker.
HTTP transport. Works with Claude.ai, Claude Code, Cursor, and any hosted MCP client. Self-hosted stdio MCPs only work with Claude Desktop.
Batch operations. batch_update_events updates up to 50 events in one concurrent call. Renaming a recurring meeting across a year is one prompt, not 50 clicks.
Multi-account, one key. Connect any number of Google accounts (mix OAuth and service-account-shared calendars) under a single API key. Reading fans out across all of them, results merged and sorted.
Google Advanced Protection support. The only hosted MCP that works for GAP users (via service-account sharing. OAuth is blocked for those accounts).
Per-calendar Read/Write matrix. Tighten what each agent can touch from the dashboard without minting new keys.

Quick start

Visit calendarmcp.ai, sign in with Google, and copy your API key.
Add the MCP server to your client of choice. Configs below.
Talk to your agent: "What do I have on Tuesday?"

Client configs

Drop these into the right config file for your MCP client.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json

{  "mcpServers": {    "calendar": {      "command": "npx",      "args": [        "@modelcontextprotocol/server-fetch",        "https://calendarmcp.ai/api/mcp"      ],      "env": {        "MCP_AUTH_HEADER": "Authorization: Bearer YOUR_CALENDARMCP_API_KEY"      }    }  }}

{  "mcpServers": {    "calendar": {      "command": "npx",      "args": [        "@modelcontextprotocol/server-fetch",        "https://calendarmcp.ai/api/mcp"      ],      "env": {        "MCP_AUTH_HEADER": "Authorization: Bearer YOUR_CALENDARMCP_API_KEY"      }    }  }}

See examples/claude-desktop.json and our Claude Desktop integration guide.

Claude Code

bash

claude mcp add calendar https://calendarmcp.ai/api/mcp \  --transport http \  --header "Authorization: Bearer YOUR_CALENDARMCP_API_KEY"

claude mcp add calendar https://calendarmcp.ai/api/mcp \  --transport http \  --header "Authorization: Bearer YOUR_CALENDARMCP_API_KEY"

See examples/claude-code.sh and our Claude Code integration guide.

Cursor

~/.cursor/mcp.json:

json

{  "mcpServers": {    "calendar": {      "url": "https://calendarmcp.ai/api/mcp",      "headers": {        "Authorization": "Bearer YOUR_CALENDARMCP_API_KEY"      }    }  }}

{  "mcpServers": {    "calendar": {      "url": "https://calendarmcp.ai/api/mcp",      "headers": {        "Authorization": "Bearer YOUR_CALENDARMCP_API_KEY"      }    }  }}

See examples/cursor.json and our Cursor integration guide.

OpenClaw

In your openclaw.json:

json

{  "plugins": {    "entries": {      "mcp-calendarmcp": {        "enabled": true,        "config": {          "url": "https://calendarmcp.ai/api/mcp",          "authHeader": "Bearer YOUR_CALENDARMCP_API_KEY"        }      }    }  }}

{  "plugins": {    "entries": {      "mcp-calendarmcp": {        "enabled": true,        "config": {          "url": "https://calendarmcp.ai/api/mcp",          "authHeader": "Bearer YOUR_CALENDARMCP_API_KEY"        }      }    }  }}

See examples/openclaw.json and our OpenClaw integration guide.

Other clients

See examples/ for Continue, Windsurf, Goose, n8n, and more.

Tools

CalendarMCP exposes 11 tools. The full machine-readable schema lives at https://calendarmcp.ai/api/docs.

Tool	Description
`list_events`	List events across one or all connected calendars in a time range. Auto-paginates up to 2500 results.
`get_event`	Full details of one event.
`create_event`	Create an event. Supports attendees, location, reminders, recurrence, all-day.
`update_event`	Partial update of an existing event.
`delete_event`	Delete an event.
`quick_add_event`	Create from natural language ("Lunch with Sam Friday 1pm").
`list_calendars`	List every calendar the API key can see, with per-calendar R/W permissions.
`find_free_time`	Free/busy query across one or more calendars. The right thing to call before `create_event` to prevent double-booking.
`manage_attendees`	Add or remove attendees from an event.
`batch_update_events`	Update up to 50 events in one concurrent call.

Full reference: docs/tools.md.

Authentication

API keys are issued from the dashboard at calendarmcp.ai/dashboard. One key can hold any number of connected Google accounts. Per-calendar R/W scopes are enforced server-side.

Rate limit: 60 requests/minute per key. Free tier; pay-as-you-go pricing for higher limits coming soon.

See docs/authentication.md.

Google Advanced Protection

If you have Google Advanced Protection enabled, OAuth into third-party calendar apps is blocked by Google policy. CalendarMCP supports a service-account sharing flow that works for GAP users. We're the only hosted MCP we know of that supports this.

See docs/google-advanced-protection.md.

Roadmap

✅ Google Calendar (live)
⏳ Microsoft Outlook Calendar (waitlist)
⏳ iCloud Calendar (waitlist)
⏳ CalDAV (any provider)

Pricing

Free tier with generous limits. Paid plans land soon for power users.

See calendarmcp.ai/pricing.

Comparison

Feature	CalendarMCP	nspady (OSS)	Composio	Zapier MCP
Hosted	✅	❌	✅	✅
HTTP transport	✅	❌ (stdio only)	✅	✅
Setup time	2 min	25 min	10 min	5 min
Batch update events	✅	❌	❌	❌
Multi-account, one key	✅	❌	❌	❌
Google Advanced Protection	✅	❌	❌	❌
Per-calendar R/W matrix	✅	❌	❌	❌
Open source	❌	✅	partial	❌
Tokens on your machine	❌	✅	❌	❌

Honest read: pick nspady if you only use Claude Desktop and want zero third parties. Pick CalendarMCP for everything else.

Contributing

This repo is docs and examples. PRs welcome for:

New client config examples
Doc improvements and clarifications
Translations

Service issues (bugs, feature requests for the hosted product) → GitHub Issues.

License

Examples and docs in this repo: MIT (see LICENSE).

The hosted service is not open source.

Links

Source: README.md at commit cb6a55d

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.

Other Calendarmcp integrations

Calendarmcp

Published by GitHub account aernouddekker

Local MCP server that lets an assistant read and manage macOS Calendar.app calendars, events, attendees and alarms via AppleScript.

STDIODesktop only

Productivity & WorkflowNot validated yetNov 3, 2026