Google Tasks MCP Server

What is Google Tasks MCP Server?

This Model Context Protocol (MCP) server bridges MCP clients (such as Claude Desktop, Cursor, and Codex) with Google Tasks, enabling users to manage task lists and tasks directly from the client.

How to use Google Tasks MCP Server?

Install dependencies with npm install, build with npm run build, then configure your MCP client (e.g., Claude Desktop or Codex) with the path to the built server. Authenticate once via the authenticate tool (get a URL, log in, and use set-auth-code with the returned code); credentials are saved automatically.

Key features of Google Tasks MCP Server

• Full CRUD on task lists (create, read, update, delete)
• Full CRUD on tasks plus complete, move, and clear completed
• Persistent OAuth token storage and automatic token refresh
• Startup validation of required environment variables
• HTML‑sanitized OAuth callback responses
• Graceful shutdown on SIGINT/SIGTERM
• Configurable OAuth redirect URI

Use cases of Google Tasks MCP Server

• Manage tasks and task lists from Claude Desktop without leaving the chat
• Automate task creation or updates during coding sessions in Cursor or Codex
• Move tasks between lists or reorder them via a single AI prompt
• Clear completed tasks from a list in one step

FAQ from Google Tasks MCP Server

What OAuth setup is required?

You must create a Google Cloud project, enable the Tasks API, and generate an OAuth 2.0 Client ID with a redirect URI of http://localhost:3000/oauth2callback. The client ID and secret are passed as environment variables.

How does authentication work?

Use the authenticate tool to get an authorization URL, visit it in a browser, approve access, and then call set-auth-code with the code displayed. The server saves tokens to ~/.config/google-tasks-mcp/credentials.json and automatically refreshes expired access tokens.

What are the runtime requirements?

Node.js 20+, an MCP‑compatible client, and a Google Cloud project with the Tasks API enabled.

Does the server persist authentication across restarts?

Yes. Credentials are saved to disk with restricted permissions (600) and refreshed automatically, so you only need to authenticate once unless you revoke access or delete the file.

How do I configure the server for Claude Desktop?

Add a google-tasks entry under mcpServers in the Claude configuration file (claude_desktop_config.json) with command: "node" and args: ["/path/to/google-tasks-mcp/build/index.js"]. Then restart Claude Desktop.