Google Tasks MCP Server

Google Tasks MCP Server

<!-- mcp-name: io.github.ebmurha/google-tasks-mcp -->

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 MCPSERVERGUIDE.md and DISTRIBUTION.md.

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 MCPBEARERTOKEN. Do not commit .env.

Google Cloud Setup

1. Create or open a Google Cloud project.
2. Enable the Google Tasks API.
3. Configure the OAuth consent screen.
4. 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 GOOGLECLIENTID, GOOGLECLIENTSECRET, and GOOGLEREDIRECTURI

Local-only alternative:

• Application type: Desktop app
• Download the OAuth client JSON outside this repo.
• Set GOOGLEOAUTHKEYS_PATH to that file path.
• Leave GOOGLECLIENTID and GOOGLECLIENTSECRET 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.

GOOGLECLIENTID / GOOGLECLIENTSECRET / GOOGLEOAUTHKEYS_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

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

Shortened. The full README is on GitHub.