Google Tasks MCP
English | Русский
Power your agent
Perintah milik penerbit sendiri. Bukan endpoint PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code tidak punya tautan instal untuk perintah lokal. Salin perintah di bawah dan jalankan di terminal.
GOOGLE_TASKS_CLIENT_ID=<value> GOOGLE_TASKS_CLIENT_SECRET=<secret> GOOGLE_TASKS_REFRESH_TOKEN=<secret> GOOGLE_TASKS_ACCESS_TOKEN=<secret> GOOGLE_TASKS_OAUTH_PORT=<value> GOOGLE_TASKS_API_BASE=<value> GOOGLE_TASKS_TIMEOUT_MS=<value> GOOGLE_TASKS_MAX_RETRIES=<value> claude mcp add io.github.a1-x-tech-mcp-google-tasks -- npx -y mcp-google-tasks@1.1.2Jalankan di terminal.
{ "mcpServers": { "io.github.a1-x-tech-mcp-google-tasks": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOOGLE_TASKS_CLIENT_ID": "<value>", "GOOGLE_TASKS_CLIENT_SECRET": "<secret>", "GOOGLE_TASKS_REFRESH_TOKEN": "<secret>", "GOOGLE_TASKS_ACCESS_TOKEN": "<secret>", "GOOGLE_TASKS_OAUTH_PORT": "<value>", "GOOGLE_TASKS_API_BASE": "<value>", "GOOGLE_TASKS_TIMEOUT_MS": "<value>", "GOOGLE_TASKS_MAX_RETRIES": "<value>" } } }}claude_desktop_config.json
URL remote atau perintah di mesin Anda? Perbedaan kedua cara instal
Jalankan di PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
BukaDari penerbit
English | Русский
MCP server for the Google Tasks API: task lists, subtasks, due dates, complete and move tasks.
A1 Google Tasks MCP lets an AI app manage Google Tasks in plain language. Plan a project as a task list, break work into subtasks with due dates and notes, mark things done and keep everything in order.
It uses the Google Tasks API with your Google account. It separates reversible completion from permanent deletion and makes the limits of the Tasks API explicit instead of implying that every to-do feature is possible.
127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.complete_task has an undo (reopen_task); the delete tools are separate and marked destructive.tasks scope, without Drive, Calendar or Gmail access.Start with a read-only question:
Show me my task lists and everything due before Friday in my default list.
You: What's still open in the "Website launch" list, and what's due this week?
Assistant: Shows the open tasks with their due dates, notes and subtasks. Nothing changes.
You: Add a task "Send the launch announcement" due Friday as a subtask of "Marketing".
Assistant: Shows the target list, the parent task and the proposed task, then asks for confirmation before creating it.
You: Confirm.
Assistant: Creates the subtask with a Friday due date. It does not complete or delete anything unless you ask separately.
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
In the app: open Settings → MCP servers, select Add server, choose STDIO, enter the command npx -y mcp-google-tasks@latest and environment variables GOOGLE_TASKS_CLIENT_ID, GOOGLE_TASKS_CLIENT_SECRET, GOOGLE_TASKS_REFRESH_TOKEN, then select Save and Restart.
From the command line:
codex mcp add google-tasks \
-- npx -y mcp-google-tasks@latest
codex mcp list
claude mcp add \
--transport stdio --scope user google-tasks \
-- npx -y mcp-google-tasks@latest
claude mcp list
The current official path is Settings → Extensions. For a custom desktop extension, open Advanced settings → Extension Developer → Install Extension…, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
{
"mcpServers": {
"google-tasks": {
"command": "npx",
"args": ["-y", "mcp-google-tasks@latest"]
}
}
}
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows:
{
"mcpServers": {
"google-tasks": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-tasks@latest"]
}
}
}
Run MCP: Open User Configuration and add:
{
"servers": {
"google-tasks": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-google-tasks@latest"]
}
}
}
Check it with MCP: List Servers.
@default; create_tasklist adds more.move_task; the API's position field is read-only.reopen_task brings it back. Deleting a task or a list is permanent, and deleting a list removes every task in it.Recurring tasks cannot be created through the API. Tasks assigned from Google Docs or Chat can be read but not created or moved to another list, and deleting one also removes it in the originating document. There is no server-side search or sorting — the server lists tasks and the AI client filters them.
The AI client controls confirmation prompts. The server marks reads, writes and destructive tools so the client can distinguish an inspection from a live change.
Google Tasks requires OAuth 2.0; an API key is not enough. There are two ways in, and the first one needs no configuration files.
Say "connect Google Tasks" and the assistant runs the flow with you:
setup_instructions prints the checklist: create or select a Google Cloud project, enable Google Tasks API, configure the consent screen and create a Desktop app OAuth client.set_client stores it owner-only. The secret never goes through the conversation.start_login returns a Google consent link. Open it on this machine and approve; the code comes back to a one-shot listener on 127.0.0.1 (PKCE), never through the chat.finish_login exchanges the code and saves the tokens to ~/.config/mcp-google-tasks/credentials.json (mode 0600) and verifies them with a real Google Tasks API call — so an API that is still switched off is caught right there.The tokens are re-read on every call, so the connection works immediately — no restart of the AI app. auth_status shows what is connected, logout revokes and deletes it.
Create or select a Google Cloud project and enable Google Tasks API.
Configure the OAuth consent screen and create a Desktop app OAuth client.
Authorize the Google account that owns the tasks. The OAuth 2.0 Playground can obtain the refresh token when Use your own OAuth credentials is enabled.
Request the scope:
https://www.googleapis.com/auth/tasks
Testing-mode OAuth refresh tokens can expire after seven days. Publish the OAuth app, or use an Internal app in a Workspace domain, when you need long-lived access. Treat the client secret and refresh token as passwords.
Every variable is optional — with none of them the server connects from the chat.
* Provide either the OAuth trio or an access token.
Without credentials the server still starts and completes the MCP handshake; the first tool call then fails with a message naming the variables to set and asking for a restart.
ASKADS_TELEMETRY=0 to opt out.429, the server uses backoff; reads also retry after network and 5xx errors, while writes are not replayed after an uncertain failure — check the outcome with get_task instead.list_tasks supports incremental sync through the updated_min filter, so an AI app with scheduled tasks can check for changes periodically without re-reading everything.Found a bug or need a scenario? Create an issue or write in Telegram.
MCP server for the Google Tasks API: task lists, subtasks, due dates, complete and move tasks.
{ "mcpServers": { "io.github.a1-x-tech-mcp-google-tasks": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOOGLE_TASKS_CLIENT_ID": "<value>", "GOOGLE_TASKS_CLIENT_SECRET": "<secret>", "GOOGLE_TASKS_REFRESH_TOKEN": "<secret>", "GOOGLE_TASKS_ACCESS_TOKEN": "<secret>", "GOOGLE_TASKS_OAUTH_PORT": "<value>", "GOOGLE_TASKS_API_BASE": "<value>", "GOOGLE_TASKS_TIMEOUT_MS": "<value>", "GOOGLE_TASKS_MAX_RETRIES": "<value>" } } }}Tool
Belum ada daftar tool. Server remote mendapatkannya setelah pemeriksaan kesehatan pertama.
FAQ
Salin konfigurasi stdio untuk Cursor, Claude Desktop, Claude Code, atau VS Code di halaman ini. Konfigurasi ini memakai instalasi dari penerbit, bukan proxy PlugMCP.
Penerbit mencantumkan variabel lingkungan berikut: GOOGLE_TASKS_CLIENT_ID, GOOGLE_TASKS_CLIENT_SECRET, GOOGLE_TASKS_REFRESH_TOKEN, GOOGLE_TASKS_ACCESS_TOKEN, GOOGLE_TASKS_OAUTH_PORT, GOOGLE_TASKS_API_BASE, GOOGLE_TASKS_TIMEOUT_MS, GOOGLE_TASKS_MAX_RETRIES.
Google Tasks MCP berjalan secara lokal melalui stdio.
Terakhir diperiksa 2026-11-11. MCP server for the Google Tasks API: task lists, subtasks, due dates, complete and move tasks.