How to integrate Google Calendar MCP with Claude Code

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 - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Google Calendar logoGoogle Calendar
Oauth2

Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.

44 Tools7 Triggers

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:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Google Calendar with

Why use Composio?

  • 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.

Connecting Google Calendar to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Google Calendar via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Google Calendar) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
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
2

Install Claude Code

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

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

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
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

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}"`);

Create a script to generate a Composio MCP URL for Google Calendar. This URL will be used to connect Claude Code to Google Calendar.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Google Calendar
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

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

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Google Calendar MCP to Claude Code

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

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.

9

Verify the installation

bash
claude mcp list

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:

Claude Code MCP list showing the toolkit MCP server
10

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

Here's the complete code to get you started with Google Calendar and Claude Code:

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.

TOOLS & TRIGGERS

Supported Tools and Triggers

Every Google Calendar action and event your agent gets out of the box.

Delete ACL Rule

Deletes an access control rule from a Google Calendar.

Get ACL Rule

Retrieves a specific access control rule for a calendar.

Create ACL Rule

Creates an access control rule for a calendar.

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.

Patch ACL Rule

Updates an existing access control rule for a calendar using patch semantics (partial update).

Update ACL Rule

Updates an access control rule for the specified calendar.

Watch ACL Changes

Tool to watch for changes to ACL resources.

Batch Events

Execute up to 1000 event mutations (create/patch/delete) in one Google Calendar HTTP batch request with per-item status/results.

Remove Calendar from List

Tool to remove a calendar from the user's calendar list.

Get Single Calendar by ID

Retrieves metadata for a SINGLE specific calendar from the user's calendar list by its calendar ID.

Insert Calendar into List

Inserts an existing calendar into the user's calendar list, making it visible in the UI.

Patch Calendar List Entry

Updates an existing calendar on the user's calendar list using patch semantics.

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.

Watch Calendar List

Watch for changes to CalendarList resources using push notifications.

Delete Calendar

Deletes a secondary calendar that you own or have delete permissions on.

Update Calendar

Full PUT-style update that overwrites all calendar metadata fields; unspecified optional fields are cleared.

Stop Channel

Tool to stop watching resources through a notification channel.

Clear Calendar

Clears a primary calendar by deleting all events from it.

Get Color Definitions

Returns the color definitions for calendars and events.

Create Event

Create a Google Calendar event using start_datetime plus duration fields.

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.

Create a calendar

Creates a new, empty Google Calendar with the specified title (summary).

Get Event

Retrieves a SINGLE event by its unique event_id (REQUIRED).

Import Event

Tool to import an event as a private copy to a calendar.

Get Event Instances

Returns instances of the specified recurring event.

List Events

Returns events on the specified calendar.

List Events from All Calendars

Return a unified event list across all calendars in the user's calendar list for a given time range.

Move Event

Moves an event to another calendar, i.

Watch Events

Watch for changes to Events resources.

Find event

Finds events in a specified Google Calendar using text query, time ranges (event start/end, last modification), and event types.

Find free slots

Finds both free and busy time slots in Google Calendars for specified calendars within a defined time range.

Get Google Calendar

Retrieves a specific Google Calendar, identified by `calendar_id`, to which the authenticated user has access.

Get current date and time

Gets the current date and time, allowing for a specific timezone offset.

List Buildings

Lists all buildings for a Google Workspace customer account with full details including addresses, coordinates, and floor names.

List Calendar Resources

Retrieves calendar resources (such as conference rooms) from a Google Workspace domain using the Admin SDK Directory API.

List Google Calendars

Retrieves calendars from the user's Google Calendar list, with options for pagination and filtering.

Patch Calendar

Partially updates (PATCHes) an existing Google Calendar, modifying only the fields provided.

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.

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'.

Remove attendee from event

Removes an attendee from a specified event in a Google Calendar; the calendar and event must exist.

Get Calendar Setting

Tool to return a single user setting for the authenticated user.

List Settings

Returns all user settings for the authenticated user.

Watch Settings

Watch for changes to Settings resources.

Update Google event

Updates an existing event in Google Calendar.

FAQ

Frequently asked questions

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.

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.

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.

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.

Start with Google Calendar.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Calendar tool your agent needs.Free to start.

Start building