MCP servers that can manage calendar events
3 verified servers expose a tool that can create and manage calendar events
A calendar is where intent becomes a commitment with a time on it. For an agent, managing one means reading what is already scheduled, adding new events, and moving or canceling them when plans change, without a human opening the calendar app.
These verified servers let an agent create and manage calendar events.
Google Calendar (Workspace MCP)
taylorwilsdon
The Google Workspace MCP, scoped to Calendar, lets an agent read your calendars, create events, and check availability over OAuth.
manage_eventget_events
manage_event creates, updates, and deletes an event in one tool, and get_events reads the existing schedule so the agent can check availability before booking, the most direct calendar control here.
Nextcloud
Chris Coutinho
Production-ready community MCP server for Nextcloud: files, notes, calendar, contacts, tables, deck, talk, and more across 110+ tools.
nc_calendar_create_eventnc_calendar_update_eventnc_calendar_delete_event
Nextcloud exposes the full event lifecycle, create, update, and delete, for teams that self-host their calendar alongside their files and contacts.
Cal.com
Cal.com
Cal.com's official MCP server lets agents manage event types, bookings, schedules, and availability over OAuth.
create_bookingreschedule_bookingcancel_booking
Cal.com operates at the booking layer: create_booking reserves a slot on a scheduling page, and reschedule_booking and cancel_booking move or release it, fitting appointment flows rather than raw calendar entries.
What to know
The shape of the capability depends on whether you run a calendar or a booking flow. Google Calendar's manage_event handles the create, update, and delete of an event in one tool, and get_events reads what is already on the calendar so the agent can check for conflicts before it writes. Nextcloud splits the same lifecycle across nc_calendar_create_event, nc_calendar_update_event, and nc_calendar_delete_event for teams that self-host their calendar. Cal.com works at the booking layer: create_booking takes a slot on a scheduling page, and reschedule_booking and cancel_booking move or release it, which is the right fit when the event is an appointment someone booked.
The context worth keeping is what the agent already scheduled. An event written and then forgotten leads to double-bookings on the next run. Reading existing events before writing a new one, and remembering which it created, is what keeps an agent from stacking two meetings on the same hour.
Questions
- Can an agent check availability before creating an event?
- Yes, where the server exposes a read. Google Calendar's get_events returns what is already scheduled, and Nextcloud lists events on a calendar, so an agent can scan for conflicts before it writes. Cal.com handles availability on the scheduling page itself, offering only open slots to book.
- What is the difference between a calendar event and a booking?
- A calendar event is an entry you create directly on a calendar, which Google Calendar and Nextcloud do. A booking is a slot someone reserves on a scheduling page, which is Cal.com's model. Both end up as an event with a time, but the booking flow adds availability and confirmation around it.