Google Tasks MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_TOKEN_FILE | No | Override the Google Tasks OAuth token path. Defaults to ~/.config/google-tasks-mcp/token.json | ~/.config/google-tasks-mcp/token.json |
| GOOGLE_API_NUM_RETRIES | No | Native Google client retries per request; integer from 0 to 10. Default is 3. | 3 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_task_listsA | List the authenticated user's Google task lists. |
| get_task_listA | Get one Google task list by ID. |
| create_task_listC | Create a Google task list. |
| update_task_listB | Rename a Google task list. |
| delete_task_listA | Permanently delete a Google task list. Requires explicit confirmation. |
| list_tasksA | List tasks in a Google task list with filters and pagination. |
| get_taskA | Get one task by task-list ID and task ID. |
| create_taskA | Create a task, optionally as a subtask or after a sibling. |
| update_taskB | Patch a task's title, notes, due date, or status. Use null to clear notes or due. |
| complete_taskC | Mark a task completed. |
| reopen_taskA | Mark a completed task as needing action again. |
| move_taskB | Reorder a task, change its parent, or move it to another task list. |
| delete_taskA | Permanently delete a task. Requires explicit confirmation. |
| clear_completed_tasksA | Hide all completed tasks in a list. Requires explicit confirmation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools target a distinct resource-action pair, but status transitions are split across complete_task, reopen_task, and update_task (which can set status), creating potential overlap. Descriptions help, so an agent can likely choose correctly.
All tools use snake_case verb_noun form, with task-list tools consistently using *_task_list and task tools using *_task. No mixed conventions are present.
14 tools are well-scoped for Google Tasks: five list operations and nine task operations, all justified by distinct lifecycle actions. No excessive or thin areas.
Covers CRUD for task lists and tasks, plus move, complete/reopen, and clear-completed, matching Google Tasks API lifecycle. No obvious dead ends.