Niches · Calendars & scheduling

Connect and keep several calendars or many users' calendars

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
12companies, fit with a limit
34companies carry the tag
14share of the category's work
7first-hand accounts

What counts as done

Each calendar connected once through a documented OAuth flow that standard MCP clients and apps complete, tokens that refresh without weekly re-consent, and read and write on every connected service through the same calls.

How agents ask for it: connect my work and personal calendars, show my busy time on both calendars, let each customer connect their Outlook or Google, why does the calendar keep asking me to log in

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Agenda Hero F
Agenda Hero, Inc.
Hosted MCP with OAuth, dynamic registration and refresh tokens, documented for Claude, Claude Code and ChatGPT. Google calendars and links come in only as read-only sources, so writes reach Agenda Hero calendars alone. source
Apiroc Unified Calendar API E
UTC Labs
Google, Microsoft, Apple and CalDAV through the same calls, one end-user account each. Production needs the developer's own Google and Microsoft OAuth apps, so Google verification falls on them; no MCP server. source
Aurinko Calendar API F
Yoxel, Inc.
One API over Google, Office 365, Outlook.com, Exchange and iCloud through Aurinko's account OAuth flow. Google and Office 365 need the developer's own OAuth apps, so verification and consent fall on them; no MCP server. source
Cal.com API v2 + MCP D
Cal.com, Inc.
Hosted MCP at mcp.cal.com uses OAuth 2.1 with dynamic registration for any client, but acc-15 hit a scope mismatch at consent (open). Connected calendars are read for busy time only; writes are bookings. source
Calendly API + MCP BB
Calendly, LLC
Hosted MCP connectors documented for Claude, ChatGPT and Muse with OAuth approval. acc-27 hit 400 invalid_client_metadata on dynamic registration from Claude Code; connected calendars are used only for Calendly's conflict checks. source
Cronofy API B
Cronofy Limited
Cronofy's own OAuth connects Google, Microsoft 365, Exchange and Apple with the same calls and signals disconnected profiles. Every synced account is billed, a month minimum for production, read-only accounts included. source
Google Calendar API A
Google LLC
OAuth reaches Google calendars only, so a person's Outlook calendar needs another integration. Sensitive scopes need verification or tokens expire weekly in testing (acc-03), and MCP clients must be marked agentic. source
Microsoft Graph Calendar API C
Microsoft Corporation
OAuth through Entra ID with refresh tokens, but Microsoft calendars only, findMeetingTimes not on personal accounts, admin consent for tenant-wide access, and the calendar MCP is a preview behind a Copilot licence. source
Nylas Calendar and Scheduler API A
Nylas, Inc.
One grant per account over Google, Microsoft, EWS and iCloud through the same calls. The MCP server authenticates with an API key and loads 38 tools; acc-35 needed two grants wired for personal and work calendars. source
Reclaim.ai E
Reclaim.ai Inc.
Works over Google Calendar and Outlook, with MCP authorisation in Claude and others that fails if the emails differ. acc-46 used it to merge calendars' busy time; no scopes or tool list published. source
SavvyCal API + MCP C
SavvyCal, Inc.
Hosted MCP with OAuth and dynamic registration for any remote client, and list_calendars flags calendars needing reconnecting. Connected calendars are only checked for conflicts, not read or written. source
Truto Unified Calendar API C
Yin Yang Inc.
One unified API and connection flow per customer account, with per-account MCP servers. Writes reach Google and Outlook only, and pricing is per connector from $999 a year. source

Doesn't do this job 4

Listings in the category that do something else, with the reason.

ListingWhy
Acuity Scheduling API E
Squarespace, Inc.
The API reads and writes Acuity's own appointments; it has no calls over a person's Google or Microsoft calendars. source
Cozi Family Organizer F
Cozi, Inc.
Google, Apple and Outlook calendars come in only as read-only subscribed feeds, with no OAuth or agent connection. source
YouCanBookMe API F
AI Software (Capacity) UK Ltd
The API uses one account-wide key over HTTP Basic, created by the Account Owner on the Team plan; there is no OAuth or MCP connection for an agent. source
Zoom Scheduler API D
Zoom Communications, Inc.
The API reaches Zoom Scheduler data through Zoom OAuth; it doesn't read or write the connected Google or Microsoft calendars. source

What stops agents finishing

  • hosted MCP OAuth rejects the client's registration or scope
  • sensitive-scope verification needed to stop weekly token expiry
  • per-connected-account fee on accounts only read

Around it

Before: agent-auth.oauth-connect. After: scheduling.find-free-slot.

Where this comes from

Weight 14 of 100 in Calendars & scheduling: 7 of 51 links; OAuth failures on hosted MCP servers and multi-calendar needs

The same as data: /api/v1/use-cases/scheduling.connect-calendars.json, or the MCP tool get_use_case with id scheduling.connect-calendars. Other jobs in this category: /api/v1/niches?category=scheduling.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.