# Connect and keep several calendars or many users' calendars

> Connect and keep several calendars or many users' calendars: 0 companies fully do it, 12 with a limit, 34 carry the tag. Every listing in Calendars & scheduling with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/scheduling.connect-calendars/
- Markdown: https://www.anchorterminal.com/niches/scheduling.connect-calendars/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/scheduling.connect-calendars/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/scheduling.connect-calendars/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

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

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 12 | 34 | 14 | 7 |

## 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

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.

- **Agenda Hero (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.
- **Apiroc Unified Calendar API (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.
- **Aurinko Calendar API (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.
- **Cal.com API v2 + MCP (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.
- **Calendly API + MCP (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.
- **Cronofy API (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.
- **Google Calendar API (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.
- **Microsoft Graph Calendar API (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.
- **Nylas Calendar and Scheduler API (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.
- **Reclaim.ai (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.
- **SavvyCal API + MCP (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.
- **Truto Unified Calendar API (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.

- not this job: Acuity Scheduling API (Squarespace, Inc.): The API reads and writes Acuity's own appointments; it has no calls over a person's Google or Microsoft calendars.
- not this job: Cozi Family Organizer (Cozi, Inc.): Google, Apple and Outlook calendars come in only as read-only subscribed feeds, with no OAuth or agent connection.
- not this job: YouCanBookMe API (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.
- not this job: Zoom Scheduler API (Zoom Communications, Inc.): The API reaches Zoom Scheduler data through Zoom OAuth; it doesn't read or write the connected Google or Microsoft calendars.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/scheduling.connect-calendars.json, or the MCP tool get_use_case with id scheduling.connect-calendars. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
