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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_upcoming_eventsA | Get upcoming calendar events. Args: max_results: Maximum number of events to return (default: 10) calendar_id: Calendar ID to query (default: "primary") Returns: Formatted list of upcoming events with start time and title |
| get_events_for_dateA | Get calendar events for a specific date. Args: date: Date in YYYY-MM-DD format calendar_id: Calendar ID to query (default: "primary") Returns: Formatted list of events for that date |
| search_eventsA | Search calendar events by keyword. Args: query: Search term to find in event titles/descriptions max_results: Maximum number of events to return (default: 10) calendar_id: Calendar ID to query (default: "primary") Returns: Matching events with start time and title |
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 3 tools
The three tools have clearly distinct purposes: retrieving events for a specific date, listing upcoming events, and searching by keyword. Some overlap exists (e.g., upcoming events could be retrieved by date), but the descriptions differentiate them well.
All tool names follow a consistent verb_noun pattern with snake_case: get_events_for_date, get_upcoming_events, search_events. The pattern is predictable and easy to understand.
With only 3 tools, the server feels under-scoped for a calendar service. Most calendar servers provide create, update, delete, and calendar management operations, which are missing here.
The server only covers read/query operations (get, list, search). It lacks any write operations (create, update, delete events) or calendar management, leaving significant gaps for common workflows.