google-tasks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_TASKS_MCP_HOME | No | Override the directory where the Tasks-only token is stored (default is ~/.config/google-tasks-mcp). |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_task_listsA | List the user's Google Tasks lists (id and title). |
| tasks_contextB | Snapshot of all open tasks across every list for use as conversation context:
overdue, due within |
| list_tasksA | List tasks in one list. |
| create_taskA | Create a task (marked as created by Claude). |
| update_taskA | Change a task's title, notes or due date (YYYY-MM-DD; empty string clears it). Only fields that are passed are changed. |
| complete_taskA | Mark a task completed. Without user_requested=true only tasks created by Claude can be completed; set it only when the user explicitly asked to complete this task. |
| reopen_taskC | Mark a completed task as not done again (same ownership rule as complete_task). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| with_my_tasks | Start a conversation with the user's open Google Tasks loaded as context. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| context_resource | Open tasks for the next 7 days, as JSON. |
TDQS
Scored across 7 tools
Most tools have clearly distinct actions (create, update, complete, reopen), and list_task_lists is unique. The only potential overlap is list_tasks versus tasks_context, since both return task data, but their descriptions clearly distinguish single-list filtered listing from a cross-list contextual snapshot.
Six of seven tools follow a clear verb_noun pattern (create_task, update_task, complete_task, reopen_task, list_task_lists, list_tasks). The outlier tasks_context is a noun phrase rather than an action, which is a minor inconsistency but remains understandable.
Seven tools is well-scoped for a Google Tasks integration, covering task creation, modification, completion lifecycle, and listing. No tool feels redundant or extraneous.
Core task lifecycle operations are covered, but there is no delete_task or get_task operation, and list management only supports listing rather than creating, renaming, or deleting task lists. These are notable gaps for full Google Tasks coverage, though common assistant workflows can mostly work around them.