Google Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | Yes | Your Google OAuth2 Client ID | |
| GOOGLE_CLIENT_SECRET | Yes | Your Google OAuth2 Client Secret | |
| GOOGLE_REFRESH_TOKEN | Yes | Your Google OAuth2 Refresh Token |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_eventC | Create a calendar event with specified details |
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 tool's purpose is singular and clear.
The single tool follows a clear verb_noun pattern (create_event), and with no other tools to compare, consistency is inherently perfect.
One tool is too few for a Google Calendar server, as it lacks essential operations like listing, updating, or deleting events, making it severely limited for typical calendar management tasks.
The tool set is severely incomplete; it only allows event creation without any way to view, modify, or manage existing events, leaving major gaps in calendar functionality.