Google Tasks MCP Server

Name: Google Tasks MCP Server
Author: ebmurha

作者：ebmurha版本 0.4.0i★ –i在你的电脑上运行

注册名称io.github.ebmurha/google-tasks-mcp

安装

概览

作者提供的说明（英文原文）

Manage Google Tasks from MCP-compatible AI clients.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI, DB_PATH, DEFAULT_TASKLIST

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "google-tasks": {
      "command": "uvx",
      "args": [
        "google-tasks-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "GOOGLE_REDIRECT_URI": "your-value",
        "DB_PATH": "your-value",
        "DEFAULT_TASKLIST": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add google-tasks --env GOOGLE_CLIENT_ID=your-value --env GOOGLE_CLIENT_SECRET=your-value --env GOOGLE_REDIRECT_URI=your-value --env DB_PATH=your-value --env DEFAULT_TASKLIST=your-value -- uvx google-tasks-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "google-tasks": {
      "command": "uvx",
      "args": [
        "google-tasks-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "GOOGLE_REDIRECT_URI": "your-value",
        "DB_PATH": "your-value",
        "DEFAULT_TASKLIST": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "google-tasks": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "google-tasks-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "GOOGLE_REDIRECT_URI": "your-value",
        "DB_PATH": "your-value",
        "DEFAULT_TASKLIST": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

GOOGLE_CLIENT_ID 机密必填 env
Google OAuth client ID from the user's Google Cloud project.
GOOGLE_CLIENT_SECRET 机密必填 env
Google OAuth client secret from the user's Google Cloud project.
GOOGLE_REDIRECT_URI 必填 env
OAuth callback URL for the user's local or hosted server.
DB_PATH env
Persistent SQLite database path for tokens and cache.
DEFAULT_TASKLIST env
Optional default tasklist title or ID.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 ebmurha 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32683 个服务器的 0%
发布到注册中心的时间比此分类中其他 32683 个服务器的 10% 更新
基础检查结果等于或优于此分类中其他 32683 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Google Tasks MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.0）于6个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

MCP Server Autocad Lisp Helper

作者：radwanalmsora

High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Google Tasks MCP Server

Connect an MCP-compatible client to Google Tasks through a private server you run yourself. The server exposes compact tools for reading, searching, summarizing, creating, completing, updating, deleting, and moving Google Tasks.

This project is for self-hosted use. You provide your own Google Cloud OAuth credentials, connect your own Google account, and keep tokens in your own SQLite database.

What You Get

19 MCP tools for Google Tasks.
Local stdio mode for desktop/client-launched setups.
Streamable HTTP mode for local HTTP or VPS hosting.
Bearer-token HTTP auth, plus optional OAuth 2.0 gateway mode for MCP clients that support OAuth.
Compact responses designed for low-context assistant workflows.
Optional operator-managed multi-account bearer-token routing, for familiar setups such as one personal account and one work account.

Choose A Transport

Use case	Transport	Auth
MCP client starts the process directly	`stdio`	No `MCP_BEARER_TOKEN` needed
Local HTTP server	Streamable HTTP at `http://127.0.0.1:8787/mcp`	Bearer token
VPS or other host	Streamable HTTP at `https://your-domain.example/mcp`	Bearer token or OAuth gateway

For deeper hosting and distribution guidance, see MCP_SERVER_GUIDE.md and DISTRIBUTION.md.

Container persistence

For a bearer-only single-account HTTP deployment whose filesystem is recreated on startup, GOOGLE_REFRESH_TOKEN can seed an empty SQLite database. It never overwrites an existing token. Keep it in the hosting provider's secret store; do not put it in a start command or Docker build argument. Hosts that provide PORT can use it when BIND_PORT is unset.

OAuth gateway deployments also persist dynamically registered clients and MCP refresh-token hashes. Configure the image's Litestream variables to restore and replicate SQLite to an S3-compatible bucket when the host filesystem is disposable. The container restores the database before starting the server and replicates changes while it runs.

Install

git clone https://github.com/ebmurha/google-tasks-mcp.git

cd google-tasks-mcp python3.11 -m venv .venv . .venv/bin/activate pip install -e . cp .env.example .env

Generate a bearer token if you will run HTTP mode:

python -c "import secrets; print(secrets.token_urlsafe(48))"

Put the generated value in .env as MCP_BEARER_TOKEN. Do not commit .env.

Google Cloud Setup

Create or open a Google Cloud project.
Enable the Google Tasks API.
Configure the OAuth consent screen.
Create an OAuth 2.0 Client ID.

Recommended for local HTTP, VPS, Docker, and other server-style installs:

Application type: Web application
Local redirect URI: http://127.0.0.1:8787/callback
Hosted redirect URI: https://your-domain.example/callback
.env: set GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GOOGLE_REDIRECT_URI

Local-only alternative:

Application type: Desktop app
Download the OAuth client JSON outside this repo.
Set GOOGLE_OAUTH_KEYS_PATH to that file path.
Leave GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET empty unless you want env vars to override the JSON file.

Example .env for a local web OAuth client:

GOOGLE_CLIENT_ID=your-client-id.apps.googleusercontent.com

GOOGLE_CLIENT_SECRET=your-client-secret GOOGLE_REDIRECT_URI=http://127.0.0.1:8787/callback MCP_BEARER_TOKEN=your-generated-token DB_PATH=./google-tasks.db BIND_HOST=127.0.0.1 BIND_PORT=8787

If the Google OAuth app is in Testing mode, add every Google account you bootstrap as a test user, such as both personal and work accounts.

GOOGLE_CLIENT_ID / GOOGLE_CLIENT_SECRET / GOOGLE_OAUTH_KEYS_PATH identify the Google Cloud OAuth app, not the Google Tasks user account. One OAuth client JSON can be reused for several Google users. Each bootstrap run stores a separate refresh token for the Google account you authorize in the browser.

Bootstrap Google OAuth

Hosted HTTP onboarding

For a hosted server, set these independently chosen values:

GOOGLE_REDIRECT_URI=https://your-domain.example/callback

GOOGLE_OAUTH_ONBOARDING_URL=https://your-domain.example/google/oauth GOOGLE_OAUTH_SETUP_SECRET=generate-a-long-random-operator-password

Configure the public URLs explicitly. The application serves the exact paths from GOOGLE_OAUTH_ONBOARDING_URL and GOOGLE_REDIRECT_URI; it does not retain root-path aliases. The MCP gateway likewise serves the paths declared by MCP_OAUTH_ISSUER and MCP_OAUTH_RESOURCE. A reverse proxy forwards these public paths unchanged. The displayed onboarding link never contains the setup secret.

OAuth-capable MCP clients use one continuous Connect or Reconnect flow. After the server's MCP consent is approved, it verifies the configured Google account. A usable Google credential continues directly to the MCP client. A missing or rejected Google credential continues through Google consent, stores the Google token in SQLite, and then returns to the same MCP client with its original OAuth state and PKCE binding. No token is displayed or copied.

GOOGLE_OAUTH_ONBOARDING_URL remains a separately password-protected recovery page. Open it directly only when explicit operator recovery is needed. If an authenticated MCP tool finds no usable Google token, its error includes this safe recovery URL.

Local and recovery CLI

Run this once per Google account you want the server to access:

google-tasks-mcp-bootstrap

Open the printed URL, approve access, and paste the authorization code back into the terminal.

For multiple trusted accounts on one HTTP server, create one stored bearer token per account and bootstrap each account separately:

google-tasks-mcp-create-bearer-token --account-id personal --label "Personal account"

google-tasks-mcp-bootstrap --account-id personal

google-tasks-mcp-create-bearer-token --account-id work --label "Work account" google-tasks-mcp-bootstrap --account-id work

Use each printed bearer token only in the matching account's MCP client. The server stores only bearer-token hashes.

Start The Server

HTTP mode:

python -m google_tasks_mcp --transport http

Health check:

curl http://127.0.0.1:8787/healthz

Expected response:

{"ok": true}

Stdio mode:

python -m google_tasks_mcp --transport stdio

Configuration check:

python -m google_tasks_mcp --check

Connect An MCP Client

Remote or local HTTP:

URL:  http://127.0.0.1:8787/mcp

Auth: Bearer

For a VPS, replace the URL with your HTTPS endpoint:

URL:  https://your-domain.example/mcp

Auth: Bearer

Local stdio:

"command": "/path/to/google-tasks-mcp/.venv/bin/python", "args": ["-m", "google_tasks_mcp", "--transport", "stdio"] }

MCP_BEARER_TOKEN is not required for stdio because the MCP client launches the process locally.

Authentication Modes

Bearer-token mode is the default HTTP mode. /mcp requires Authorization: Bearer .

MCP_BEARER_TOKEN routes to account default.
Tokens created with google-tasks-mcp-create-bearer-token can route different clients to different account_id values.
Bearer tokens are displayed once and stored only as hashes.

OAuth 2.0 gateway mode is optional. Enable it when your HTTP MCP client supports OAuth authorization metadata and token refresh.

Set MCP_OAUTH_ISSUER, MCP_OAUTH_CLIENT_ID, MCP_OAUTH_CLIENT_SECRET, and MCP_OAUTH_SIGNING_SECRET.
Set MCP_OAUTH_RESOURCE to the canonical public MCP URL, or let it default to /mcp.
Set MCP_OAUTH_REDIRECT_URIS to the callback URI values accepted by your MCP client.
Set MCP_OAUTH_ENABLE_DCR=true for clients that use Dynamic Client Registration.
The gateway publishes protected-resource and authorization-server metadata, requires PKCE S256, binds tokens to the canonical resource, and includes RFC 9207 issuer identification in authorization redirects.
/mcp accepts OAuth-issued access tokens and the legacy bearer token.
OAuth client secrets and refresh tokens are stored only by hash. Registered clients and rotating refresh tokens survive restarts when DB_PATH is durable.

The public proxy URL, MCP OAuth issuer/resource, and Google OAuth callback are operator-controlled deployment settings. They may be changed independently. The server does not require a particular hostname or derive these choices from an owner-specific URL.

MCP OAuth authenticates the client to this server. Google OAuth independently authorizes this server to call Google Tasks. The MCP consent flow coordinates the two layers so Connect and Reconnect cannot finish successfully while the configured Google account is knowingly unusable. The standalone operator page remains available for explicit recovery.

Leave MCP_OAUTH_REDIRECT_URIS empty to keep OAuth gateway mode disabled.

Tools

The same 19 tools are available over stdio, bearer-token HTTP, and OAuth gateway HTTP modes. Tools expose standard MCP titles, descriptions, and safety hints where the client supports them.

Group	Tools	Notes
Tasklists	`list_tasklists`, `create_tasklist`, `get_tasklist`, `update_tasklist`, `delete_tasklist`	Tasklist delete requires `confirm: true`; non-empty lists require `force: true`.
Task reads	`list_tasks`, `get_task`	Read from one tasklist. If `tasklist` is omitted, uses `DEFAULT_TASKLIST` or Google's first list.
Task summaries	`today`, `overdue`, `upcoming`, `search`, `digest`	If `tasklist` is omitted, reads all tasklists and includes tasklist context.
Task mutations	`clear_completed`, `add`, `complete`, `update`, `uncomplete`, `delete`, `move`	Mutate one tasklist/task at a time. `clear_completed` requires `confirm: true`.

All tasklist arguments accept a tasklist ID or exact title. Task title lookup is exact after trimming whitespace and ignores case.

For today, overdue, upcoming, search, and digest, omitting tasklist reads every tasklist. Returned task objects include tasklist_id and tasklist_title; digest labels items with tasklist context.

For list_tasks, clear_completed, single-task tools, and write tools, omitting tasklist uses DEFAULT_TASKLIST, or the first list returned by Google. This prevents unqualified writes from touching every list.

Limitations

These are Google Tasks REST API limits:

Due dates are date-only. Google drops time-of-day values on task due dates.
Recurring tasks cannot be created or read through the Google Tasks REST API.
clear_completed hides completed tasks; it does not permanently delete them.

Docker And VPS

Docker:

docker compose up --build

Keep .env, OAuth JSON files, and SQLite databases outside images and public bundles.

VPS/systemd/Caddy templates are in deploy/:

deploy/caddy/Caddyfile
deploy/systemd/google-tasks-mcp.service

Replace every placeholder domain, path, and user before deploying.

Troubleshooting

Missing bearer token:

HTTP /mcp requires Authorization: Bearer unless OAuth gateway mode is handling the client.
Stdio mode does not use MCP_BEARER_TOKEN.

Google OAuth app is in Testing mode:

Add every bootstrapped Google user as a test user.
Testing-mode refresh tokens can expire after 7 days.

Callback URI mismatch:

GOOGLE_REDIRECT_URI must exactly match an Authorized redirect URI in Google Cloud.
For local web OAuth, use http://127.0.0.1:8787/callback consistently.

Expired or revoked Google refresh token:

For hosted HTTP, open GOOGLE_OAUTH_ONBOARDING_URL and reconnect Google.
For local or recovery use, run google-tasks-mcp-bootstrap ag

只显示了开头部分；其余内容请在仓库中阅读

Google Tasks MCP Server

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

MCP Server Autocad Lisp Helper

作者的 README

Google Tasks MCP Server

What You Get

Choose A Transport

Container persistence

Install

Google Cloud Setup

Bootstrap Google OAuth

Hosted HTTP onboarding

Local and recovery CLI

Start The Server

Connect An MCP Client

Authentication Modes

Tools

Limitations

Docker And VPS

Troubleshooting