# How to integrate Google Tasks MCP with Grok Build ```json { "title": "How to integrate Google Tasks MCP with Grok Build", "toolkit": "Google Tasks", "toolkit_slug": "googletasks", "framework": "Grok Build", "framework_slug": "grok-build", "url": "https://composio.dev/toolkits/googletasks/framework/grok-build", "markdown_url": "https://composio.dev/toolkits/googletasks/framework/grok-build.md", "updated_at": "2026-05-12T10:14:10.893Z" } ``` ## Introduction ### How to integrate Google Tasks MCP with Grok Build [Grok Build](https://docs.x.ai/build/overview) is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes. In this guide, I will show you how to connect your Google Tasks account to Grok Build through Composio, so it can add a new task to your work list, list all tasks due this week, delete completed tasks from your shopping list, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve. ## Also integrate Google Tasks with - [ChatGPT Work](https://composio.dev/toolkits/googletasks/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/googletasks/framework/antigravity) - [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 Code](https://composio.dev/toolkits/googletasks/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/googletasks/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/googletasks/framework/codex) - [Kimi Code](https://composio.dev/toolkits/googletasks/framework/kimi) - [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 ### Why use Composio over a standalone MCP server? - Read and write access. Composio's Google Tasks integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data. - 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce. - One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app. - Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using. - Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt. ## Connect Google Tasks to Grok Build ### Prerequisites - Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at [console.x.ai](https://console.x.ai/)). - Access to the Google Tasks account you want to connect. - The [Composio MCP endpoint](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=grok-build&utm_content=composio_connect). Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up. ### Step-by-step: Connect Google Tasks to Grok Build ### 1. Install and verify Grok Build Install the CLI, then restart your shell so the grok binary lands on your PATH: ```bash curl -fsSL https://x.ai/cli/install.sh | bash which grok ``` ## 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_BATCH_EXECUTE` | Batch Execute Google Tasks Operations | Executes multiple Google Tasks API operations in a single HTTP batch request and returns structured per-item results. Use this to reduce LLM tool invocations when performing bulk operations like updating many tasks, moving tasks, or deleting multiple items. Note: Each sub-request still counts toward API quota; batching primarily reduces HTTP overhead and tool call count. | | `GOOGLETASKS_CLEAR_TASKS` | Clear tasks | Permanently and irreversibly clears all completed tasks from a specified Google Tasks list; this action is destructive, idempotent, and cannot be undone. Always require explicit user confirmation before invoking. | | `GOOGLETASKS_CREATE_TASK_LIST` | Create a task list | Creates a new task list with the specified title and returns a tasklist_id. Use the returned tasklist_id (not the title) when calling GOOGLETASKS_INSERT_TASK or other task operations. Duplicate titles are permitted by the API, so verify existing lists before creating to avoid unintended duplicates. | | `GOOGLETASKS_DELETE_TASK` | Delete task | Deletes a specified task from a Google Tasks list. Deletion is permanent and irreversible — confirm with the user before executing, and consider GOOGLETASKS_UPDATE_TASK or GOOGLETASKS_MOVE_TASK as non-destructive alternatives. Both tasklist_id and task_id are required parameters. The Google Tasks API does not support deleting tasks by task_id alone — you must specify which task list contains the task. Use 'List Task Lists' to get available list IDs, then 'List Tasks' to find the task_id within that list. | | `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. Require explicit user confirmation before calling; do not invoke in read-only or exploratory flows. | | `GOOGLETASKS_GET_TASK` | Get Task | Retrieve a specific Google Task. REQUIRES both `tasklist_id` and `task_id`. Tasks cannot be retrieved by ID alone - you must always specify which task list contains the task. Use this to refresh task details before display or edits rather than relying on potentially stale results from GOOGLETASKS_LIST_TASKS. | | `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. IMPORTANT: Date fields (due, completed) accept various formats like '28 Sep 2025', '11:59 PM, 22 Sep 2025', or ISO format '2025-09-21T15:30:00Z' and will automatically convert them to RFC3339 format required by the API. Not idempotent — repeated calls with identical parameters create duplicate tasks; track returned task IDs to avoid duplication. High-volume inserts may trigger 403 rateLimitExceeded or 429; apply exponential backoff. | | `GOOGLETASKS_LIST_ALL_TASKS` | List All Tasks Across All Lists | Tool to list all tasks across all of the user's task lists with optional filters. Use when the agent needs to see all tasks without knowing which list to query first. Each returned task is annotated with its tasklist_id and tasklist_title for context. | | `GOOGLETASKS_LIST_TASK_LISTS` | List task lists | Fetches the authenticated user's task lists from Google Tasks; results may be paginated. Response contains task lists under the `items` key. Multiple lists may share similar names — confirm the correct list by ID before passing to other tools. | | `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. Response key for tasks is `tasks` (not `items`). No full-text search; filter client-side by title/notes. Results ordered by position, not by date. | | `GOOGLETASKS_MOVE_TASK` | Move Task | Moves the specified task to another position in the task list or to a different task list. Use cases: - Reorder tasks within a list (use 'previous' parameter) - Create subtasks by moving a task under a parent (use 'parent' parameter) - Move tasks between different task lists (use 'destinationTasklist' parameter) - Move a subtask back to top-level (omit 'parent' parameter) | | `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_FULL` | Update Task (Full Replacement) | Tool to fully replace an existing Google Task using PUT method. Use when you need to update the entire task resource, not just specific fields. This method requires all required fields (id, title) and replaces the complete task, unlike PATCH which supports partial updates. | | `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 Once connected, Grok Build can access the Google Tasks MCP server via Composio to run the app actions you authorize, directly from your terminal. ## Complete Code None listed. ## How to build Google Tasks MCP Agent with another framework - [ChatGPT Work](https://composio.dev/toolkits/googletasks/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/googletasks/framework/antigravity) - [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 Code](https://composio.dev/toolkits/googletasks/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/googletasks/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/googletasks/framework/codex) - [Kimi Code](https://composio.dev/toolkits/googletasks/framework/kimi) - [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 is the difference between the Composio Tool Router and a standalone Google Tasks MCP server? A standalone Google Tasks MCP server gives Grok Build a fixed set of Google Tasks tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Google Tasks and many other apps on demand, based on the task, all through a single endpoint. ### Does Grok Build support MCP? Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically. ### Can I reuse the same MCP config I already use with Claude Code? Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits. ### How safe is my Google Tasks data with Composio? Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Google Tasks data and credentials are handled to that standard. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)