google-task-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_TASKS_CLIENT_ID | Yes | OAuth client ID from Google Cloud Console | |
| GOOGLE_TASKS_TOKEN_PATH | No | Optional path to store the OAuth token file | |
| GOOGLE_TASKS_REDIRECT_URI | No | OAuth redirect URI (default is http://127.0.0.1:53682/oauth2callback) | http://127.0.0.1:53682/oauth2callback |
| GOOGLE_TASKS_CLIENT_SECRET | Yes | OAuth client secret from Google Cloud Console |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_tasks_get_authorization_urlA | Start local OAuth 2.0 authorization and return the URL the user must open in a browser. |
| google_tasks_complete_authorizationA | Confirm the browser OAuth callback has completed and save the local token. |
| google_tasks_list_tasklistsB | List the user's Google Tasks lists. |
| google_tasks_list_tasksC | List tasks in a Google Task list. |
| google_tasks_create_taskC | Create a Google Task. Due dates are RFC 3339 timestamps, for example 2026-08-18T17:00:00Z. |
| google_tasks_update_taskB | Update a task's title, notes, or due date. At least one editable field is required. |
| google_tasks_set_task_completionC | Complete or uncomplete a task. |
| google_tasks_delete_taskA | Permanently delete one task. First show the exact task to the user; this tool refuses to run without confirm: true. |
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 8 tools
Each tool addresses a distinct operation: authorization, listing, creation, update, completion, and deletion. There is no overlap or ambiguity between the tools.
All tools follow a consistent `google_tasks_<verb>_<noun>` pattern, with clear, predictable verbs like `list`, `create`, `update`, and `delete`.
With 8 tools, the set covers the core lifecycle of managing Google Tasks (auth, lists, tasks) without being excessive or sparse. Each tool has a clear purpose.
The tool set provides full CRUD for tasks (create, read, update, delete) plus completion toggling and authorization. It lacks a `get_task` detail endpoint, but the list tool likely returns sufficient information for most workflows.