Google Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANGO_CONNECTION_ID | Yes | The connection ID created when a user connects their Google account | |
| NANGO_INTEGRATION_ID | Yes | The ID of your Google Calendar integration in Nango | |
| NANGO_NANGO_BASE_URL | No | The base URL for the Nango API | https://api.nango.dev |
| NANGO_NANGO_SECRET_KEY | Yes | Your Nango secret key, found in your Nango project settings |
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 |
|---|---|
| get_all_calendarsB | Get all Google Calendars accessible to the user |
| get_calendar_eventsB | Get events from a specific Google Calendar Args: calendar_id: Calendar ID (default: primary) time_min: Lower bound for event start time (ISO format) time_max: Upper bound for event start time (ISO format) max_results: Maximum number of events to return (default: 10) |
| create_meet_eventB | Create a new Google Calendar event with Google Meet integration Args: summary: Event title/summary start_datetime: Start datetime in ISO format (e.g., '2024-12-25T10:00:00') end_datetime: End datetime in ISO format (e.g., '2024-12-25T11:00:00') description: Event description attendees: List of attendee emails timezone: Timezone (default: UTC) calendar_id: Calendar ID (default: primary) |
| cancel_calendar_eventB | Cancel (delete) a specific event from Google Calendar Args: calendar_id: Calendar ID where the event exists event_id: The unique identifier of the event to cancel |
| get_today_eventsC | Get today's events from the primary calendar Args: calendar_id: Calendar ID (default: primary) |
| get_upcoming_eventsB | Get upcoming events for the next N days Args: days_ahead: Number of days to look ahead (default: 7) calendar_id: Calendar ID (default: primary) |
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 6 tools
Most tools have distinct purposes, but get_calendar_events, get_today_events, and get_upcoming_events overlap significantly in functionality. An agent might struggle to choose between them for general event retrieval, though their specific scopes (today, upcoming, custom time range) provide some differentiation in descriptions.
All tools follow a consistent verb_noun pattern with snake_case naming (e.g., cancel_calendar_event, create_meet_event, get_all_calendars). The naming is predictable and readable throughout the set.
With 6 tools, the count is reasonable for a calendar server, but it feels slightly thin. Core operations like updating events or managing calendar settings are missing, which could justify a few more tools to cover the domain more completely.
The server covers basic CRUD operations (create and cancel events, get events and calendars), but lacks update functionality for events, which is a notable gap. There are also no tools for managing calendar properties (e.g., create/delete calendars, update event attendees), limiting agent workflows.