SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Google Tasks MCP with Claude Agent SDK

Connect Claude Agent SDK to Google Tasks MCP. Add a new task to your work list, list all tasks due this week, and more using natural language, with authentication handled for you.

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

Introduction

This guide walks you through connecting Google Tasks to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Google Tasks agent that can create and update tasks, manage task lists, reorder tasks, clear completed items, and view tasks across lists through natural language commands.

This guide will help you understand how to give your Claude Agent SDK 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

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKGrok BotMuseCodexKimi CodeGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Google Tasks
  • Configure an AI agent that can use Google Tasks as a tool
  • Run a live chat session where you can ask the agent to perform Google Tasks operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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 task lists and tasks, so your agent can create, retrieve, update, move, and delete them on your behalf.

  • Task creation and planning: Have your agent create tasks, add subtasks, and place new work in the right task list.
  • Task retrieval and review: Instruct your agent to retrieve a specific task, review tasks from one list, or list tasks across all your lists using completion and date filters.
  • Task updates and organization: Let the agent edit task details or move tasks to a different position or task list as your plans change.
  • Task list management: Direct your agent to create, retrieve, rename, or permanently delete task lists.
  • Completed task cleanup: Have your agent delete individual tasks or permanently clear completed tasks from a chosen list.

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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Google Tasks account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • 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

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Google Tasks functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Google Tasks
  const session = await composio.create(USER_ID, {
    toolkits: ['googletasks'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Google Tasks
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Google Tasks tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Google Tasks
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Google Tasks and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  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 composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['googletasks']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Google Tasks tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Google Tasks through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
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 its details, including its ID for use in task operations.

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 task in a specified list, optionally under a parent or after a sibling in that list.

List All Tasks Across All Lists

List tasks across the user's task lists with optional filters, annotating each returned task with its list ID and title.

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 with optional date, status, and pagination filters; date inputs can use human-readable formats, and a completion range forces an explicit false showCompleted value to true.

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

Claude Code logo

Claude Code

Use Google Tasks MCP with Claude Code

Cursor logo

Cursor

Use Google Tasks MCP with Cursor

ChatGPT logo

ChatGPT

Use Google Tasks MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Google Tasks MCP with Claude Cowork

Antigravity logo

Antigravity

Use Google Tasks MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Google Tasks MCP with OpenAI Agents SDK

Grok Bot logo

Grok Bot

Use Google Tasks MCP with Grok Bot

Muse logo

Muse

Use Google Tasks MCP with Muse

Codex logo

Codex

Use Google Tasks MCP with Codex

Kimi Code logo

Kimi Code

Use Google Tasks MCP with Kimi Code

Grok Build logo

Grok Build

Use Google Tasks MCP with Grok Build

VS Code logo

VS Code

Use Google Tasks MCP with VS Code

OpenCode logo

OpenCode

Use Google Tasks MCP with OpenCode

OpenClaw logo

OpenClaw

Use Google Tasks MCP with OpenClaw

Hermes logo

Hermes

Use Google Tasks MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Google Tasks MCP with Atomic Agent

CLI logo

CLI

Use Google Tasks MCP with CLI

Google ADK logo

Google ADK

Use Google Tasks MCP with Google ADK

LangChain logo

LangChain

Use Google Tasks MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Google Tasks MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Google Tasks MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Google Tasks MCP with LlamaIndex

CrewAI logo

CrewAI

Use Google Tasks MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Google Tasks MCP with Pydantic AI

AutoGen logo

AutoGen

Use Google Tasks MCP with AutoGen

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. Claude Agent SDK 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