# Add or change an event on a person's or family's calendar

> Add or change an event on a person's or family's calendar: 3 companies fully do it, 6 with a limit, 38 carry the tag. Every listing in Calendars & scheduling with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/scheduling.add-event/
- Markdown: https://www.anchorterminal.com/niches/scheduling.add-event/index.md (~1,400 tokens)
- Slim: https://www.anchorterminal.com/niches/scheduling.add-event/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/scheduling.add-event/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

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 6 | 38 | 14 | 7 |

## What counts as done

An event on the right calendar at the intended local time, with attendees and invites only when asked, created once, in one call. The event's start read back matches the requested date and weekday.

How agents ask for it: put lunch with Ana on Friday at one; add the school trip from this email to the family calendar; block two hours tomorrow morning; create an event for my flight

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Cronofy API (Cronofy Limited)**: Upsert takes the caller's event_id, so a retry updates rather than duplicates, with tzid and attendees invited only when listed, across Google, Microsoft and Apple. Read events returns localized times to check the start.
- **Microsoft Graph Calendar API (Microsoft Corporation)**: POST /events with start and end time zones, attendees only when listed, and transactionId so a retry doesn't double-book; Prefer: outlook.timezone returns local times to check.
- **Truto Unified Calendar API (Yin Yang Inc.)**: POST /unified/calendar/events on Google or Outlook with start, end, timezone, attendees and send_notifications (all, external_only, none); the reference describes an Idempotency-Key cache per account and path.

## 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.)**: Adds one or several events with time zone and repeat pattern on calendars the user can edit, saved at once. No idempotency or safe-retry guidance, and events from Google sources are read-only.
- **Apiroc Unified Calendar API (UTC Labs)**: POST /v1/events creates an event with start, end and an IANA timeZone across all four providers. No idempotency key and no parameter to send or suppress attendee invites is documented.
- **Aurinko Calendar API (Yoxel, Inc.)**: POST /v1/calendars/{id}/events with start, end and timezone and attendees; notifyAttendees=false creates silently on Google and Clio only. No idempotency key.
- **Google Calendar API (Google LLC)**: events.insert accepts a caller-set id (a retry then fails rather than duplicating), a timeZone and sendUpdates defaulting to none. acc-01 shows duplicates when a client doesn't set id, and acc-03 testing-mode tokens expiring weekly.
- **Nylas Calendar and Scheduler API (Nylas, Inc.)**: POST /v3/grants/{id}/events on any provider; notify_participants=false works on Google and EWS but Microsoft rejects it and iCloud ignores it. No idempotency key.
- **Reclaim.ai (Reclaim.ai Inc.)**: Changes an assistant proposes are staged in Preview Mode and apply only after the user approves in Reclaim, so an event isn't created in one call. No tool schema published.

- not this job: Acuity Scheduling API (Squarespace, Inc.): Acuity holds appointments on its own booking calendars; the API reference has no general event write to a person's or family calendar.
- not this job: Cal.com API v2 + MCP (Cal.com, Inc.): Cal.com writes bookings on event types into connected calendars; the API has no general event create on a person's calendar.
- not this job: Calendly API + MCP (Calendly, LLC): Calendly adds its own bookings to a connected calendar; nothing in the help centre has a general event write on a person's calendar.
- not this job: Cozi Family Organizer (Cozi, Inc.): No official write path for an outside agent; events are added in the Cozi apps, and feeds are read-only.
- not this job: SavvyCal API + MCP (SavvyCal, Inc.): SavvyCal writes bookings on scheduling links; the API and MCP have no general event create on a person's calendar.
- not this job: YouCanBookMe API (AI Software (Capacity) UK Ltd): A booking-page service; nothing in the help centre has writing a general event to a person's calendar.
- not this job: Zoom Scheduler API (Zoom Communications, Inc.): The Scheduler API books on Zoom Scheduler pages only; it has no general event write on a person's calendar.

## What stops agents finishing

- model resolves a relative date wrong and the tool accepts it
- client timeout after the write succeeds, so a retry duplicates the event and invite
- OAuth app in testing mode expires the token every 7 days

## Around it

Before: email.read-thread, document-extraction.parse-flyer, messaging.inbound. After: notifications.remind.

## Where this comes from

Weight 14 of 100 in Calendars & scheduling: 7 of 51 links; personal assistants on Google Calendar from Hacker News and voice-agent issues

As data: https://www.anchorterminal.com/api/v1/use-cases/scheduling.add-event.json, or the MCP tool get_use_case with id scheduling.add-event. 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
