How to integrate Google Calendar MCP with CrewAI

This guide walks you through connecting Google Calendar to CrewAI using the Composio tool router. By the end, you'll have a working Google Calendar agent that can create a meeting with the marketing team, list all events scheduled for next week, delete tomorrow’s canceled event from your calendar through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Google Calendar account through Composio's Google Calendar MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
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

This guide walks you through connecting Google Calendar to CrewAI using the Composio tool router. By the end, you'll have a working Google Calendar agent that can create a meeting with the marketing team, list all events scheduled for next week, delete tomorrow’s canceled event from your calendar through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Google Calendar account through Composio's Google Calendar MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Google Calendar with

ChatGPTOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndex

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Google Calendar connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Google Calendar
  • Build a conversational loop where your agent can execute Google Calendar operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

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 step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Google Calendar connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Google Calendar via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

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

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Google Calendar MCP URL
6

Create a Composio Tool Router session for Google Calendar

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["googlecalendar"])

url = session.mcp.url
What's happening:
  • You create a Google Calendar only session through Composio
  • Composio returns an MCP HTTP URL that exposes Google Calendar tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

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

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["googlecalendar"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Google Calendar through Composio's Tool Router. The agent can perform Google Calendar operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
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.

FRAMEWORKS

How to build Google Calendar MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Google Calendar MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Google Calendar MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Google Calendar MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Google Calendar MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Google Calendar MCP with Claude Cowork

Codex logo

Codex

Use Google Calendar MCP with Codex

Cursor logo

Cursor

Use Google Calendar MCP with Cursor

OpenClaw logo

OpenClaw

Use Google Calendar MCP with OpenClaw

Hermes logo

Hermes

Use Google Calendar MCP with Hermes

CLI logo

CLI

Use Google Calendar MCP with CLI

Google ADK logo

Google ADK

Use Google Calendar MCP with Google ADK

LangChain logo

LangChain

Use Google Calendar MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Google Calendar MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Google Calendar MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Google Calendar MCP with LlamaIndex

OpenCode logo

OpenCode

Use Google Calendar MCP with OpenCode

VS Code logo

VS Code

Use Google Calendar MCP with VS Code

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. CrewAI 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
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies