# How to integrate Google Tasks MCP with Claude Code

```json
{
  "title": "How to integrate Google Tasks MCP with Claude Code",
  "toolkit": "Google Tasks",
  "toolkit_slug": "googletasks",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/googletasks/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/googletasks/framework/claude-code.md",
  "updated_at": "2026-05-06T08:14:35.383Z"
}
```

## Introduction

Manage your Google Tasks 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 Tasks with

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

### Connecting Google Tasks 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 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `GOOGLETASKS_CLEAR_TASKS` | Clear tasks | Permanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent. |
| `GOOGLETASKS_CREATE_TASK_LIST` | Create a task list | Creates a new task list with the specified title. |
| `GOOGLETASKS_DELETE_TASK` | Delete task | Deletes a specified task from a given task list in google tasks. |
| `GOOGLETASKS_DELETE_TASK_LIST` | Delete task list | Permanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible. |
| `GOOGLETASKS_GET_TASK` | Get Task | Use to retrieve a specific google task if its `task id` and parent `tasklist id` are known. |
| `GOOGLETASKS_GET_TASK_LIST` | Get task list | Retrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user. |
| `GOOGLETASKS_INSERT_TASK` | 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. |
| `GOOGLETASKS_LIST_TASK_LISTS` | List task lists | Fetches the authenticated user's task lists from google tasks; results may be paginated. |
| `GOOGLETASKS_LIST_TASKS` | 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. |
| `GOOGLETASKS_MOVE_TASK` | Move Task | Moves the specified task to another position in the destination task list. |
| `GOOGLETASKS_PATCH_TASK` | 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.g., `title`, `notes`, `due` date, `status`) and requiring both the task and list to exist. |
| `GOOGLETASKS_PATCH_TASK_LIST` | Patch task list | Updates the title of an existing google tasks task list. |
| `GOOGLETASKS_UPDATE_TASK` | Update Task | Updates the specified task. |
| `GOOGLETASKS_UPDATE_TASK_LIST` | Update Task List | Updates the authenticated user's specified task list. |

## Supported Triggers

| Trigger slug | Name | Description |
|---|---|---|
| `GOOGLETASKS_NEW_TASK_CREATED_TRIGGER` | New Task Created | Triggers when a new task is created in a Google Tasks list. Uses timestamp filtering (updatedMin) to efficiently detect new tasks. |
| `GOOGLETASKS_NEW_TASK_LIST_CREATED_TRIGGER` | New Task List Created | Triggers when a new Google Tasks task list is created. This trigger monitors Google Tasks and fires when new task lists are detected. |
| `GOOGLETASKS_TASK_DETAILS_CHANGED_TRIGGER` | Task Details Changed | Triggers when a specific task's details change. This trigger monitors a single Google Task and fires when any of its details (title, notes, status, due date, completion, position) are modified. |
| `GOOGLETASKS_TASK_LIST_CHANGED_TRIGGER` | Task List Changed | Triggers when a task list changes (title or content updates). This trigger monitors a specific Google Tasks list and fires when changes are detected. |
| `GOOGLETASKS_TASK_UPDATED_TRIGGER` | Task Updated | Triggers when an existing task is updated in a Google Tasks list. This trigger monitors a specific task list and fires when tasks are modified. |

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

The Google Tasks 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 Tasks account. It provides structured and secure access so Claude can perform Google Tasks 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 Tasks 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=["googletasks"],
)

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 googletasks-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: ['googletasks'],
});

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 googletasks-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 Tasks 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 (googletasks-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 googletasks-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 Tasks MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your googletasks-composio entry in the list
- This confirms that Claude Code can now access Google Tasks tools
If everything is wired up, you should see your googletasks-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Google Tasks

The first time you try to use Google Tasks tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Google Tasks
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Google Tasks authorization flow
- Return to the terminal and start using Google Tasks through Claude Code
Once authenticated, you can ask Claude Code to perform Google Tasks operations in natural language. For example:
- "Add a new task to my work list"
- "List all tasks due this week"
- "Delete completed tasks from my shopping list"

## 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=["googletasks"],
)

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 googletasks-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: ['googletasks'],
});

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 googletasks-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Google Tasks with Claude Code using Composio's MCP server. Now you can interact with Google Tasks directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Google Tasks 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 Tasks 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 Tasks MCP Agent with another framework

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

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - 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](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - 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](https://composio.dev/toolkits/asana) - 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.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.
- [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management.

## Frequently Asked Questions

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

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.

### 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 Tasks tools.

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

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.

### 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 Tasks data and credentials are handled as safely as possible.

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