Google Tasks MCP Server

Personal MCP server exposing Google Tasks as tools for Claude Code.

Tools

• list_task_lists

• list_tasks (taskListId, includeCompleted?)

• create_task (taskListId, title, notes?, due?)

• complete_task (taskListId, taskId)

• delete_task (taskListId, taskId)

• update_task (taskListId, taskId, title?, notes?, due?)

Setup

1. Install dependencies (already done if you just built this):

   npm install
   npm run build

2. Create .env in this folder (copy .env.example) with the OAuth client credentials from your existing Google Cloud project (the one with the Google Tasks API enabled):

   GOOGLE_TASKS_CLIENT_ID=...
   GOOGLE_TASKS_CLIENT_SECRET=...

   Make sure http://localhost:53682/oauth2callback is registered as an authorized redirect URI on that OAuth client in Google Cloud Console (APIs & Services > Credentials > your OAuth client > Authorized redirect URIs).

3. Run the one-time interactive auth flow:

   npm run auth

   This opens a URL for you to authorize in the browser, then saves a refresh token to token.json in this folder. Only needs to be done once (tokens auto-refresh after that).

4. Register the server with Claude Code:

   claude mcp add google-tasks "C:\Users\Pedro\.google-tasks-mcp\google-tasks-mcp.cmd"

Notes

• .env and token.json hold secrets — never commit or share them.

• If the server errors with "No token file found", re-run npm run auth.