Google Tasks

Google Tasks

This connector reads and manages the signed-in user's Google Tasks through the Google Tasks API v1 (https://tasks.googleapis.com/tasks/v1): task lists, tasks and subtasks, due dates, completing, moving and creating. These are the tasks shown in Gmail, Calendar and the Google Tasks app. It works with personal Google accounts and Google Workspace.

Setup (one-time, about 10 minutes)

1. Open https://console.cloud.google.com, pick or create a project, then APIs & Services → Library → enable Google Tasks API.
2. APIs & Services → OAuth consent screen: choose Internal if you are on Google Workspace (simplest), otherwise External. For External, set the publishing status to In production: while an app is in Testing, Google revokes its refresh tokens after 7 days and the connector stops working every week. For your own use, the "unverified app" warning can be clicked through.
3. APIs & Services → Credentials → Create credentials → OAuth client ID → application type Web application → add the authorized redirect URI <your AnythingMCP URL>/api/mcp-oauth/callback (on AnythingMCP Cloud: https://cloud.anythingmcp.com/api/mcp-oauth/callback).
4. Paste the client ID and secret into GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET and install the connector.
5. On the connector page, click Authorize with Provider and sign in with the Google account whose tasks the AI should use. The refresh token is stored encrypted and access tokens are renewed automatically.

One Google client for all Google connectors: the same Cloud project and OAuth client can serve every Google connector (Gmail, Google Calendar, Google Drive, Google Sheets, Google Docs, Google Tasks, Search Console, Analytics, Ads). Enable each API in that project, reuse the same GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, and authorize each connector once: each one asks only for its own scopes.

Scope: the connector asks for https://www.googleapis.com/auth/tasks (read and change the user's tasks and lists). For a read-only setup, change the scope to https://www.googleapis.com/auth/tasks.readonly in the connector's OAuth settings, authorize again, and disable gtasks_create_tasklist, gtasks_create_task, gtasks_update_task, gtasks_complete_task and gtasks_move_task.

Switched off at install: gtasks_delete_task. Turn it on per tool if the AI should delete tasks; completing a task is usually what the user means.

Ids: list ids come from gtasks_list_tasklists; @default always means the default list ("My Tasks"). Task ids come from gtasks_list_tasks and belong to their list: every task call needs both ids.

Listing

• gtasks_list_tasks returns open and completed tasks by default. Tasks completed in the Google apps are hidden, so to see them pass show_completed: true and show_hidden: true; show_completed: false gives only open tasks.
• due_min / due_max filter on the due date (RFC 3339, e.g. 2026-10-15T00:00:00Z), completed_min / completed_max on completion time.
• A subtask carries parent, the id of its parent task; position orders siblings.
• Tasks assigned from Google Docs or Chat spaces appear only with show_assigned: true.

Writing

• gtasks_create_task adds a task at the top of the list; parent makes it a subtask, previous places it after a sibling.
• due is a date: Google stores only the day, so 2026-10-15T00:00:00.000Z is "15 October"; a time of day cannot be set through the API.
• gtasks_complete_task marks a task done; gtasks_update_task with status: "needsAction" reopens it and changes title, notes or due date (only the fields given).
• gtasks_move_task re-parents, reorders or moves a task to another list (destination_tasklist_id).

Pagination: list responses carry nextPageToken while more results exist; call the same tool with the same arguments and page_token set to it. Tasks come 20 per page by default, up to 100 with max_results.

Limits and quotas: the Tasks API has a daily request quota per project (50,000 by default) and per-user rate limits. Over the limit Google answers 403 rateLimitExceeded or 429: wait and retry. A user can have up to 2,000 lists and 20,000 tasks per list.

Common errors

• 401: the authorization expired or was revoked (always after 7 days while the consent screen is in Testing). Click Authorize with Provider again.
• 403 insufficientPermissions: the scope does not allow the call (a write on a read-only setup). 403 accessNotConfigured: enable the Google Tasks API in the Cloud project.
• 404: the list or task id is wrong, or the task belongs to another list.
• 400 Invalid Value on due: write it as a full RFC 3339 timestamp, e.g. 2026-10-15T00:00:00.000Z.

Out of scope here: renaming or deleting task lists, clearing completed tasks, and recurring task rules.