Google Tasks

What is gtasks-mcp?

gtasks-mcp is a Google Tasks Model Context Protocol (MCP) server designed to integrate with Google Tasks. It allows users to manage their Google Tasks programmatically, enabling operations like listing, reading, searching, creating, updating, and deleting tasks. It is built with TypeScript and can be integrated with applications like Claude Desktop via Smithery.

How to use gtasks-mcp?

To use gtasks-mcp, you need to set up a Google Cloud project, enable the Google Tasks API, configure an OAuth consent screen, and create an OAuth Client ID. The client ID JSON file should be renamed to gcp-oauth.keys.json and placed in the root of the repository. The server can be built using npm run build or npm run watch. For automatic installation with Claude Desktop, you can use Smithery via npx -y @smithery/cli install @zcaceres/gtasks --client claude. Authentication is done by running the server with the auth argument (npm run start auth), which opens a browser for the OAuth flow. Credentials are saved in .gdrive-server-credentials.json. For desktop app integration, you need to add a specific JSON configuration to your app's server configuration, pointing to the compiled index.js file.

Key Features of gtasks-mcp

• Comprehensive Task Management: Supports all CRUD (Create, Read, Update, Delete) operations for Google Tasks.
• Search Functionality: Allows searching for tasks based on a query.
• Pagination: The list tool supports pagination using a cursor.
• Task Clearing: Provides a tool to clear completed tasks from a task list.
• Resource Access: Offers direct access to Google Tasks resources, representing individual tasks.
• Integration with Smithery: Simplifies installation and integration with compatible clients like Claude Desktop.
• OAuth2 Authentication: Securely authenticates with Google Tasks API.

Use Cases of gtasks-mcp

• Automated Task Management: Develop scripts or applications to automatically manage Google Tasks based on specific triggers or schedules.
• Custom Task Interfaces: Build custom user interfaces or dashboards that interact with Google Tasks.
• Integration with AI Assistants: Enable AI assistants (like Claude) to understand and manipulate Google Tasks, allowing for natural language task management.
• Workflow Automation: Integrate Google Tasks into broader workflow automation systems.
• Data Synchronization: Synchronize tasks between Google Tasks and other task management systems.

FAQ from gtasks-mcp

• How do I set up Google Cloud for gtasks-mcp?
  • Create a new Google Cloud project.
  • Enable the Google Tasks API.
  • Configure an OAuth consent screen.
  • Create an OAuth Client ID for "Desktop App".
  • Download the JSON key file and rename it to gcp-oauth.keys.json in the repo root.
• How do I install gtasks-mcp via Smithery?
  • Run npx -y @smithery/cli install @zcaceres/gtasks --client claude.
• How do I authenticate gtasks-mcp?
  • Run npm run start auth and complete the authentication flow in your browser. Credentials will be saved in .gdrive-server-credentials.json.
• What are the available tools in gtasks-mcp?
  • search: Search for tasks.
  • list: List all tasks.
  • create: Create a new task.
  • update: Update an existing task.
  • delete: Delete a task.
  • clear: Clear completed tasks.
• What resources does gtasks-mcp provide access to?
  • Individual Google Tasks, accessible via gtasks:///<task_id>.

Google Tasks MCP Server

This MCP server integrates with Google Tasks to allow listing, reading, searching, creating, updating, and deleting tasks.

Components

Tools

• search

  • Search for tasks in Google Tasks
  • Input: query (string): Search query
  • Returns matching tasks with details

• list

  • List all tasks in Google Tasks
  • Optional input: cursor (string): Cursor for pagination
  • Returns a list of all tasks

• create

  • Create a new task in Google Tasks
  • Input:
    • taskListId (string, optional): Task list ID
    • title (string, required): Task title
    • notes (string, optional): Task notes
    • due (string, optional): Due date
  • Returns confirmation of task creation

• update

  • Update an existing task in Google Tasks
  • Input:
    • taskListId (string, optional): Task list ID
    • id (string, required): Task ID
    • uri (string, required): Task URI
    • title (string, optional): New task title
    • notes (string, optional): New task notes
    • status (string, optional): New task status ("needsAction" or "completed")
    • due (string, optional): New due date
  • Returns confirmation of task update

• delete

  • Delete a task in Google Tasks
  • Input:
    • taskListId (string, required): Task list ID
    • id (string, required): Task ID
  • Returns confirmation of task deletion

• clear

  • Clear completed tasks from a Google Tasks task list
  • Input: taskListId (string, required): Task list ID
  • Returns confirmation of cleared tasks

Resources

The server provides access to Google Tasks resources:

• Tasks (gtasks:///<task_id>)
  • Represents individual tasks in Google Tasks
  • Supports reading task details including title, status, due date, notes, and other metadata
  • Can be listed, read, created, updated, and deleted using the provided tools

Getting started

1. Create a new Google Cloud project
2. Enable the Google Tasks API
3. Configure an OAuth consent screen ("internal" is fine for testing)
4. Add scopes https://www.googleapis.com/auth/tasks
5. Create an OAuth Client ID for application type "Desktop App"
6. Download the JSON file of your client's OAuth keys
7. Rename the key file to gcp-oauth.keys.json and place into the root of this repo (i.e. gcp-oauth.keys.json)

Make sure to build the server with either npm run build or npm run watch.

Installing via Smithery

To install Google Tasks Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @zcaceres/gtasks --client claude

Authentication

To authenticate and save credentials:

1. Run the server with the auth argument: npm run start auth
2. This will open an authentication flow in your system browser
3. Complete the authentication process
4. Credentials will be saved in the root of this repo (i.e. .gdrive-server-credentials.json)

Usage with Desktop App

To integrate this server with the desktop app, add the following to your app's server configuration:

{
  "mcpServers": {
    "gtasks": {
      "command": "/opt/homebrew/bin/node",
      "args": [
        "{ABSOLUTE PATH TO FILE HERE}/dist/index.js"
      ]
    }
  }
}