MCP Google Calendar Integration
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALENDAR_ID | Yes | Your calendar ID or email | |
| GOOGLE_API_KEY | Yes | Your Google Calendar API key |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getMyCalendarDataByDateD | – |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool stands alone without any competing or confusing alternatives.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming pattern cannot be inconsistent when only one exists.
A single tool for a Google Calendar integration is too few for the apparent scope. Calendar integrations typically require multiple operations like creating, updating, deleting events, and listing calendars, making this server severely under-equipped.
The tool surface is severely incomplete for a Google Calendar domain. With only a date-based data retrieval tool, there are obvious gaps in CRUD operations, event management, and other essential calendar functionalities, which will cause agent failures.