Log inSubmit server
Google Tasks logo

Google Tasks

Read and modify Google Tasks lists and tasks through MCP, including due dates, completion, ordering, and OAuth access.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Tasks

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": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@girmmy/google-tasks-mcp-server",
        "google-tasks-mcp-auth"
      ],
      "env": {
        "GOOGLE_TASKS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "GOOGLE_TASKS_TOKEN_PATH": "YOUR_VALUE_HERE",
        "GOOGLE_TASKS_OAUTH_PORT": "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.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y -p @girmmy/google-tasks-mcp-server google-tasks-mcp-auth

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 6d ago.

Overview

  • google-tasks
  • productivity
  • task-management
  • oauth

The google-tasks MCP server connects MCP clients to a user’s Google Tasks account for reading and writing task data. It manages task lists and tasks, including creation, updates, completion, deletion, reordering, subtasks, and due dates. Authorization uses a local Google OAuth flow, with credentials and refreshed tokens stored on the user’s machine. Reach for it when an agent needs to organize or maintain Google Tasks directly rather than using a separate task system.

Use cases

  • Create tasks and subtasks from an agent conversation
  • Update Google Tasks titles, notes, due dates, and status
  • Reorder tasks or move them between task lists
  • Review tasks using due-date and updated-time filters
  • Clear completed tasks from a list

Key features

  • Full task-list CRUD operations
  • Task creation, updates, completion, reopening, and deletion
  • Due dates, notes, subtasks, ordering, and cross-list moves
  • Pagination and due-date or updated-time task filters
  • Markdown or JSON tool responses
  • Local Google OAuth authorization with cached tokens

Tools14

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

Self-reported~90 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.

4/4 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @girmmy/google-tasks-mcp-server (npm)

Adoption & maintenance

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

GitHub stars2Stargazers on the source repository.
npm downloads637Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Tools exposed14Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Google Tasks works

What the google-tasks MCP server does

The google-tasks MCP server gives an MCP client access to Google Tasks through the Google Tasks API. It supports both task-list management and individual task operations, so an agent can inspect existing work, add new items, change task details, and maintain completion state.

Task lists can be listed, retrieved, created, renamed, and deleted. Deleting a list also deletes its tasks. Within a list, the server can create tasks, optionally create subtasks, update titles, notes, due dates, and status, mark items complete or incomplete, remove tasks, and clear completed items.

How it works

The package uses Google OAuth installed-app authorization. You create a desktop OAuth client in Google Cloud, enable the Google Tasks API, and authorize the account once. The authorization command opens a consent URL and uses a local loopback listener on port 53682 by default to receive the redirect.

The OAuth client JSON and cached token remain on the local machine. The token is refreshed automatically after the initial authorization.

Each tool accepts a response_format option with either markdown or json, allowing the client to choose a presentation suitable for an agent or application.

Setup and configuration

Install the npm package globally, run it with npx, or build it from a source checkout. From source, the documented flow is npm install followed by npm run build. MCP clients can launch the package with npx -y @girmmy/google-tasks-mcp-server, or run the built dist/index.js file directly.

Before starting the server, create the OAuth client JSON and place it at ~/.config/google-tasks-mcp-server/client_secret.json, or set GOOGLE_TASKS_CLIENT_SECRET to another path. Run google-tasks-mcp-auth once to authorize the account. The token is saved at ~/.config/google-tasks-mcp-server/token.json; GOOGLE_TASKS_TOKEN_PATH changes that location.

GOOGLE_TASKS_OAUTH_PORT changes the loopback port used during authorization. Authorization should run on the same machine as the browser used to approve access, because isolated containers, remote environments, or sandboxed shells may not route the localhost redirect correctly.

Tools and capabilities

The available operations include:

  • Listing, retrieving, creating, renaming, and deleting task lists.
  • Listing tasks with due-date or updated-time filters and pagination.
  • Retrieving, creating, and updating individual tasks.
  • Creating subtasks and positioning tasks when supported by the operation.
  • Completing, reopening, deleting, moving, and clearing completed tasks.
  • Reordering tasks, changing their parent, or moving them between lists.

The google-tasks MCP server exposes separate tools for these operations, including google_tasks_list_tasks, google_tasks_create_task, google_tasks_update_task, google_tasks_move_task, and the corresponding task-list tools.

Limitations and notes

The server requires each user to create and use their own Google OAuth client. It does not provide a shared hosted instance. The default authorization scope is read/write access to Google Tasks.

Client secrets and cached tokens are plain files on disk; the cached token uses file mode 0600. Keep these files out of source control. Delete and clear operations are marked with destructiveHint: true, allowing MCP clients to warn about or gate those actions.

When using Codex with a cold npx launch, the initial package download may require a longer startup timeout. The documented Codex configuration uses TOML, while Claude Desktop and Claude Code use MCP configuration entries.

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

google-tasks is an MCP server that connects MCP clients to your Google Tasks account through Google’s Tasks API. Its main tools list, create, update, complete, reopen, delete, move, and clear tasks, while also managing task lists. It uses OAuth credentials stored locally for authorization.

Install it globally with `npm install -g @girmmy/google-tasks-mcp-server`, run it through `npx`, or clone the repository and build it with `npm install` and `npm run build`. You must also create Google OAuth credentials and authorize the account before using the server.

Configure Cursor to launch the package with `npx` or the built Node.js entry point, then complete the one-time OAuth authorization separately.

Run `google-tasks-mcp-auth` after creating a Google Cloud desktop OAuth client and enabling the Google Tasks API. The command opens a consent URL, receives the redirect through a local loopback server, and caches the token for later launches.

Yes, it can create and update due dates, list tasks with due-date or updated-time filters, complete or reopen tasks, and clear completed tasks from a list. The available task tools also support notes, subtasks, ordering, and moving tasks between lists.

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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-tasks?style=directory)](https://allmcps.com/mcp/google-tasks)
HTML Embed
<a href="https://allmcps.com/mcp/google-tasks"><img src="https://allmcps.com/api/badge/google-tasks?style=directory" alt="Google Tasks on AllMCPs" /></a>