Google Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your Google Cloud OAuth client ID | |
| GOOGLE_REDIRECT_URI | Yes | The OAuth redirect URI, typically http://localhost:4153/oauth2callback | http://localhost:4153/oauth2callback |
| GOOGLE_CLIENT_SECRET | Yes | Your Google Cloud OAuth client secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getEventsA | List events from a Google Calendar within an optional time range. |
| createEventA | Create an event on a Google Calendar. Supports all-day events, attendees, reminders and RFC5545 recurrence rules. |
| updateEventA | Update an existing Google Calendar event. Omitted fields keep their current values. |
| deleteEventC | Delete an event from a Google Calendar by its event ID. |
| authenticateA | Start the Google Calendar OAuth flow. Opens a browser window for consent and stores the resulting tokens in memory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| view_upcoming_events | Show my upcoming events |
| create_meeting | Create a new meeting |
| find_free_time | Find available time slots |
| reschedule_event | Reschedule an existing event |
| cancel_event | Cancel an existing event |
| weekly_schedule_overview | Get a weekly schedule overview |
| create_recurring_meeting | Create a recurring meeting |
| find_meeting_conflicts | Check for scheduling conflicts |
| prepare_for_today | Get today's schedule summary |
| schedule_around_event | Schedule new events around existing ones |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| primary_calendar | User's primary Google Calendar |
| user_calendars | List of all calendars accessible to the user |
TDQS
Scored across 5 tools
Each tool targets a distinct action on calendar events—listing, creating, updating, deleting—plus a separate authentication flow. There is no overlap or ambiguity between the tools.
Four tools follow a clear verb+Event pattern (getEvents, createEvent, updateEvent, deleteEvent), while authenticate is a necessary but non-parallel exception. Overall the naming is predictable and easy to infer.
Five tools is a well-scoped set for a Google Calendar event server: authentication plus full CRUD operations. Each tool serves a clear purpose without unnecessary bloat.
The server covers the full event lifecycle—list, create, update, delete—and includes OAuth authentication as a prerequisite. There are no obvious dead ends or critical missing operations for managing calendar events.