mcpField
G
gtasks-mcp

gtasks-mcp

Local
github.com/alvinjchoiProductivity10Updated 14w ago

About gtasks-mcp

gtasks-mcp is an MCP server for managing Google Tasks task lists and tasks. It adds paginated listing, hierarchy views, and task moves across lists.

Key features

  1. 01Search and paginate tasks
  2. 02Create, update, and delete tasks
  3. 03List task lists
  4. 04View parent-child hierarchy
  5. 05Reorder, nest, and move tasks
  6. 06Clear completed tasks

Use cases

  1. 01Find tasks by title or notes
  2. 02Browse large task lists
  3. 03Organize task hierarchy and order
  4. 04Move tasks between lists

MCP support

It exposes Google Tasks list and task management tools to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"alvinjchoi-gtasks": {
"command": "npx",
"args": [
"-y",
"@alvincrave/gtasks-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
"GOOGLE_CLIENT_SECRET": "<GOOGLE_CLIENT_SECRET>",
"GOOGLE_REFRESH_TOKEN": "<GOOGLE_REFRESH_TOKEN>"
}
}
}
}
Run commandnpx -y @alvincrave/gtasks-mcp
Environment variables to set
GOOGLE_CLIENT_IDGoogle OAuth client ID
GOOGLE_CLIENT_SECRETSecretGoogle OAuth client secret
GOOGLE_REFRESH_TOKENSecretGoogle OAuth refresh token with Tasks scope

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@alvincrave/gtasks-mcp0.2.0

Tools

9

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
querystringYesSearch query
taskListIdstringNoTask list ID to search within. If omitted, searches all lists.

Details

From the project 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.

MCP Server 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:

npx -y @alvincrave/gtasks-mcp

Or install globally:

npm install -g @alvincrave/gtasks-mcp
From source
git clone https://github.com/alvinjchoi/gtasks-mcp.git
cd gtasks-mcp
npm install
npm 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):
{
  "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:
export GTASKS_CREDENTIALS_PATH=/path/to/gcp-oauth.keys.json
export GTASKS_TOKEN_PATH=/path/to/.gtasks-server-credentials.json
node 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:

{
  "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 lists
list tasks in list <id>
search for tasks containing "meeting"
create a task named "Prepare presentation" due 2026-07-20
show the task tree for list <id>
move task <id> under parent <parentId>
mark task <id> completed

Docker

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

npm install
npm run build
npm start

Auth check / interactive login:

npm run build
node 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.