Google Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALENDAR_ID | Yes | Your target Google Calendar ID | |
| GOOGLE_PUBLIC_API_KEY | Yes | Your Google API key with Calendar API enabled |
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
Server capabilities have not been inspected yet.
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 confusion or overlap between tools. The single tool stands alone with no ambiguity about its purpose relative to other tools in the set.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns or conventions. The naming stands alone without any inconsistency issues.
A single tool for a Google Calendar server is too few for the apparent scope, as calendar operations typically require multiple actions like creating, updating, deleting events, and listing calendars. This minimal set will likely cause agent failures due to lack of functionality.
The tool set is severely incomplete for a calendar domain, missing essential CRUD operations for events and calendars. With only a single data retrieval tool, agents cannot perform basic calendar management tasks, leading to significant gaps in coverage.