Gtasks Mcp

io.github.alvinjchoiPublished by GitHub account alvinjchoiv0.2.0Updated Oct 27, 2026

Manage Google Tasks via MCP: list, search, create, update, move, and clear tasks.

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Local MCP server that lets an assistant read and manage Google Tasks: list, search, create, update, move, and clear tasks.

What you can do
  • List and search tasks, optionally scoped to one task list, with full pagination
  • Discover task lists and view parent/child hierarchy in tree order
  • Create, update, and delete tasks, and clear completed tasks from a list
  • Reorder, nest, un-nest, or move tasks between lists
When to use it
Useful when you want an assistant to work with your Google Tasks from a desktop MCP client such as Claude Desktop — reviewing what is due, adding tasks from a conversation, or reorganizing lists and subtasks.
Requirements
Runs locally via npx or a global npm install (Node.js). Needs a Google Cloud project with the Google Tasks API enabled and OAuth 2.0 Desktop credentials, supplied as GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and GOOGLE_REFRESH_TOKEN, or through credential files or a home config file. Desktop only.
Before you install
Requires a Google OAuth client secret and a refresh token with Tasks scope; the README says to treat refresh tokens like passwords, keep them out of version control, and rotate them if leaked. The assistant can create, modify, move, and delete tasks and clear completed ones, so changes affect your real Google Tasks data.

Installation

In SourceWeft

  1. Open Gtasks Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Google Tasks MCP Server

A Model Context Protocol (MCP) server for Google Tasks. Manage task lists and tasks through natural language in Claude Desktop and other MCP clients.

Forked from zcaceres/gtasks-mcp with stronger auth options, multi-list support, pagination, and hierarchy tools.

[Image] [npm version] [MCP Registry] [License: MIT]

Registry name: io.github.alvinjchoi/gtasks-mcp
npm: @alvincrave/gtasks-mcp

Features

  • List and search tasks (optionally scoped to one task list)
  • Paginate through all tasks (no silent 100-task cap)
  • Create, update, delete, and clear completed tasks
  • Discover task lists (list_task_lists)
  • View parent/child hierarchy (list_with_tree)
  • Reorder, nest, or move tasks across lists (move)
  • OAuth2 auth via env vars, credential files, or interactive auth
  • Docker support

Installation

Recommended (Claude Desktop / any MCP client) — runs the latest published npm package:

bash
npx -y @alvincrave/gtasks-mcp

Or install globally:

bash
npm install -g @alvincrave/gtasks-mcp

From source

bash
git clone https://github.com/alvinjchoi/gtasks-mcp.gitcd gtasks-mcpnpm installnpm run build

Setup

Option A — Environment variables (Claude Desktop)

  1. Create a Google Cloud project and enable the Google Tasks API.
  2. Create OAuth 2.0 Desktop credentials and obtain a refresh token (OAuth Playground with scope https://www.googleapis.com/auth/tasks works).
  3. Configure Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
json
{  "mcpServers": {    "gtasks": {      "command": "npx",      "args": ["-y", "@alvincrave/gtasks-mcp"],      "env": {        "GOOGLE_CLIENT_ID": "your_client_id_here",        "GOOGLE_CLIENT_SECRET": "your_client_secret_here",        "GOOGLE_REFRESH_TOKEN": "your_refresh_token_here"      }    }  }}

Option B — Credential files (local / shared with other Google MCP servers)

  1. Download your OAuth client JSON (gcp-oauth.keys.json).
  2. Authenticate once:
bash
export GTASKS_CREDENTIALS_PATH=/path/to/gcp-oauth.keys.jsonexport GTASKS_TOKEN_PATH=/path/to/.gtasks-server-credentials.jsonnode dist/index.js auth
  1. Run the server with the same env vars set (or place gcp-oauth.keys.json in the project root and use the defaults).

Aliases also accepted:

PurposePreferredAlias
OAuth client keysGTASKS_CREDENTIALS_PATHGOOGLE_OAUTH_KEYS_PATH
Saved tokensGTASKS_TOKEN_PATHGOOGLE_TASKS_CREDENTIALS_PATH

Option C — Home config file

Create ~/.gtasks-credentials.json:

json
{  "clientId": "your_client_id",  "clientSecret": "your_client_secret",  "refreshToken": "your_refresh_token"}

Tools

ToolDescription
searchSearch tasks by title/notes. Optional taskListId.
listList tasks (all lists, or one via taskListId). Fully paginated.
list_task_listsList task list names and IDs.
list_with_treeTree view for one list (parent/child, position order).
moveReorder, nest/un-nest, or move across lists.
createCreate a task (title required; optional notes/due/taskListId).
updatePatch a task (only provided fields change).
deleteDelete a task.
clearClear completed tasks from a list.

Usage examples

show my task listslist tasks in list <id>search for tasks containing "meeting"create a task named "Prepare presentation" due 2026-07-20show the task tree for list <id>move task <id> under parent <parentId>mark task <id> completed

Docker

bash
docker build -t gtasks-mcp .docker run -i \  -e GOOGLE_CLIENT_ID=your_client_id \  -e GOOGLE_CLIENT_SECRET=your_client_secret \  -e GOOGLE_REFRESH_TOKEN=your_refresh_token \  gtasks-mcp

Development

bash
npm installnpm run buildnpm start

Auth check / interactive login:

bash
npm run buildnode dist/index.js auth

Security Notes

  • Treat refresh tokens like passwords
  • Prefer env vars or ignored credential files — never commit them
  • Rotate credentials if they leak

Contributors

  • ArtyMcLabin — pagination, taskListId filtering, list_task_lists, list_with_tree, move, and file-based auth (#1)
  • zcaceres — original Google Tasks MCP server
  • alvinjchoi — fork maintenance, Smithery/npm packaging

See CONTRIBUTORS.md.

License

MIT

Source: README.md at commit d88254c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts