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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_eventsC | List events from a Google Calendar |
| create_eventC | Create a new event in Google Calendar |
| update_eventC | Update an existing event in Google Calendar |
| delete_eventC | Delete an event from Google Calendar |
| list_calendarsB | List available Google Calendars |
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 5 tools
Every tool has a clearly distinct purpose with no ambiguity. create_event, update_event, and delete_event handle the event lifecycle, while list_calendars and list_events provide listing functionality for different resources. The descriptions clearly differentiate each tool's role.
All tools follow a consistent verb_noun pattern (e.g., create_event, list_calendars). The naming is uniform throughout with no deviations in style or convention, making it easy to predict and understand tool purposes.
With 5 tools, this server is well-scoped for Google Calendar operations. Each tool earns its place by covering essential CRUD and listing functions without being overly sparse or bloated, fitting typical server tool counts.
The tool surface provides complete CRUD/lifecycle coverage for events (create, read via list, update, delete) and includes listing calendars. There are no obvious gaps for core calendar operations, ensuring agents can handle common workflows without dead ends.