Google TasksCAUTION
This Model Context Protocol (MCP) server provides a bridge between LLMs and Google Tasks, allowing you to manage your task lists and tasks directly through Claude.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
This Model Context Protocol (MCP) server provides a bridge between MCP clients and Google Tasks, allowing you to manage your task lists and tasks directly from clients like Claude Desktop, Cursor, and Codex.
[!NOTE] All (bar some edits) code in this project was "vibe coded" - generated with Claude/Copilot with instructions from me.
Features
This MCP server provides the following functionality:
Task List Management
list-tasklists- List all your task listsget-tasklist- Get details about a specific task listcreate-tasklist- Create a new task listupdate-tasklist- Update an existing task listdelete-tasklist- Delete a task list
Task Management
list-tasks- List all tasks in a task list, including paginated resultsget-task- Get details about a specific taskcreate-task- Create a new taskupdate-task- Update an existing taskdelete-task- Delete a taskcomplete-task- Mark a task as completedmove-task- Move a task (reorder, change parent, or move across task lists)clear-completed-tasks- Clear all completed tasks from a list
Setup Instructions
1. Create Google Cloud Project & Enable API
- Go to the Google Cloud Console
- Create a new project
- Navigate to "APIs & Services" > "Library"
- Search for "Google Tasks API" and enable it
- Go to "APIs & Services" > "Credentials"
- Click "Create Credentials" > "OAuth Client ID"
- Configure the OAuth consent screen (External is fine for personal use)
- For Application Type, select "Web application"
- Add "http://localhost:3000/oauth2callback" as an authorized redirect URI
- Create the client ID and secret
2. Configure Environment Variables
Create a .env file in this project directory:
GOOGLE_CLIENT_ID=your_client_id_here GOOGLE_CLIENT_SECRET=your_client_secret_here GOOGLE_REDIRECT_URI=http://localhost:3
fa0412b62e81OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add google-tasks-mcp --env GOOGLE_CLIENT_SECRET=${GOOGLE_CLIENT_SECRET} -- npx -y [email protected]{
"mcpServers": {
"google-tasks-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"GOOGLE_CLIENT_SECRET": "${GOOGLE_CLIENT_SECRET}"
}
}
}
}Exposed tools (15)
6 read · 6 write · 3 destructive. Blast radius: 3 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.
| Tool | Risk | Description |
|---|---|---|
authenticate | read | |
clear-completed-tasks | destructive | |
complete-task | read | |
create-task | write | |
create-tasklist | write | |
delete-task | destructive | |
delete-tasklist | destructive | |
get-task | read | |
get-tasklist | read | |
list-tasklists | read | |
list-tasks | read | |
move-task | write | |
set-auth-code | write | |
update-task | write | |
update-tasklist | write |
Trust audit
CAUTIONgrade B · trust 87/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | FAIL |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | WARN |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (6)
.env
clear-completed-tasks, delete-task, delete-tasklist
.env
@modelcontextprotocol/sdk, dotenv, google-auth-library, googleapis, zod, @types/node, ts-node, typescript
screenshot.png
- **No re-authentication needed** - After the initial setup, you won't need to authenticate again unless you revoke access or delete the credentials file
Gates applied: no_behavioural_pass.
fa0412b62e81full audit observations/trust-audit/mcp-server/arpitbatra123__google-tasks-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | fa0412b62e81 | CAUTION | B | 87 | first audit |
Questions
What is the Google Tasks MCP server?
This Model Context Protocol (MCP) server provides a bridge between LLMs and Google Tasks, allowing you to manage your task lists and tasks directly through Claude.
What tools does Google Tasks expose?
15 in total: 6 read-only, 6 that write, and 3 that can delete or overwrite (clear-completed-tasks, delete-task, delete-tasklist). Every one is listed on this page with its risk.
Is Google Tasks safe to connect to an agent?
With care. The audit graded it B (87/100) and found 6 things worth knowing before you trust this server, listed below with the exact line each was found on. Separately from the audit: 3 of its tools can destroy data, so scope the token you give it to what you actually need.
What credentials does Google Tasks need?
It reads GOOGLE_CLIENT_SECRET from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Google Tasks run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as google-tasks-mcp at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (fa0412b62e81), read on 2026-10-08. The repository is watched and re-audited when it changes.