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
- 01Search and paginate tasks
- 02Create, update, and delete tasks
- 03List task lists
- 04View parent-child hierarchy
- 05Reorder, nest, and move tasks
- 06Clear completed tasks
Use cases
- 01Find tasks by title or notes
- 02Browse large task lists
- 03Organize task hierarchy and order
- 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.
npx -y @alvincrave/gtasks-mcpGOOGLE_CLIENT_IDGoogle OAuth client IDGOOGLE_CLIENT_SECRETSecretGoogle OAuth client secretGOOGLE_REFRESH_TOKENSecretGoogle OAuth refresh token with Tasks scopeLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
9Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | Yes | Search query |
| taskListId | string | No | Task list ID to search within. If omitted, searches all lists. |
Details
From the project READMEGoogle 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.
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)
- Create a Google Cloud project and enable the Google Tasks API.
- Create OAuth 2.0 Desktop credentials and obtain a refresh token (OAuth Playground with scope
https://www.googleapis.com/auth/tasksworks). - Configure Claude Desktop (
~/Library/Application Support/Claude/claude_desktop_config.jsonon 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)
- Download your OAuth client JSON (
gcp-oauth.keys.json). - 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
- Run the server with the same env vars set (or place
gcp-oauth.keys.jsonin the project root and use the defaults).
Aliases also accepted:
| Purpose | Preferred | Alias |
|---|---|---|
| OAuth client keys | GTASKS_CREDENTIALS_PATH | GOOGLE_OAUTH_KEYS_PATH |
| Saved tokens | GTASKS_TOKEN_PATH | GOOGLE_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
| Tool | Description |
|---|---|
search | Search tasks by title/notes. Optional taskListId. |
list | List tasks (all lists, or one via taskListId). Fully paginated. |
list_task_lists | List task list names and IDs. |
list_with_tree | Tree view for one list (parent/child, position order). |
move | Reorder, nest/un-nest, or move across lists. |
create | Create a task (title required; optional notes/due/taskListId). |
update | Patch a task (only provided fields change). |
delete | Delete a task. |
clear | Clear 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,
taskListIdfiltering,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
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.