
Google Tasks MCP Server
io.github.ebmurhaPublished by GitHub account ebmurhav0.4.0Updated Nov 10, 2026
Manage Google Tasks from MCP-compatible AI clients.
Overview
Self-hosted MCP server that lets an assistant read, search, summarize and modify Google Tasks in your own Google account.
- What you can do
- List, create, get, update and delete tasklists, with confirmation required for deletes
- Read tasks from a tasklist and list tasks
- Summarize work with today, overdue, upcoming, search and digest views across tasklists
- Add, complete, uncomplete, update, delete, move and clear completed tasks
- Run over local stdio or streamable HTTP with bearer-token or optional OAuth gateway auth
- When to use it
- Use it when you want an AI client to triage and edit your Google Tasks — reviewing what is due today or overdue, searching tasks, and creating or completing items — while keeping credentials and data on infrastructure you control.
- Requirements
- Python 3.11 and a local install of the package, or a hosted HTTP deployment. A Google Cloud project with the Tasks API enabled and an OAuth client, set via GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET and GOOGLE_REDIRECT_URI (or a client JSON path). A one-time bootstrap per Google account. HTTP mode needs MCP_BEARER_TOKEN; a persistent DB_PATH is needed for tokens and OAuth state.
Installation
In SourceWeft
- Open Google Tasks MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
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
Generate a bearer token if you will run HTTP mode:
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: setGOOGLE_CLIENT_ID,GOOGLE_CLIENT_SECRET, andGOOGLE_REDIRECT_URI
Local-only alternative:
- Application type: Desktop app
- Download the OAuth client JSON outside this repo.
- Set
GOOGLE_OAUTH_KEYS_PATHto that file path. - Leave
GOOGLE_CLIENT_IDandGOOGLE_CLIENT_SECRETempty unless you want env vars to override the JSON file.
Example .env for a local web OAuth client:
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:
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:
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:
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:
Health check:
Expected response:
Stdio mode:
Configuration check:
Connect An MCP Client
Remote or local HTTP:
For a VPS, replace the URL with your HTTPS endpoint:
Local 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 <token>.
MCP_BEARER_TOKENroutes to accountdefault.- Tokens created with
google-tasks-mcp-create-bearer-tokencan route different clients to differentaccount_idvalues. - 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, andMCP_OAUTH_SIGNING_SECRET. - Set
MCP_OAUTH_RESOURCEto the canonical public MCP URL, or let it default to<issuer>/mcp. - Set
MCP_OAUTH_REDIRECT_URISto the callback URI values accepted by your MCP client. - Set
MCP_OAUTH_ENABLE_DCR=truefor 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. /mcpaccepts 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_PATHis 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.
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_completedhides completed tasks; it does not permanently delete them.
Docker And VPS
Docker:
Keep .env, OAuth JSON files, and SQLite databases outside images and public bundles.
VPS/systemd/Caddy templates are in deploy/:
Replace every placeholder domain, path, and user before deploying.
Troubleshooting
Missing bearer token:
- HTTP
/mcprequiresAuthorization: Bearer <token>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_URImust exactly match an Authorized redirect URI in Google Cloud.- For local web OAuth, use
http://127.0.0.1:8787/callbackconsistently.
Expired or revoked Google refresh token:
- For hosted HTTP, open
GOOGLE_OAUTH_ONBOARDING_URLand reconnect Google. - For local or recovery use, run
google-tasks-mcp-bootstrapagain. - For multi-account mode, include the same
--account-idyou used before.
OAuth MCP client keeps re-authorizing:
- Ensure the server is running a version with persisted MCP OAuth refresh tokens.
- Check that
DB_PATHpoints to persistent storage and survives restarts. - Verify
MCP_OAUTH_ISSUERis the public HTTPS base URL with no trailing slash. - Verify
MCP_OAUTH_RESOURCEmatches the public/mcpURL exactly. - On disposable hosts, verify Litestream restored the SQLite replica before startup.
More Docs
- MCP_SERVER_GUIDE.md explains hosting models, credential boundaries, and public project vs public service choices.
- DISTRIBUTION.md explains registry, bundle, and directory publishing.
- .env.example lists every supported environment variable.
- google-tasks-mcp-specifications.md is the behavioral source of truth.
Tests
Source: README.md at commit 4948e10
Tools
0Version history
1- v0.4.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts