# How to integrate Google Calendar MCP with Claude Code

```json
{
  "title": "How to integrate Google Calendar MCP with Claude Code",
  "toolkit": "Google Calendar",
  "toolkit_slug": "googlecalendar",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/googlecalendar/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/googlecalendar/framework/claude-code.md",
  "updated_at": "2026-05-12T10:13:51.567Z"
}
```

## Introduction

Manage your Google Calendar directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Google Calendar with

- [ChatGPT](https://composio.dev/toolkits/googlecalendar/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/googlecalendar/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/googlecalendar/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/googlecalendar/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/googlecalendar/framework/codex)
- [Cursor](https://composio.dev/toolkits/googlecalendar/framework/cursor)
- [VS Code](https://composio.dev/toolkits/googlecalendar/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/googlecalendar/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/googlecalendar/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/googlecalendar/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/googlecalendar/framework/cli)
- [Google ADK](https://composio.dev/toolkits/googlecalendar/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/googlecalendar/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/googlecalendar/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/googlecalendar/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/googlecalendar/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/googlecalendar/framework/crew-ai)

## TL;DR

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Google Calendar to Claude Code

### Connecting Google Calendar to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## What is the Google Calendar MCP server, and what's possible with it?

The Google Calendar MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Calendar account. It provides structured and secure access to your calendars and events, so your agent can schedule meetings, create or modify events, list upcoming appointments, and manage calendars—all on your behalf.
- Automated event creation and scheduling: Easily instruct your agent to add new events, meetings, or reminders with specific times, attendees, and details.
- Event listing and agenda overview: Have your agent list all upcoming, past, or filtered events on any of your calendars to keep you on top of your schedule.
- Calendar management and customization: Direct your agent to create new calendars, update calendar details, or even insert calendars into your list for better organization.
- Event updating and deletion: Let your agent modify existing events or remove events that are no longer needed, keeping your calendar up to date.
- Complete calendar clearing: Ask your agent to clear all events from a primary calendar or delete secondary calendars entirely when you need a fresh start.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GOOGLECALENDAR_ACL_DELETE` | Delete ACL Rule | Deletes an access control rule from a Google Calendar. Use when you need to remove sharing permissions for a user, group, or domain. |
| `GOOGLECALENDAR_ACL_GET` | Get ACL Rule | Retrieves a specific access control rule for a calendar. Use when you need to check permissions for a specific user, group, or domain. |
| `GOOGLECALENDAR_ACL_INSERT` | Create ACL Rule | Creates an access control rule for a calendar. Use when you need to grant sharing permissions to a user, group, or domain. |
| `GOOGLECALENDAR_ACL_LIST` | List ACL Rules | Retrieves the list of access control rules (ACLs) for a specified calendar, providing the necessary 'rule_id' values required for updating specific ACL rules. |
| `GOOGLECALENDAR_ACL_PATCH` | Patch ACL Rule | Updates an existing access control rule for a calendar using patch semantics (partial update). This allows modifying specific fields without affecting other properties. IMPORTANT: The ACL rule must already exist on the calendar. This action cannot create new rules. If you receive a 404 Not Found error, the rule does not exist - use ACL insert to create it first, or use ACL list to verify available rules. Each patch request consumes three quota units. For domain-type ACL rules, if PATCH fails with 500 error, this action will automatically fallback to UPDATE method. |
| `GOOGLECALENDAR_ACL_UPDATE` | Update ACL Rule | Updates an access control rule for the specified calendar. |
| `GOOGLECALENDAR_ACL_WATCH` | Watch ACL Changes | Tool to watch for changes to ACL resources. Use when you need to set up real-time notifications for access control list modifications on a calendar. |
| `GOOGLECALENDAR_BATCH_EVENTS` | Batch Events | Execute up to 1000 event mutations (create/patch/delete) in one Google Calendar HTTP batch request with per-item status/results. Use this to materially reduce round-trips for bulk operations like migrations, cleanup, or large-scale updates. |
| `GOOGLECALENDAR_CALENDAR_LIST_DELETE` | Remove Calendar from List | Tool to remove a calendar from the user's calendar list. Use when you need to unsubscribe from or hide a calendar from the user's list. |
| `GOOGLECALENDAR_CALENDAR_LIST_GET` | Get Single Calendar by ID | Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar ID. This action requires a calendarId parameter and returns details about that one calendar only. NOTE: This does NOT list all calendars. To list all calendars in the user's calendar list, use GOOGLECALENDAR_CALENDAR_LIST_LIST instead. |
| `GOOGLECALENDAR_CALENDAR_LIST_INSERT` | Insert Calendar into List | Inserts an existing calendar into the user's calendar list, making it visible in the UI. Calendars (e.g., newly created ones) won't appear in the list or UI until explicitly inserted. |
| `GOOGLECALENDAR_CALENDAR_LIST_PATCH` | Patch Calendar List Entry | Updates an existing calendar on the user's calendar list using patch semantics. This method allows partial updates, modifying only the specified fields. |
| `GOOGLECALENDAR_CALENDAR_LIST_UPDATE` | Update Calendar List Entry | Updates a calendar list entry's display/subscription settings (color, visibility, reminders, selection) for the authenticated user — does not modify the underlying calendar resource (title, timezone, etc.). To modify the calendar itself, use GOOGLECALENDAR_CALENDARS_UPDATE. |
| `GOOGLECALENDAR_CALENDAR_LIST_WATCH` | Watch Calendar List | Watch for changes to CalendarList resources using push notifications. Use this to receive real-time updates when calendar list entries are modified. |
| `GOOGLECALENDAR_CALENDARS_DELETE` | Delete Calendar | Deletes a secondary calendar that you own or have delete permissions on. Deletion is permanent and irreversible — verify the correct calendar_id before calling. You cannot delete your primary calendar or calendars you only have read/write access to. Use calendarList.list to find calendars with owner accessRole. For primary calendars, use calendars.clear instead. Parallel calls may trigger userRateLimitExceeded; sequence bulk deletions. |
| `GOOGLECALENDAR_CALENDARS_UPDATE` | Update Calendar | Full PUT-style update that overwrites all calendar metadata fields; unspecified optional fields are cleared. Use GOOGLECALENDAR_PATCH_CALENDAR to update only a subset of fields. Mutates the underlying calendar resource (title, description, timeZone, etc.); use GOOGLECALENDAR_CALENDAR_LIST_UPDATE to change per-user display properties like color. |
| `GOOGLECALENDAR_CHANNELS_STOP` | Stop Channel | Tool to stop watching resources through a notification channel. Use when you need to discontinue push notifications for a specific channel subscription. |
| `GOOGLECALENDAR_CLEAR_CALENDAR` | Clear Calendar | Clears a primary calendar by deleting all events from it. The calendar itself is preserved; only its events are removed. Primary calendars cannot be deleted entirely. |
| `GOOGLECALENDAR_COLORS_GET` | Get Color Definitions | Returns the color definitions for calendars and events. Use when you need to retrieve the available color palette for styling calendars or events. |
| `GOOGLECALENDAR_CREATE_EVENT` | Create Event | Create a Google Calendar event using start_datetime plus duration fields. The organizer is added as an attendee unless exclude_organizer is True. By default adds Google Meet link (works for Workspace, gracefully falls back for personal Gmail). Attendees can be email strings (required) or objects with email and optional fields. No conflict checking is performed; use GOOGLECALENDAR_FREE_BUSY_QUERY to detect overlaps before creating. Returns event id and htmlLink nested under data.response_data. Example: { "start_datetime": "2025-01-16T13:00:00", "timezone": "America/New_York", "event_duration_hour": 1, "event_duration_minutes": 30, "summary": "Client sync", "attendees": ["required@example.com", {"email": "optional@example.com", "optional": true}] } |
| `GOOGLECALENDAR_DELETE_EVENT` | Delete event | Deletes a specified event by `event_id` from a Google Calendar (`calendar_id`); idempotent — a 404 for an already-deleted event is a no-op. Bulk deletions may trigger `rateLimitExceeded` or `userRateLimitExceeded`; cap concurrency to 5–10 requests and apply exponential backoff. |
| `GOOGLECALENDAR_DUPLICATE_CALENDAR` | Create a calendar | Creates a new, empty Google Calendar with the specified title (summary). Newly created calendars default to UTC timezone; use GOOGLECALENDAR_PATCH_CALENDAR afterward to set the desired timeZone if needed. |
| `GOOGLECALENDAR_EVENTS_GET` | Get Event | Retrieves a SINGLE event by its unique event_id (REQUIRED). This action does NOT list or search events - it fetches ONE specific event when you already know its ID. If you want to list events within a time range, search for events, or filter by criteria like time_min/time_max, use GOOGLECALENDAR_EVENTS_LIST instead. |
| `GOOGLECALENDAR_EVENTS_IMPORT` | Import Event | Tool to import an event as a private copy to a calendar. Use when you need to add an existing event to a calendar using its iCalUID. Only events with eventType='default' can be imported. |
| `GOOGLECALENDAR_EVENTS_INSTANCES` | Get Event Instances | Returns instances of the specified recurring event. Use timeMin/timeMax to constrain the window; omitting bounds can return large result sets and is quota-heavy. On high-volume calls, 403 rateLimitExceeded or 429 too_many_requests may occur; apply exponential backoff (1s, 2s, 4s) before retrying. |
| `GOOGLECALENDAR_EVENTS_LIST` | List Events | Returns events on the specified calendar. TIMEZONE WARNING: When using timeMin/timeMax with UTC timestamps (ending in 'Z'), the time window is interpreted in UTC regardless of the calendar's timezone. For example, querying '2026-01-19T00:00:00Z' to '2026-01-20T00:00:00Z' on a calendar in America/Los_Angeles (UTC-8) covers 2026-01-18 4pm to 2026-01-19 4pm local time, potentially missing events on the intended local date. To query for a specific local date, use timestamps with the appropriate timezone offset in timeMin/timeMax (e.g., '2026-01-19T00:00:00-08:00' for PST). |
| `GOOGLECALENDAR_EVENTS_LIST_ALL_CALENDARS` | List Events from All Calendars | Return a unified event list across all calendars in the user's calendar list for a given time range. Use when you need a single view of all events across multiple calendars. An inverted or incorrect time range silently returns empty results rather than an error. An empty `items` list means no events matched the filters—adjust `time_min`, `time_max`, or `q` before concluding no events exist. |
| `GOOGLECALENDAR_EVENTS_MOVE` | Move Event | Moves an event to another calendar, i.e., changes an event's organizer. |
| `GOOGLECALENDAR_EVENTS_WATCH` | Watch Events | Watch for changes to Events resources. Watch channels expire; persist the channel `id` per `calendarId` to re-establish watches after expiration or restarts. |
| `GOOGLECALENDAR_FIND_EVENT` | Find event | Finds events in a specified Google Calendar using text query, time ranges (event start/end, last modification), and event types. Ensure `timeMin` is not chronologically after `timeMax` if both are provided. Results may span multiple pages; always follow `nextPageToken` until absent to avoid silently missing events. Validate the correct match from results by checking summary, start.dateTime, and organizer.email before using event_id for mutations. An empty `items` array means no events matched — widen filters rather than treating it as an error. |
| `GOOGLECALENDAR_FIND_FREE_SLOTS` | Find free slots | Finds both free and busy time slots in Google Calendars for specified calendars within a defined time range. If `time_min` is not provided, defaults to the current timestamp in the specified timezone. If `time_max` is not provided, defaults to 23:59:59 of the day specified in `time_min` (if provided), otherwise defaults to 23:59:59 of the current day in the specified timezone. Returns busy intervals and calculates free slots by finding gaps between busy periods; `time_min` must precede `time_max` if both are provided. This action retrieves free and busy time slots for the specified calendars over a given time period. It analyzes the busy intervals from the calendars and provides calculated free slots based on the gaps in the busy periods. Returned free slots are unfiltered by duration; callers must filter intervals to those fully containing the required meeting length. No event metadata (titles, descriptions, links) is returned; use GOOGLECALENDAR_EVENTS_LIST for event details. |
| `GOOGLECALENDAR_GET_CALENDAR` | Get Google Calendar | Retrieves a specific Google Calendar, identified by `calendar_id`, to which the authenticated user has access. Response includes `timeZone` (IANA format, e.g., 'America/Los_Angeles') — use it directly when constructing `timeMin`/`timeMax` in other tools to avoid DST errors. An empty `defaultReminders` list is valid (no defaults configured). Insufficient `accessRole` may omit fields like `defaultReminders` and `colorId`. |
| `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` | Get current date and time | Gets the current date and time, allowing for a specific timezone offset. Call this tool first before computing relative dates (e.g., 'tomorrow', 'next Monday') to avoid off-by-one-day errors across timezones. |
| `GOOGLECALENDAR_LIST_BUILDINGS` | List Buildings | Lists all buildings for a Google Workspace customer account with full details including addresses, coordinates, and floor names. Use this action when you need to retrieve the complete list of physical building locations configured in Google Workspace Calendar resources. This is useful for workspace administrators managing conference room and resource scheduling across multiple office buildings. Requires Google Workspace administrator privileges with Directory API access. |
| `GOOGLECALENDAR_LIST_CALENDAR_RESOURCES` | List Calendar Resources | Retrieves calendar resources (such as conference rooms) from a Google Workspace domain using the Admin SDK Directory API. Use this action when you need to list available meeting rooms, conference spaces, or other bookable calendar resources in an organization. The action supports filtering by resource category, capacity, building location, and other criteria. IMPORTANT: This requires Admin SDK Directory API access and appropriate admin permissions - it is NOT available for personal Gmail accounts, only Google Workspace domains. |
| `GOOGLECALENDAR_LIST_CALENDARS` | List Google Calendars | Retrieves calendars from the user's Google Calendar list, with options for pagination and filtering. Loop through all pages using nextPageToken until absent to avoid missing calendars. Use the primary flag and accessRole field from the response to identify calendars — display names are not valid calendar_id values. Read access (listing) does not imply write OAuth scopes. |
| `GOOGLECALENDAR_PATCH_CALENDAR` | Patch Calendar | Partially updates (PATCHes) an existing Google Calendar, modifying only the fields provided. At least one of summary, description, location, or timezone must be provided. Empty strings for `description` or `location` clear them. |
| `GOOGLECALENDAR_PATCH_EVENT` | Patch Event | Update specified fields of an existing event in a Google Calendar using patch semantics (array fields like `attendees` are fully replaced if provided); ensure the `calendar_id` and `event_id` are valid and the user has write access to the calendar. |
| `GOOGLECALENDAR_QUICK_ADD` | Quick Add Event | Parses natural language text to quickly create a basic Google Calendar event with its title, date, and time, suitable for simple scheduling; does not support direct attendee addition or recurring events, and `calendar_id` must be valid if not 'primary'. |
| `GOOGLECALENDAR_REMOVE_ATTENDEE` | Remove attendee from event | Removes an attendee from a specified event in a Google Calendar; the calendar and event must exist. Concurrent calls on the same event can overwrite attendee lists — apply changes sequentially per event. |
| `GOOGLECALENDAR_SETTINGS_GET` | Get Calendar Setting | Tool to return a single user setting for the authenticated user. Use when you need to retrieve a specific calendar setting value. |
| `GOOGLECALENDAR_SETTINGS_LIST` | List Settings | Returns all user settings for the authenticated user. Results include multiple settings keyed by id (e.g., `timeZone`); locate a specific setting by its `id` field. `timeZone` values are IANA identifiers (e.g., `America/New_York`) — use directly in datetime and event logic; align with `timeZone` from GOOGLECALENDAR_GET_CALENDAR for consistent notification times. |
| `GOOGLECALENDAR_SETTINGS_WATCH` | Watch Settings | Watch for changes to Settings resources. |
| `GOOGLECALENDAR_UPDATE_EVENT` | Update Google event | Updates an existing event in Google Calendar. REQUIRES event_id - you MUST first search for the event using GOOGLECALENDAR_FIND_EVENT or GOOGLECALENDAR_EVENTS_LIST to obtain the event_id. This is a full PUT replacement: omitted fields (including attendees, reminders, recurrence, conferencing) are cleared. Always provide the complete desired event state. Use GOOGLECALENDAR_PATCH_EVENT instead for partial edits. |

## Supported Triggers

| Trigger slug | Name | Description |
|---|---|---|
| `GOOGLECALENDAR_ATTENDEE_RESPONSE_CHANGED_TRIGGER` | Attendee Response Changed | Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status. |
| `GOOGLECALENDAR_EVENT_CANCELED_DELETED_TRIGGER` | Event Canceled or Deleted | Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp. |
| `GOOGLECALENDAR_EVENT_STARTING_SOON_TRIGGER` | Event Starting Soon | Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available. |
| `GOOGLECALENDAR_GOOGLE_CALENDAR_EVENT_CHANGE_TRIGGER` | Calendar Event Changes | **SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger). |
| `GOOGLECALENDAR_GOOGLE_CALENDAR_EVENT_CREATED_TRIGGER` | Event Created | Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info. |
| `GOOGLECALENDAR_GOOGLE_CALENDAR_EVENT_SYNC_TRIGGER` | Calendar Event Sync | Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook). |
| `GOOGLECALENDAR_GOOGLE_CALENDAR_EVENT_UPDATED_TRIGGER` | Event Updated | Triggers when an existing Google Calendar event is modified. Returns the event ID, change type, and the specific fields that changed with their previous and new values. |

## Creating MCP Server - Stand-alone vs Composio SDK

The Google Calendar MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Google Calendar account. It provides structured and secure access so Claude can perform Google Calendar operations on your behalf.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Google Calendar account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["googlecalendar"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http googlecalendar-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googlecalendar'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googlecalendar-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Google Calendar MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (googlecalendar-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http googlecalendar-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Google Calendar MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your googlecalendar-composio entry in the list
- This confirms that Claude Code can now access Google Calendar tools
If everything is wired up, you should see your googlecalendar-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Google Calendar

The first time you try to use Google Calendar tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Google Calendar
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Google Calendar authorization flow
- Return to the terminal and start using Google Calendar through Claude Code
Once authenticated, you can ask Claude Code to perform Google Calendar operations in natural language. For example:
- "Create a meeting with the marketing team"
- "List all events scheduled for next week"
- "Delete tomorrow’s canceled event from my calendar"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["googlecalendar"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http googlecalendar-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googlecalendar'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googlecalendar-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Google Calendar with Claude Code using Composio's MCP server. Now you can interact with Google Calendar directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Google Calendar operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Google Calendar operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Google Calendar MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/googlecalendar/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/googlecalendar/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/googlecalendar/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/googlecalendar/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/googlecalendar/framework/codex)
- [Cursor](https://composio.dev/toolkits/googlecalendar/framework/cursor)
- [VS Code](https://composio.dev/toolkits/googlecalendar/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/googlecalendar/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/googlecalendar/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/googlecalendar/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/googlecalendar/framework/cli)
- [Google ADK](https://composio.dev/toolkits/googlecalendar/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/googlecalendar/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/googlecalendar/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/googlecalendar/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/googlecalendar/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/googlecalendar/framework/crew-ai)

## Related Toolkits

- [Apaleo](https://composio.dev/toolkits/apaleo) - Apaleo is a cloud-based property management platform for hospitality businesses. It centralizes reservations, billing, and daily operations for smoother hotel management.
- [Appointo](https://composio.dev/toolkits/appointo) - Appointo is an appointment booking platform for Shopify stores. It lets businesses add online scheduling to their websites with zero coding.
- [Bart](https://composio.dev/toolkits/bart) - Bart is the Bay Area Rapid Transit system, providing fast public transportation across the San Francisco Bay Area. It helps commuters and travelers get real-time schedule info, plan routes, and stay updated on service changes.
- [Bookingmood](https://composio.dev/toolkits/bookingmood) - Bookingmood is commission-free booking software for rental businesses. It lets you manage reservations and sync bookings directly on your website.
- [Booqable](https://composio.dev/toolkits/booqable) - Booqable is a rental software platform for managing inventory, bookings, and reservations. It helps businesses streamline rentals and keep track of every item with ease.
- [Cal](https://composio.dev/toolkits/cal) - Cal is a meeting scheduling platform that offers shareable booking links and real-time calendar syncing. It streamlines the process of finding mutual availability to make scheduling effortless.
- [Calendarhero](https://composio.dev/toolkits/calendarhero) - Calendarhero is a powerful scheduling platform that streamlines your calendar management across multiple services. It helps you efficiently schedule, reschedule, and organize meetings without the back-and-forth.
- [Calendly](https://composio.dev/toolkits/calendly) - Calendly is an appointment scheduling tool that automates meeting invitations, availability checks, and reminders. It helps individuals and teams avoid endless email back-and-forth when booking meetings.
- [Etermin](https://composio.dev/toolkits/etermin) - eTermin is an online appointment scheduling platform for businesses to manage bookings. It streamlines client appointments, saving time and reducing scheduling conflicts.
- [Evenium](https://composio.dev/toolkits/evenium) - Evenium is an all-in-one platform for managing professional events, from planning to analysis. It helps teams simplify event logistics, boost engagement, and track every detail in one place.
- [Eventee](https://composio.dev/toolkits/eventee) - Eventee is a user-friendly event management platform for mobile and web. It boosts attendee engagement for in-person, virtual, and hybrid events.
- [Eventzilla](https://composio.dev/toolkits/eventzilla) - Eventzilla is an event management platform for creating, promoting, and running events. It streamlines ticketing, registration, and attendee coordination for organizers.
- [Humanitix](https://composio.dev/toolkits/humanitix) - Humanitix is a not-for-profit ticketing platform that donates 100% of profits to charity. It empowers event organizers to make social impact with every ticket sold.
- [Lodgify](https://composio.dev/toolkits/lodgify) - Lodgify is an all-in-one vacation rental software for property managers and owners. It centralizes bookings, guest messaging, and channel synchronization in one dashboard.
- [Planyo Online Booking](https://composio.dev/toolkits/planyo_online_booking) - Planyo Online Booking is a flexible reservation system for managing bookings by day, hour, or event. It streamlines scheduling for any business needing reservations.
- [Scheduleonce](https://composio.dev/toolkits/scheduleonce) - Scheduleonce is a scheduling platform for capturing, qualifying, and engaging with inbound leads. It streamlines appointment booking and follow-ups for faster lead conversion.
- [Supersaas](https://composio.dev/toolkits/supersaas) - Supersaas is a flexible appointment scheduling platform for businesses and individuals. It streamlines bookings, reminders, and calendar management in one place.
- [Sympla](https://composio.dev/toolkits/sympla) - Sympla is a platform for managing in-person and online events, ticket sales, and registrations. It streamlines event setup, attendee tracking, and digital content delivery.
- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Google Calendar MCP?

With a standalone Google Calendar MCP server, the agents and LLMs can only access a fixed set of Google Calendar tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Calendar and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Claude Code?

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google Calendar tools.

### Can I manage the permissions and scopes for Google Calendar while using Tool Router?

Yes, absolutely. You can configure which Google Calendar scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google Calendar data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)