Skip to main content

Set up the Google Tasks MCP server

The Google Tasks MCP server gives AI agents access to Google Tasks: reading, creating, updating, completing, and organizing tasks and task lists. This guide covers enabling the Google Tasks API, creating an OAuth client in Google Cloud, and connecting the server to MintMCP.

Prerequisites​

  • A MintMCP admin account
  • A Google Cloud project with permission to enable APIs and create OAuth credentials

Enable the Google Tasks API​

  1. Go to console.cloud.google.com and select or create a project.
  2. Go to APIs & Services → Library, search for Google Tasks API, and click Enable.

Google requires a configured OAuth consent screen before you can create credentials.

  1. Go to console.cloud.google.com/auth/audience for your project.
  2. Set the User type that fits your organization and click Create.
  3. Fill in the required fields: App name (for example, MintMCP Google Tasks), User support email, and Developer contact information.
  4. Click Save and continue through the Scopes and Test users pages.

Create the OAuth client​

The OAuth client gives MintMCP a Client ID and secret to broker each user's Google sign-in. Create one Web application client and point its redirect URI at MintMCP's callback.

  1. Go to console.cloud.google.com/auth/clients and click Create client.

  2. Set Application type to Web application and give it a name (for example, MintMCP Google Tasks). The name only identifies the client in the console.

    Create OAuth client ID form with application type set to Web application and a name field

  3. Under Authorized redirect URIs, click Add URI and enter MintMCP's callback URL:

    https://app.mintmcp.com/oauth/callback
    Authorized redirect URIs field set to the MintMCP OAuth callback URL

  4. Click Create. Google shows the Client ID and Client secret once; copy both now because you can't view the secret again after closing the dialog.

    OAuth client created dialog showing the Client ID and Client secret

Reopen the client anytime from the Clients list to edit its redirect URIs or rotate the secret.

OAuth client detail page showing Client ID, redirect URIs, and the client secret with rotation options

Add Google Tasks to MintMCP​

  1. In MintMCP, go to MCP store → Manage store.
  2. Find the Google Tasks connector, marked Recommended, and click to install it.
  3. Enter the Client ID and Client Secret from the OAuth client you created.
  4. Click Install.

The first time a user calls a tool, MintMCP directs them to sign in with Google and consent to the Tasks scope. MintMCP stores and refreshes their token automatically on every subsequent call.

Scope reference​

CapabilityScope
Sign-in and account identificationopenid, .../userinfo.email, .../userinfo.profile
Create, read, update, and delete tasks and task lists.../tasks

All scopes use the https://www.googleapis.com/auth/ prefix.

Security considerations​

  • Each user authenticates individually through OAuth, so tool calls run under that user's own Google Tasks access.
  • The tasks scope grants read and write access to all of the user's task lists and tasks.
  • Keep the client secret secure: anyone with it can impersonate the app and request access to users' Tasks data.

Troubleshooting​

  • Sign-in fails with redirect_uri_mismatch. The redirect URI on the Google Cloud OAuth client doesn't match MintMCP's callback. Open the OAuth client, confirm Authorized redirect URIs contains https://app.mintmcp.com/oauth/callback exactly, and save. Changes can take a few minutes to take effect.
  • Sign-in is blocked before the consent screen appears. The OAuth consent screen is still in Testing status, so only accounts added as test users can sign in. Go to console.cloud.google.com/auth/audience and publish the app.

Next steps​