How to integrate Google Tasks MCP with CrewAI

This guide walks you through connecting Google Tasks to CrewAI using the Composio tool router. By the end, you'll have a working Google Tasks agent that can add a new task to your work list, list all tasks due this week, delete completed tasks from your shopping list through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Google Tasks account through Composio's Google Tasks MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Google Tasks

Oauth2

Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.

16 Tools5 Triggers

Managed auth

Connect Google Tasks without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

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

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

Also integrate Google Tasks with

ChatGPT OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenCode Cursor VS Code OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex

TL;DR

Here's what you'll learn:

Get a Composio API key and configure your Google Tasks connection
Set up CrewAI with an MCP enabled agent
Create a Tool Router session or standalone MCP server for Google Tasks
Build a conversational loop where your agent can execute Google Tasks 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 Tasks MCP server, and what's possible with it?

The Google Tasks 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 Tasks account. It provides structured and secure access to your to-do lists and tasks, so your agent can create task lists, add or update tasks, reorganize and clean up your lists, and fetch or manage your action items automatically.

Intelligent task list management: Ask your agent to create new to-do lists, fetch existing ones, or remove lists you no longer need—all without manual clicks.
Automated task creation and updates: Let your agent add new tasks, set due dates, or update existing to-dos to keep your lists current and organized.
Efficient task organization and movement: Move tasks between lists, reorder them, or set parent/child relationships so your priorities always stay clear.
Fast cleanup and deletion: Direct your agent to clear completed tasks or delete specific items and lists, helping you declutter swiftly and securely.
Detailed task retrieval and review: Have your agent pull details on any task or list so you can review upcoming deadlines, notes, and status at a glance.

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:

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

Step-by-step Guide

Step by step08 STEPS

Prerequisites

Before starting, make sure you have:

Python 3.9 or higher
A Composio account and API key
A Google Tasks connection authorized in Composio
An OpenAI API key for the CrewAI LLM
Basic familiarity with Python

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.

Install dependencies

bash

pip install composio crewai crewai-tools[mcp] python-dotenv

What's happening:

composio connects your agent to Google Tasks via MCP
crewai provides Agent, Task, Crew, and LLM primitives
crewai-tools[mcp] includes MCP helpers
python-dotenv loads environment variables from .env

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

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 Tasks MCP URL

Create a Composio Tool Router session for Google Tasks

python

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

url = session.mcp.url

What's happening:

You create a Google Tasks only session through Composio
Composio returns an MCP HTTP URL that exposes Google Tasks tools

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.

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 Tasks 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=["googletasks"],
)
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 Tasks through Composio's Tool Router. The agent can perform Google Tasks 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 Tasks action and event your agent gets out of the box.

Batch Execute Google Tasks Operations

Executes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results.

Clear tasks

Permanently and irreversibly clears all completed tasks from a specified Google Tasks list; this action is destructive, idempotent, and cannot be undone.

Create a task list

Creates a new task list with the specified title and returns a tasklist_id.

Delete task

Deletes a specified task from a Google Tasks list.

Delete task list

Permanently deletes an existing Google Task list, identified by `tasklist_id`, along with all its tasks; this operation is irreversible.

Get Task

Retrieve a specific Google Task.

Get task list

Retrieves a specific task list from the user's Google Tasks if the `tasklist_id` exists for the authenticated user.

Insert Task

Creates a new task in a given `tasklist_id`, optionally as a subtask of an existing `task_parent` or positioned after an existing `task_previous` sibling, where both `task_parent` and `task_previous` must belong to the same `tasklist_id` if specified.

List All Tasks Across All Lists

Tool to list all tasks across all of the user's task lists with optional filters.

List task lists

Fetches the authenticated user's task lists from Google Tasks; results may be paginated.

List Tasks

Retrieves tasks from a Google Tasks list; all date/time strings must be RFC3339 UTC, and `showCompleted` must be true if `completedMin` or `completedMax` are specified.

Move Task

Moves the specified task to another position in the task list or to a different task list.

Patch Task

Partially updates an existing task (identified by `task_id`) within a specific Google Task list (identified by `tasklist_id`), modifying only the provided attributes from `TaskInput` (e.

Patch task list

Updates the title of an existing Google Tasks task list.

Update Task (Full Replacement)

Tool to fully replace an existing Google Task using PUT method.

Update Task List

Updates the authenticated user's specified task list.

FRAMEWORKS

How to build Google Tasks MCP Agent with another framework

ChatGPT

Use Google Tasks MCP with ChatGPT

OpenAI Agents SDK

Use Google Tasks MCP with OpenAI Agents SDK

Claude Agent SDK

Use Google Tasks MCP with Claude Agent SDK

Claude Code

Use Google Tasks MCP with Claude Code

Claude Cowork

Use Google Tasks MCP with Claude Cowork

Codex

Use Google Tasks MCP with Codex

Cursor

Use Google Tasks MCP with Cursor

OpenClaw

Use Google Tasks MCP with OpenClaw

Hermes

Use Google Tasks MCP with Hermes

CLI

Use Google Tasks MCP with CLI

Google ADK

Use Google Tasks MCP with Google ADK

LangChain

Use Google Tasks MCP with LangChain

Vercel AI SDK

Use Google Tasks MCP with Vercel AI SDK

Mastra AI

Use Google Tasks MCP with Mastra AI

LlamaIndex

Use Google Tasks MCP with LlamaIndex

OpenCode

Use Google Tasks MCP with OpenCode

VS Code

Use Google Tasks MCP with VS Code

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Sheets

Oauth2

Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.

Notion

Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

Airtable

Oauth2Api Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

Asana

Oauth2

Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.

FAQ

Frequently asked questions

With a standalone Google Tasks MCP server, the agents and LLMs can only access a fixed set of Google Tasks tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Tasks 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 Tasks tools.

Yes, absolutely. You can configure which Google Tasks 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 Tasks data and credentials are handled as safely as possible.

Start with Google Tasks.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

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

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

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

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

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

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

Co-Founder, Ingram Technologies

How to integrate Google Tasks MCP with CrewAI

Connect Google Tasks without auth hassles

Introduction

Also integrate Google Tasks with

TL;DR

What is CrewAI?

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

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio Tool Router session for Google Tasks

Initialize the MCP Server

Create a CLI Chatloop and define the Crew

Complete Code

Conclusion

Supported Tools and Triggers

How to build Google Tasks MCP Agent with another framework

ChatGPT

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

Cursor

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

OpenCode

VS Code

Explore Other Toolkits

Google Sheets

Notion

Airtable

Asana

Frequently asked questions

What are the differences in Tool Router MCP and Google Tasks MCP?+

Can I use Tool Router MCP with CrewAI?+

Can I manage the permissions and scopes for Google Tasks while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Google Tasks.It takes 30 seconds.

Teams ship real agents on Composio