Google Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_eventsA | Retrieve a list of calendar events based on specified filters. This function queries the calendar for events that match the given criteria. All filter parameters are optional and can be used in combination to narrow down the results. Args: summary (str, optional): Filter events by their summary (title or subject). description (str, optional): Filter events by text found in the event description. location (str, optional): Filter events based on their location. timeMin (str, optional): ISO 8601 formatted lower time bound (exclusive) for filtering events by end time. Must be in local time and have timezone offset. timeMax (str, optional): ISO 8601 formatted upper time bound (exclusive) for filtering events by start time. Must be in local time and have timezone offset. maxResults (int, optional): Maximum number of events to return. Returns: list: A list of event objects that match the provided filters. |
| create_eventA | Creates a calendar event using the provided details. Args: start (str): Event start time in ISO 8601 format (e.g., '2025-04-06T10:00:00-07:00'). end (str): Event end time in ISO 8601 format (e.g., '2025-04-06T11:00:00-07:00'). timeZone (str): User timezone formatted as an IANA Time Zone Database name (e.g. "Europe/Zurich"). summary (str): Short title or subject of the event. description (str, optional): Detailed description or notes for the event. Defaults to None. location (str, optional): Physical or virtual location of the event. Defaults to None. |
| delete_eventB | Deletes an event from the calender. Args: event_id: Event identifier. |
| update_eventA | Updates an event by replacing specified fields with new values. Any fields not included in the request will retain their existing values. Args: event_id (str): Event identifier. start (str, optional): Event start time in ISO 8601 format (e.g., '2025-04-06T10:00:00-04:00'). Defaults to None. end (str, optional): Event end time in ISO 8601 format (e.g., '2025-04-06T11:00:00-04:00'). Defaults to None. timeZone (str, optional): User timezone formatted as an IANA Time Zone Database name (e.g. "Europe/Zurich"). Defaults to None. summary (str, optional): Short title or subject of the event. Defaults to None. description (str, optional): Detailed description or notes for the event. Defaults to None. location (str, optional): Physical or virtual location of the event. Defaults to None. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation on calendar events: listing, creating, deleting, and updating. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_events, create_event, delete_event, update_event. This provides a predictable and clear naming convention.
With only 4 tools, the server is tightly focused on core calendar event operations. The count is well within the ideal range and each tool serves a necessary purpose.
The server offers full CRUD coverage for events: create, read (list), update, and delete. A minor gap is the lack of a direct 'get event by ID' operation, but list_events with filters can work around this.