AllMyMeetings Launches Its Calendar MCP Server

AllMyMeetings ships a built-in Model Context Protocol (MCP) server. Connect Claude, ChatGPT, Cursor or any other MCP client to your AllMyMeetings account, and your assistant can work with every calendar you've connected: Google, Outlook and iCloud.

This post covers what launched and what has changed since. For setup steps and config for each client, see the MCP server setup guide.

What's new since launch

October 2026: OAuth sign-in for connectors. Claude custom connectors (claude.ai and Claude Desktop) and ChatGPT connectors now connect with OAuth 2.1. Add https://allmymeetings.com/mcp/calendar as a custom connector, sign in to AllMyMeetings and approve access. You don't need to create or paste a token.

October 2026: read-only and expiring tokens. For clients that use a personal access token, such as Cursor, VS Code or your own scripts, tokens can now be read-only or read-write, and expire after 30, 90 or 365 days. A read-only token only sees the tools that don't change data.

Recurring events. The event creation tool accepts an iCalendar RRULE, so your assistant can create a weekly standup or a monthly review in one call.

Listed in the official MCP Registry as com.allmymeetings/calendar.

What is MCP?

The Model Context Protocol is an open standard, created by Anthropic, for connecting AI clients to servers that provide tools and data. Any client that speaks MCP can connect to any server that speaks MCP.

Connect once to AllMyMeetings, and every MCP client you use can reach your calendars through the same server.

What the MCP server exposes

The server provides 21 tools and 4 resources.

Events and availability

• List events from any or all connected calendars for a time range
• Create events, including recurring events, on any connected calendar. Your syncs copy them to the other calendars.
• Update events: title, time, description or location
• Delete events from one calendar, or along with all their synced copies
• Check availability across every connected calendar at once
• Check conflicts for a proposed time

Sync pairs

• Create, list, update and delete sync pairs. Choose the direction (one-way, or two-way on Pro and above) and the mode (Full details, Free/Busy or Private, depending on your plan).
• Check sync status to see whether everything is healthy.

If you've been meaning to sync your Google Calendar with Outlook, you can now ask your assistant to do it.

Calendars and connections

• Connect a provider. Your assistant starts the Google or Microsoft sign-in, or the iCloud connection, and gives you the link to finish it.
• Check connection status, list calendars, turn syncing on or off for a calendar, force a fresh sync of a calendar that looks out of date, and disconnect an account.

Account and scheduling

• Get account details, check plan limits and start an upgrade (returns a Stripe checkout link).
• Create scheduling links: booking pages that check your connected calendars for conflicts. This is the one tool that needs a paid plan.

Resources

The full list of tool names and descriptions, generated from the live server, is at /llms-full.txt.

Which plan do you need?

Any plan, including the free plan. The MCP server isn't read-only on the free plan: your assistant can read and write events and create sync pairs. Your plan's limits still apply to what it creates. The free plan allows 2 calendar accounts and 1 one-way sync in Free/Busy mode. Two-way sync and the other privacy modes need Pro. See plans and limits.

Security

• Calendar connections use the providers' own sign-in. Google and Microsoft connect through OAuth, so AllMyMeetings never sees those passwords. iCloud uses an app-specific password you create at account.apple.com and can revoke at any time.
• MCP access is scoped to your account. OAuth connectors get access only after you approve them. Personal access tokens can be read-only, expire on a schedule, and can be revoked from Settings → API.
• Rate limits. MCP calls are limited per day by plan.

Built on Laravel MCP

The server is built on the official Laravel MCP package. For Laravel developers, it's a real-world example of Laravel MCP in production: tools registered with #[Description] attributes, shouldRegister() to hide write tools from read-only tokens, and Passport plus Sanctum for authentication. Endpoint and auth details for developers are on the developer page.

Get started

Sign up free, then follow the MCP server setup guide for your client. In Claude or ChatGPT, that's: add the connector URL, sign in, approve.

For a step-by-step example of setting up calendar sync from a conversation, read how to set up calendar sync with Claude.

See all features · Compare plans