google-calendar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKEN_PATH | Yes | Path to store/load the OAuth2 token JSON file | |
| CLIENT_SECRET_PATH | Yes | Path to the client_secret.json file from Google Cloud Console |
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 |
|---|---|
| list_calendarsA | ユーザーがアクセス可能なカレンダーの一覧を取得します |
| get_calendarA | 指定したカレンダーの詳細情報を取得します |
| list_eventsB | 指定した期間のカレンダーイベント一覧を取得します |
| get_eventA | 特定のイベントの詳細情報を取得します |
| search_eventsC | キーワードでイベントを検索します |
| create_eventA | 新しいカレンダーイベントを作成します。定期イベントの作成も可能です |
| update_eventB | 既存のカレンダーイベントを更新します |
| delete_eventB | カレンダーイベントを削除します |
| update_recurring_eventA | 定期イベント（繰り返しイベント）を更新します。「この予定のみ」「すべての予定」「これ以降の予定」の3つの編集スコープをサポートします |
| delete_recurring_instanceA | 定期イベントの特定のインスタンス（1回分）のみを削除します |
| get_freebusyA | 指定した期間の空き時間情報を取得します。複数のカレンダーの予定が埋まっている時間帯を確認できます |
| list_colorsA | カレンダーとイベントで使用可能なカラーパレットを取得します |
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 12 tools
Each tool targets a distinct resource and action: calendars vs. events, list vs. get vs. search, and specific recurring-event tools are clearly separated from regular event tools. Descriptions further clarify any potential overlap, such as delete_recurring_instance versus delete_event.
All tool names follow a consistent verb_noun pattern (list_, get_, search_, create_, update_, delete_), using snake_case throughout. Compound names like update_recurring_event and delete_recurring_instance are logical extensions of the pattern.
12 tools is well within the ideal 3-15 range for a calendar server. Each tool addresses a meaningful aspect of calendar and event management without unnecessary redundancy or bloat.
The set provides comprehensive event CRUD, recurring event handling, free/busy lookup, and color details. Minor gaps include no ability to create/delete calendars (only list and get), but the core calendar workflow is well covered.