AllMyMeetings Now Supports the Model Context Protocol (MCP)

If you've ever wished you could manage your calendars without leaving your IDE, your terminal, or whatever tool you're already working in — you can now.

AllMyMeetings ships a built-in Model Context Protocol (MCP) server. Connect Claude Desktop, Cursor, Windsurf, or any MCP-compatible client to your AllMyMeetings account, and your entire calendar stack — Google, Outlook, iCloud — becomes accessible from that client.

This isn't a chatbot feature or an "AI assistant." It's infrastructure. Your MCP client talks to our server, and our server talks to your calendars. What you do with that connection is up to you.

What is MCP?

The Model Context Protocol is an open standard created by Anthropic that defines how clients connect to external servers that provide tools and data. Think of it as a standardized interface: any client that speaks MCP can connect to any server that speaks MCP.

Before MCP, integrating calendar operations into your workflow meant building custom API integrations, writing glue code, or hoping someone built a plugin for your specific tool. MCP changes that by giving every compatible client the same standardized way to discover and call tools on remote servers.

The practical result: connect once to AllMyMeetings, and every MCP-compatible tool you use gains access to your unified calendar stack.

What the MCP server exposes

The AllMyMeetings MCP server provides 21 tools and 4 resources across five categories.

Calendar operations

The core of what you'd expect:

• List events — Pull events from any or all connected calendars for a given time range
• Create events — Add events to any connected calendar, with automatic propagation to synced calendars
• Update events — Modify existing events (title, time, description, attendees)
• Delete events — Remove events from specific calendars or all synced copies
• Check availability — Query free/busy across every connected calendar simultaneously
• Detect conflicts — Check whether a proposed time block overlaps with anything on any calendar

This is the same availability engine that powers AllMyMeetings scheduling pages, exposed as MCP tools.

Sync pair management

Manage the sync configuration that keeps your calendars aligned:

• Create sync pairs — Set up a new sync between two calendars with your choice of direction (one-way or bidirectional) and mode (full details, free/busy, or private)
• List sync pairs — See all active sync configurations
• Update sync pairs — Change direction, mode, or other settings
• Delete sync pairs — Remove a sync pair and optionally clean up synced events

If you've been meaning to sync your Google Calendar with Outlook but haven't gotten around to configuring it, you can now do it from whatever tool you're already in.

Scheduling

• Create scheduling links — Generate booking pages with custom durations and availability windows (Pro and Business plans)

Account and connections

• Check account status — View your current plan, usage, and limits
• Connect calendar providers — Initiate OAuth flows for Google and Microsoft, or set up iCloud
• Check connection status — Verify calendar provider connections are healthy
• Disconnect providers — Revoke access to a connected calendar account

Read-only resources

Four MCP resources provide live data your client can subscribe to:

How to connect

Setting up takes a few minutes.

1. Generate an API token

From your AllMyMeetings dashboard, navigate to Settings and generate a personal access token. This token authenticates your MCP client.

2. Configure your client

Add the AllMyMeetings MCP server to your client's configuration. The specifics depend on your client:

Claude Desktop — Add the server URL and token to your claude_desktop_config.json.

Cursor / Windsurf — Follow the client's MCP server configuration flow and provide the endpoint URL and your API token.

Any MCP client — Point it at your AllMyMeetings MCP endpoint with your token as the bearer credential.

3. Start using it

Once connected, your client discovers the available tools and resources automatically. Query your events, create sync pairs, check availability — whatever your workflow needs.

Who is this for?

Developers who live in their tools. If you spend your day in Cursor or Claude Desktop and don't want to context-switch to a calendar app to check if you're free at 3 PM — this is for you.

Automation builders. If you're building workflows that need calendar awareness — checking availability before scheduling, creating events as part of a larger pipeline, monitoring sync health — the MCP server provides a standardized interface.

Power users. If you manage multiple calendars across Google, Outlook, and iCloud and want a single integration point instead of three separate APIs — AllMyMeetings unifies them behind one MCP server.

This is not a replacement for the AllMyMeetings dashboard. It's an additional access layer for people who prefer working through MCP-compatible tools.

Security

OAuth 2.0 for calendar connections. Google and Microsoft connections use standard OAuth flows. We never store your provider passwords.

Sanctum tokens for MCP access. Your MCP client authenticates with a personal API token scoped to your account. You can revoke tokens at any time from your dashboard.

Rate limiting. API requests are rate-limited per plan tier to prevent abuse and ensure service reliability.

Plan-based access. Tools are gated by your subscription plan. The free tier supports read operations. Pro and Business plans unlock full calendar management and scheduling tools.

Built on Laravel MCP

The AllMyMeetings MCP server is built on the official Laravel MCP package — the same framework that powers the rest of the application. This means it benefits from Laravel's authentication, middleware, and rate limiting infrastructure out of the box.

For Laravel developers: yes, this is a real-world example of Laravel MCP in production. The server registers tools with #[Description] attributes, uses shouldRegister() for plan-gating, and leverages Sanctum for token authentication.

What's on the roadmap

The MCP server shipping today covers the core calendar management workflows. Coming next:

• Recurring event management — Create and modify recurring events with full instance exception support
• Attendee availability — Check availability across multiple users' calendars (with their permission)
• RSVP tracking — Accept or decline meeting invitations through your MCP client
• Webhook notifications — Proactive alerts for calendar changes, new conflicts, or sync issues

These will land as updates to the existing MCP server — no reconfiguration needed.

Get started

If you're already using AllMyMeetings, generate an API token from your dashboard and connect your MCP client.

If you're new, sign up free and connect your calendars. The free plan supports read operations through the MCP server. Upgrade to Pro for full access — event creation, sync management, scheduling, and everything else.

If you're evaluating calendar sync tools and MCP support matters to you, AllMyMeetings is the only calendar sync platform with a native MCP server. No plugins, no middleware, no third-party connectors. It's built in.

AllMyMeetings syncs Google Calendar, Outlook, and iCloud in real time. The MCP server is available now on all plans. Get started free.

/features · /pricing