Skip to content
Google Tasks logo

Google Tasks MCP server

Task list management application

Google Tasks is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
Auth
OAuth 2.0
License
MIT, open source
Updated
September 2026

About the Google Tasks MCP server

Connect Google Tasks once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Google Tasks and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Google Tasks tools your AI can run

Once connected, your assistant can call any of these Google Tasks actions by asking in plain language.

  • Add Task

    Add a new task to a specified task list

    5 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Google Tasks events your agent can watch

These start a run the moment something happens in Google Tasks, so work gets picked up on its own.

  • New Task

    Triggers when a task is created

    1 field

Give your assistant Google Tasks

Connect Google Tasks once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Google Tasks MCP, answered.

No. That is the point of it. One Activepieces server exposes Google Tasks alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Google Tasks in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Add Task, Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.