# How to connect Google Tasks to Grok Bot

> Set up Google Tasks for Grok Bot with Agent200, then check which tools are available to your agent.

- Page: https://www.agent200.com/connectors/google-tasks/framework/grok-bot/
- Connector: [Google Tasks](https://www.agent200.com/connectors/google-tasks.md)
- Framework: Grok Bot
- Updated: 2026-11-18

## Instructions for AI agents

Goal: connect Google Tasks to Grok Bot with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/google-tasks/framework/grok-bot/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Grok Bot's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure Google Tasks is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Grok Bot: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Grok Bot's exact menus or commands.
4. The first Google Tasks request returns an authorization link if the user has not connected Google Tasks yet: show it to them and continue once they have approved access on Google Tasks's own page.
5. Check it works with this request: "Ask Grok Bot to list the Agent200 tools available for Google Tasks, including which are read-only."
   What should come back:
   - A list of the Google Tasks tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Google Tasks, then retry.

## Overview

This guide connects Google Tasks to Grok Bot through Agent200's MCP server. When you finish, Grok Bot can search, read and act in Google Tasks with the tools Agent200 provides, whenever a request needs them.

You add one MCP server to Grok Bot with your Agent200 API key. Your Google Tasks account is connected through managed OAuth: you approve access once on Google Tasks's own page, and Agent200 keeps the connection working.

- **Connector:** [Google Tasks](https://www.agent200.com/connectors/google-tasks/)
- **Works with:** Grok Bot · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [6 tools](https://www.agent200.com/connectors/google-tasks/framework/grok-bot/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **Google Tasks enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a Google Tasks account.** They approve access once, on Google Tasks's own page.
- **Grok Bot, with custom MCP servers allowed.** Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.

## Connect Google Tasks to Grok Bot

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Google Tasks and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Open the custom connector form

In Grok Bot, open **Connect apps** from the sidebar and choose **Add a custom connector** at the bottom.

### Step 3: Fill in the server and your key

Enter the name Agent200, pick Type **Remote HTTPS**, enter the server URL and add one HTTP header: `Authorization` with the value `Bearer` followed by your key. Leave Client ID empty, then choose **Add plugin**.

File `Add a custom connector`:

```text
Name:          Agent200
Type:          Remote HTTPS
Server URL:    https://api.agent200.com/mcp/
HTTP headers:  Authorization: Bearer YOUR_AGENT200_API_KEY
```

### Step 4: Attach Agent200 in a chat

In a Bot chat, type `@` and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it.

### Step 5: Connect your Google Tasks account

The first time you ask Grok Bot for something in Google Tasks, Agent200 returns an authorization link. Open it and approve access on Google Tasks's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.

## Test your connection

Ask: "Ask Grok Bot to list the Agent200 tools available for Google Tasks, including which are read-only."

What should come back:

- A list of the Google Tasks tools enabled for this Agent200 project, with their names and descriptions. If no tools appear, check that the connector is available to the project and its tools are enabled.

If no tools appear, check your Agent200 project access for Google Tasks and make sure its tools are enabled. Tool availability depends on your project setup.

## Google Tasks tools Grok Bot can call

- **List task lists** (`google_tasks_list_tasklists`, read): List the user's task lists.
- **List tasks** (`google_tasks_list_tasks`, read): List the tasks in a task list.
- **Create a task** (`google_tasks_create_task`, write): Add a task with an optional due date and notes.
- **Update a task** (`google_tasks_update_task`, write): Change a task's title, notes or due date.
- **Complete a task** (`google_tasks_complete_task`, write): Mark a task as completed.
- **Delete a task** (`google_tasks_delete_task`, write): Remove a task from a list.

## How it works

1. **You ask Grok Bot.** In your own words, for something in Google Tasks.
2. **Grok Bot picks a tool.** It sees the Google Tasks tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own Google Tasks connection, within the tools and scopes your project allows.
4. **Grok Bot answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's Google Tasks account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and Google Tasks enforces what its API grants.

## Troubleshooting

### The server cannot be saved, or shows Disabled by team admin

Your team’s connector policy blocks it. Ask the admin to allow the Agent200 server address on the Plugins & MCPs page of the Cursor dashboard.

### Calls fail on a team with a network allowlist

If the admin applies the network allowlist to MCP servers, api.agent200.com must be on it.

### The connector shows Needs auth, or tools return 401

Check the Authorization header is exactly `Bearer`, a space and a valid key, then reconnect. If the key was replaced, remove the connector and add it again.

### The Bot cannot see the Google Tasks tools

Check Agent200 is enabled in your plugins, attach it with @ in the chat, and start a new chat if it was added mid-conversation.

### Grok Bot shows a Google Tasks authorization link

You have not connected Google Tasks yet, or the connection needs to be approved again. Open the link, approve access on Google Tasks's own page, then ask Grok Bot again.

### A tool call is refused or returns less than expected

Agent200 runs only what your project allows. Check that Google Tasks and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Google Tasks the access the task needs.

### The API key was pasted into a chat or committed

Create a new key on the [API keys page](https://agent200.com/platform/apikeys/), replace it in Grok Bot's MCP settings, and stop using the old one. Paste the key only into Grok Bot's settings, never into a chat.

## Use Google Tasks with another framework

- [Google Tasks + Claude](https://www.agent200.com/connectors/google-tasks/framework/claude.md)
- [Google Tasks + ChatGPT](https://www.agent200.com/connectors/google-tasks/framework/chatgpt.md)
- [Google Tasks + Claude Code](https://www.agent200.com/connectors/google-tasks/framework/claude-code.md)
- [Google Tasks + Muse](https://www.agent200.com/connectors/google-tasks/framework/muse.md)
- [Google Tasks + OpenAI Dots](https://www.agent200.com/connectors/google-tasks/framework/openai-dots.md)
- [Google Tasks + Claude Duet](https://www.agent200.com/connectors/google-tasks/framework/claude-duet.md)
- [Google Tasks + Hermes Agent](https://www.agent200.com/connectors/google-tasks/framework/hermes-agent.md)
- [Google Tasks + OpenClaw](https://www.agent200.com/connectors/google-tasks/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
