# arpitbatra123/mcp-googletasks [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/arpitbatra123/mcp-googletasks  
**GitHub Stars:** 48  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/arpitbatra123-mcp-googletasks

## Description
An MCP server to interface with the Google Tasks API

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "mcp-googletasks": {
    "command": "npx",
    "args": ["-y","arpitbatra123-mcp-googletasks"],
    "env": {
      "GOOGLE_CLIENT_ID": "",
      "GOOGLE_CLIENT_SECRET": "",
      "GOOGLE_REDIRECT_URI": ""
    }
  }
}
```

**Requires environment variables:** `GOOGLE_CLIENT_ID`, `GOOGLE_CLIENT_SECRET`, `GOOGLE_REDIRECT_URI` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What arpitbatra123/mcp-googletasks MCP server does

The arpitbatra123/mcp-googletasks MCP server exposes Google Tasks operations through the Model Context Protocol. It supports both task lists and the tasks inside them, allowing an MCP-compatible client to inspect and change Google Tasks data through tool calls.

Task-list operations include listing all lists, retrieving one list, creating a list, changing a list, and deleting a list. Task operations cover listing tasks with paginated results, retrieving individual tasks, creating and updating tasks, deleting tasks, marking tasks complete, clearing completed tasks, and moving tasks. Moving a task can reorder it, change its parent, or transfer it between task lists.

## How it works

The server runs locally as a Node.js application and communicates with an MCP client such as Claude Desktop, Cursor, or Codex. It uses the Google Tasks API as the backend and requires a Google Cloud project with that API enabled.

Authentication uses Google OAuth. On first use, call the `authenticate` tool to obtain an authorization URL, approve access in a browser, then provide the returned code to the `set-auth-code` tool. OAuth access and refresh credentials are saved at `~/.config/google-tasks-mcp/credentials.json` with restricted file permissions. The saved refresh token allows the server to renew expired access tokens without requiring another login, unless access is revoked or the credentials file is removed.

The arpitbatra123/mcp-googletasks MCP server validates required configuration at startup and validates tool inputs, including identifier formats, string lengths, and RFC 3339 dates. It also supports graceful shutdown and sanitizes OAuth callback responses.

## Setup and configuration

Use Node.js 20 or newer. Before starting the arpitbatra123/mcp-googletasks MCP server, create a Google Cloud project, enable the Google Tasks API, configure the OAuth consent screen, and create a Web application OAuth client. The redirect URI should be `http://localhost:3000/oauth2callback` unless a different value is configured.

Set these environment variables:

- `GOOGLE_CLIENT_ID` — required Google OAuth client ID.
- `GOOGLE_CLIENT_SECRET` — required Google OAuth client secret.
- `GOOGLE_REDIRECT_URI` — optional callback URI; it defaults to `http://localhost:3000/oauth2callback`.

Install the project dependencies with `npm install`, then compile it with `npm run build`. Configure the MCP client to launch the resulting `build/index.js` file with Node.js. The README provides separate configuration examples for Codex and Claude Desktop, including the platform-specific Claude configuration paths.

## Tools and capabilities

The listed tools are:

- `list-tasklists`, `get-tasklist`, `create-tasklist`, `update-tasklist`, and `delete-tasklist` for task-list administration.
- `list-tasks`, `get-task`, `create-task`, `update-task`, and `delete-task` for task records.
- `complete-task` for marking a task complete.
- `move-task` for reordering, reparenting, or moving tasks between lists.
- `clear-completed-tasks` for removing completed tasks from a list.
- `authenticate` and `set-auth-code` for completing the initial OAuth flow.

## Limitations and notes

This project requires a Google Cloud project, enabled Google Tasks API, configured OAuth credentials, and an MCP-compatible client. The README describes the software as intended for demonstration purposes and says to use it at your own risk. Authentication tokens are stored locally, so deployment and file-system access should be considered when choosing where to run it. Codex is documented as a supported client, but it is not included in the directory's compatible-client list.

_Full upstream README: https://allmcps.com/mcp/arpitbatra123-mcp-googletasks/readme_