# mcp-google-tasks

MCP server for the Google Tasks API: task lists, subtasks, due dates, complete and move tasks.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** io.github.A1-x-Tech
- **License:** MIT
- **npm:** mcp-google-tasks
- **Source:** https://github.com/A1-x-Tech/mcp-google-tasks
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 14 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-21T10:39:28.336Z
- **Version scanned:** 0.2.0
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `complete_task`
- `reopen_task` — Reverts a completed task to needsAction and clears its completed timestamp — the undo for complete_task. Works on hidden tasks too (tasks cleared with clear_com
- `clear_completed_tasks`
- `raw_request`
- `list_tasklists` — Lists the user's task lists: id, title, updated (RFC3339). Every task lives in exactly one list, so this is the entry point — task tools need a tasklist_id from
- `get_tasklist` — Fetches one task list by id: id, title, updated, selfLink. Accepts "@default" for the user's default list — useful to resolve its real id. The list resource car
- `create_tasklist` — Creates a new task list and returns it (id, title, updated). The API accepts only a title — there are no other list-level settings. The returned id is the taskl
- `update_tasklist` — Renames a task list (PATCH — the title is the only field the API lets you change). Tasks, their order and their completion state are untouched. Returns the upda
- `delete_tasklist` — Deletes a task list AND every task in it, permanently — there is no undo and no trash. The user's default task list cannot be deleted (the API rejects it). To e
- `list_tasks`
- `get_task` — Fetches one task by id: title, notes, status, due (date only), completed timestamp, parent, position, updated, deleted/hidden flags, links and webViewLink. Also
- `create_task`
- `update_task` — Changes a task's title, notes and/or due date (PATCH — only the provided fields change, at least one is required). clear_due=true / clear_notes=true erase the f
- `move_task`
- `delete_task` — Deletes a task permanently — this is NOT the same as completing it. To mark work done (reversibly), use complete_task instead. A deleted task disappears from de

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-google-tasks\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-google-tasks\"\n      ],\n      \"env\": {\n        \"GOOGLE_TASKS_CLIENT_SECRET\": \"<YOUR_GOOGLE_TASKS_CLIENT_SECRET>\",\n        \"GOOGLE_TASKS_REFRESH_TOKEN\": \"<YOUR_GOOGLE_TASKS_REFRESH_TOKEN>\",\n        \"GOOGLE_TASKS_ACCESS_TOKEN\": \"<YOUR_GOOGLE_TASKS_ACCESS_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `GOOGLE_TASKS_CLIENT_SECRET` — Google Tasks Client Secret (optional)
- `GOOGLE_TASKS_REFRESH_TOKEN` — Google Tasks Refresh Token (optional)
- `GOOGLE_TASKS_ACCESS_TOKEN` — Google Tasks Access Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 3 credentials (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Critical blast radius — deletes data; holds an oauth grant.
- Floor 62, ceiling 62 (tier: critical)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/mcp-google-tasks
- Install plan: https://forgeregistry.com/api/v1/packages/mcp-google-tasks/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mcp-google-tasks
- HTML page: https://forgeregistry.com/registry/mcp-google-tasks
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.