Google Calendar MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_SCOPES | No | Google API scopes required for Calendar access | https://www.googleapis.com/auth/calendar |
| GOOGLE_CLIENT_SECRET_FILE | No | Path to the Google OAuth client secret JSON file | client_secret.json |
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_month_eventsC | 지정한 연/월의 모든 일정 목록 조회 |
| list_day_eventsC | 지정한 날짜(YYYY-MM-DD)의 모든 일정 목록 조회 |
| get_event_detailC | 일정 ID로 상세 정보 조회 |
| create_eventC | 새로운 일정 생성 (attendees: 이메일 리스트) |
| update_eventB | 일정 ID로 일정 정보 수정 (전달된 값만 반영) |
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
Each tool has a clearly distinct purpose with no ambiguity: create_event, get_event_detail, list_day_events, list_month_events, and update_event target specific actions on calendar events. The descriptions clarify their unique scopes, such as day vs. month listing, preventing misselection.
All tool names follow a consistent verb_noun pattern (e.g., create_event, get_event_detail, list_day_events). There are no deviations in style or convention, making the set predictable and readable for agents.
With 5 tools, the count is well-scoped for a Google Calendar server, covering core operations like CRUD and listing. It's slightly lean but reasonable, as each tool earns its place without feeling thin or excessive for the domain.
The tool surface provides strong coverage for event management, including create, read (get and list), and update operations. A minor gap is the lack of a delete_event tool, which agents might need to work around, but core workflows are well-supported.