MCP Googletasks MCP Server

Mcp googletasks mcp server lets Claude, Cursor and other MCP clients work with MCP Googletasks directly. A local MCP server for Google Tasks integration with LLMs.

What MCP Googletasks does

This Model Context Protocol (MCP) server provides a bridge between MCP clients and Google Tasks, allowing you to manage your task lists and tasks directly from clients like Claude Desktop, Cursor, and Codex.

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

• Codex — Replace /path/to/google-tasks-mcp with the path to this project, then restart Codex
• Cursor — The Cursor tool exposed by this server

Installing the mcp googletasks mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js 20+ (see package.json engines) - An MCP-compatible client - Google Cloud Project with Tasks API enabled

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Googletasks sits in that group, and the shape of its toolset — Codex, Cursor — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by arpitbatra123, written in TypeScript.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp googletasks mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.