MCP.Market

Google Tasks MCP server

by girmmy·io.github.girmmy/google-tasks·v1.0.3·1 stars
No reviews yet

Read/write Google Tasks: create, update, complete, delete, move tasks and lists, with due dates.

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Growing

1 stars60 downloads/wk

Reviews

Write one

Nobody has reviewed Google Tasks yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Google Tasks tools (14, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • google_tasks_clear_completed_tasks

    Clear all completed tasks from a task list. Cleared tasks are hidden from the default view (they become 'hidden' and won't reappear unless show_hidden=true is passed to google_tasks_list_tasks). This does not delete incomplete tasks. Args: - tasklist_id (string): ID of the task list, or '@default' (default: '@default') Returns a confirmation message. Examples: - Use when: "Clear out everything I'v

  • google_tasks_complete_task

    Mark a task as completed. Args: - tasklist_id (string): ID of the task list, or '@default' (default: '@default') - task_id (string): ID of the task to complete - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns the updated task with status='completed' and a completion timestamp. Examples: - Use when: "Mark 'buy milk' as done"

  • google_tasks_create_taskwrite action
  • google_tasks_create_tasklistwrite action

    Create a new Google Task list (a new top-level container, e.g. "Work" or "Groceries"). Args: - title (string): Title for the new list - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns the newly created task list's id and title. Use the returned id as tasklist_id in other tools. Examples: - Use when: "Make me a new task list called Home Renovation" - Don't use whe

  • google_tasks_delete_taskwrite action

    Permanently delete a single task. This cannot be undone. Args: - tasklist_id (string): ID of the task list, or '@default' (default: '@default') - task_id (string): ID of the task to delete Returns a confirmation message. Don't use when: You want to remove all completed tasks at once — use google_tasks_clear_completed_tasks instead. Error Handling: - Returns "Error: Not found (404)" if task_id does

  • google_tasks_delete_tasklistwrite action

    Permanently delete a Google Task list AND all tasks in it. This cannot be undone and cannot target the '@default' list. Args: - tasklist_id (string): ID of the task list to delete (must not be '@default') Returns a confirmation message. Error Handling: - Returns "Error: Invalid request (400)" if you try to delete the default list. - Returns "Error: Not found (404)" if tasklist_id doesn't exist.

  • google_tasks_get_task

    Fetch full details for a single task by ID. Args: - tasklist_id (string): ID of the task list, or '@default' (default: '@default') - task_id (string): ID of the task (from google_tasks_list_tasks) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns the task's title, status, due date, notes, completion time, and parent (if a subtask). Error Handling: - Returns "Erro

  • google_tasks_get_tasklist

    Fetch metadata for a single Google Task list by ID. Args: - tasklist_id (string): ID of the task list (from google_tasks_list_tasklists) - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns the task list's id, title, and last-updated time. Error Handling: - Returns "Error: Not found (404)" if the tasklist_id doesn't exist.

  • google_tasks_list_tasklists

    List all of the user's Google Task lists (the top-level containers tasks live in, shown as separate lists in the Google Tasks UI). Args: - limit (number): Max task lists to return, 1-100 (default: 20) - page_token (string, optional): Pagination token from a previous response's next_page_token - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns task list id + title

  • google_tasks_list_tasks
  • google_tasks_move_task
  • google_tasks_reopen_task

    Mark a completed task as not-done (status back to 'needsAction'). Args: - tasklist_id (string): ID of the task list, or '@default' (default: '@default') - task_id (string): ID of the task to reopen - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns the updated task with status='needsAction'.

  • google_tasks_update_taskwrite action
  • google_tasks_update_tasklistwrite action

    Rename an existing Google Task list. Args: - tasklist_id (string): ID of the task list to rename - title (string): New title - response_format ('markdown' | 'json'): Output format (default: 'markdown') Returns the updated task list. Error Handling: - Returns "Error: Not found (404)" if tasklist_id doesn't exist.

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings
  • Code scan21 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 34 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Google Tasks compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,243 servers
Tools
14
the typical server has 7
Tools that change things
43%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
60
more than 48% of 12,306 servers with a package

What its tools let an agent do: 8 read · 6 change

Install Google Tasks in Claude Code, Cursor or VS Code

Runs npx -y @girmmy/google-tasks-mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add google-tasks -- npx -y @girmmy/google-tasks-mcp-server
Add to Cursor

What the publisher says

From the Google Tasks repository's README, as published. We do not edit it. Read it on GitHub

google-tasks-mcp-server

An MCP server for Google Tasks. Gives any MCP client (Claude Desktop, Claude Code, Codex, Cursor, etc.) full read/write access to your task lists and tasks: list, create, update, complete, delete, and move them, with real due dates.

There's no official Google Tasks MCP server, so this covers that. Full CRUD, OAuth installed-app auth flow (your credentials never leave your machine), TypeScript throughout.

Tools

Task lists

  • googletaskslist_tasklists list all task lists
  • googletasksget_tasklist get one task list
  • googletaskscreate_tasklist create a new task list
  • googletasksupdate_tasklist rename a task list
  • googletasksdelete_tasklist delete a task list and all its tasks

Tasks

  • googletaskslist_tasks list tasks in a list, with due-date/updated filters and pagination
  • googletasksget_task get one task
  • googletaskscreate_task create a task (optionally as a subtask, optionally positioned)
  • googletasksupdate_task update title/notes/due date/status
  • googletaskscompletetask / googletasksreopentask mark done / not done
  • googletasksdelete_task delete a task
  • googletasksmove_task reorder, re-parent, or move a task to a different list
  • googletasksclearcompletedtasks clear all completed tasks from a list

Every tool supports response_format: "markdown" | "json".

Quick start

From npm:

npm install -g @girmmy/google-tasks-mcp-server

Or don't install it at all and let your MCP client run it via npx (see step 4).

Or from source:

git clone https://github.com/girmmy/google-tasks-mcp-server.git
cd google-tasks-mcp-server
npm install
npm run build

Either way, follow Setup below to create your own Google OAuth credentials and authorize. There's no shared or hosted version of this, it talks directly to your own Google account.

Setup

1. Create a Google Cloud OAuth client

Each user needs their own OAuth client. It's not something that can be shared, since anyone using your client secret could impersonate your app (though they'd still need each individual user's own consent).

  1. Go to the Google Cloud Console, create (or pick) a project.
  2. APIs & Services → Library → enable the Google Tasks API.
  3. APIs & Services → OAuth consent screen (Google now calls this "Google Auth Platform"):
  • User type: External is fine for personal use.
  • Fill in app name and your email for support/contact.
  • Under Audience → Test users, add your own Google account. While the app is in "Testing" status only listed test users can authorize it, which is fine for running this yourself.

~/.config/google-tasks-mcp-server/clientsecret.json (override the path with the GOOGLETASKSCLIENTSECRET env var, useful if you'd rather keep it inside the project directory, e.g. ./credentials/client_secret.json. credentials/ is already gitignored.)

  1. Clients → Create Client → Application type Desktop app. Create it.
  2. Grab the client ID and client secret, either via "Download JSON" right after creation or from the client's detail page later. Google's console won't show a secret's plaintext again once you navigate away, only download or regenerate it, so if you lose it just add a new secret instead of hunting for the old one.
  3. Save that file. By default this server looks for it at:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Google Tasks: common questions

Is Google Tasks MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Google Tasks safety report
How do I install Google Tasks?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Google Tasks need an API key?
No secret keys are declared. It reads 3 settings from the environment.
Is Google Tasks maintained?
The last commit was 56 days ago (2026-09-10). The latest release is v1.0.3.
How does Google Tasks compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,243 servers); tools 14 (the typical server has 7); tools that change things 43% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.