Log inSubmit server
Google Tasks MCP logo

Google Tasks MCP

Manage Google Tasks lists and tasks through MCP, including subtasks, date-only due dates, ordering, completion, and deletion.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Tasks MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-tasks-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-google-tasks@latest"
      ],
      "env": {
        "GOOGLE_TASKS_CLIENT_ID": "YOUR_VALUE_HERE",
        "GOOGLE_TASKS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "GOOGLE_TASKS_REFRESH_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 21 tools correctly (8d ago).

Overview

Google Tasks MCP connects AI clients to the Google Tasks API for reading and changing task lists and tasks. It provides 21 tools for creating, updating, moving, completing, reopening, clearing, and deleting work, plus a raw API request option. OAuth 2.0 can be initiated from the conversation, with PKCE on localhost and tokens retained by the server. Reach for it when an agent needs to organize Google Tasks while respecting the API's date-only due dates and irreversible deletion behavior.

Use cases

  • List open tasks due before a specified date
  • Create project task lists with nested subtasks
  • Move tasks between lists and reorder work
  • Mark tasks complete and reopen them later
  • Clear completed tasks after reviewing a list

Key features

  • 21 tools for Google Tasks lists and tasks
  • OAuth 2.0 connection with PKCE
  • Reversible completion through task reopening
  • Date-only due dates matching the Tasks API
  • Task movement, nesting, and cross-list organization
  • Raw Google Tasks API request access

Tools21

What Google Tasks MCP lets your agent do. Expand a tool for its parameters.

Verified live~4.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

12/12 checks healthy over the last 66d

What it can do

From the 21 tools this server returned when we ran it; 21 declare their own safety hints.

Can delete or modify data · 9Handles credentials · 6Makes network requests · 21Read-only tools · 12
Network at startup4 connections
Files written at startup1
Install scriptsprepare
npm provenanceNot published
Package age66 days
Maintainers1

Observed 2026-11-04 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · mcp-google-tasks@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed21Callable tools this server registers over MCP.

How Google Tasks MCP works

What Google Tasks MCP does

Google Tasks MCP exposes Google Tasks through the Model Context Protocol. It works with the account's task lists, including the built-in default list identified by @default, and can inspect or change the tasks within them. The server supports titles, notes, date-only due dates, completion state, nesting, and ordering.

Its tool set covers 21 operations. These include listing, creating, and updating task lists and tasks; moving tasks between positions, parents, and lists; marking tasks complete; reopening completed tasks; clearing completed tasks from a list view; and deleting tasks or lists. A raw API request tool provides access to Google Tasks methods without a dedicated wrapper.

The server distinguishes ordinary reads, changes, reversible completion actions, and destructive operations so an MCP client can present suitable confirmation prompts. Completing a task can be undone with reopen_task. Deleting a task is permanent, and deleting a list also removes its tasks.

How it works

Google Tasks MCP uses Google OAuth 2.0 rather than an API key. A user can tell the assistant to connect Google Tasks, after which the server guides the OAuth setup, receives Google's redirect on 127.0.0.1, uses PKCE, and stores the resulting tokens itself. This conversational flow avoids requiring credentials during installation or a configuration-file edit.

Task dates follow the Google Tasks API: only the calendar date is stored. A requested time of day is not scheduled, so time-specific instructions belong in task notes. Ordering and nesting are changed with move_task; the API's position field is read-only.

The server does not provide server-side search or sorting. It returns tasks and lets the AI client filter the results. Recurring tasks cannot be created through the API. Tasks originating in Google Docs or Google Chat can be read, but they cannot be created or moved to another list through this API; deleting one also affects its originating document.

Setup and configuration

Node.js 20 or newer and a Google account are required. Install the npm stdio package with the @latest tag through an MCP client, for example:

Terminal
npx -y mcp-google-tasks@latest

Codex and Claude Code can add that command as an stdio server. Claude Desktop, Cursor, and VS Code also have documented stdio configurations for the package. Claude Desktop's current extension path expects an .mcpb bundle, while this project publishes an npm stdio package; local configuration is available in desktop builds that still support it.

For a manual credential setup, the documented environment variables are GOOGLE_TASKS_CLIENT_ID, GOOGLE_TASKS_CLIENT_SECRET, and GOOGLE_TASKS_REFRESH_TOKEN. The conversational connection flow can establish access without entering those values at installation time. Google access uses the Tasks scope and does not request Drive, Calendar, or Gmail access.

Tools and capabilities

Typical workflows include:

  • Listing task lists and open or completed tasks.
  • Creating task lists, tasks, notes, subtasks, and date-only due dates.
  • Updating titles, notes, and due dates.
  • Moving tasks to another list, changing their order, or nesting them under another task.
  • Completing and reopening tasks.
  • Clearing completed tasks or deleting individual tasks and lists.
  • Calling the underlying Google Tasks API when a dedicated tool is unavailable.

Read operations leave Google Tasks unchanged. Creation, updates, moves, and completion alter the account, while clearing and deletion are destructive actions.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Tasks MCP

Google Tasks MCP is an MCP server that connects AI clients to the Google Tasks API. Its main tools list, create, update, move, complete, reopen, clear, and delete task lists and tasks, while also supporting subtasks, notes, date-only due dates, and raw API requests for uncovered methods.

Install it as an npm stdio server with `npx -y mcp-google-tasks@latest`. Add that command through your MCP client, then say “connect Google Tasks” to start the OAuth flow. Node.js 20 or newer and a Google account are required.

Connect it by telling the assistant “connect Google Tasks.” The server guides OAuth 2.0 setup, uses PKCE, handles Google's redirect on `127.0.0.1`, and retains the tokens. A manual setup can instead use the client ID, client secret, and refresh token environment variables.

Yes, Google Tasks MCP works with Cursor as a stdio server. Add `mcp-google-tasks@latest` to Cursor's MCP configuration, using the `npx` command and `-y` argument, then connect the Google account through the conversational OAuth flow.

No, Google Tasks MCP stores only calendar dates because that is what the Google Tasks API supports. Put a time-of-day instruction in the task's notes instead; the server does not pretend to create a timed schedule.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Tasks MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-tasks-mcp?style=directory)](https://allmcps.com/mcp/google-tasks-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/google-tasks-mcp"><img src="https://allmcps.com/api/badge/google-tasks-mcp?style=directory" alt="Google Tasks MCP on AllMCPs" /></a>