The one tool creates an event: there is no list, no search, no update and no delete, which means the agent cannot check for a clash beforehand and cannot take back what it just created. What it does do in one call is the entire event — summary, start and end, attendees, location, description and reminders — so booking something does not turn into a sequence of follow-up edits.
A single-tool Google Calendar writer: one call creates an event with its times, guests, place and reminders. It authenticates with your own Google OAuth client rather than a hosted service.
- create_event, which creates a calendar event from a summary, a start time and an end time.
- Attendees, a location, a description and reminders carried on the same call rather than added afterwards.
Node.js v18 or later, and a Google Cloud project with the Calendar API enabled. Three values go into the environment: the OAuth client ID and secret, and a refresh token for the Google account whose calendar is being written to — which means the one-time OAuth dance happens before this server is any use.
One command plus a key — npx -y @tobedoit/google-calendar-mcp, then supply credentials