GoogleCalendarMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALENDAR_ID | Yes | Your Google Calendar ID (typically your Gmail address for your primary calendar) | |
| GOOGLE_PUBLIC_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
Only one tool exists, so there is no risk of confusing between tools.
With a single tool, naming consistency is inherently maintained.
A Google Calendar server with only one tool is too few for its apparent scope, failing to cover basic operations.
The tool has no description and likely only fetches data by date, missing essential CRUD operations for a calendar service.