Use Claude with Google Tasks through MCP to list tasks, search by intent, create new follow-ups, and clean up completed items. Compare the current Google Tasks MCP options and copy a starter config.
Connect Claude to Google Tasks with MCP
If your goal is “let Claude review my task lists, find overdue work, and create follow-ups in Google Tasks,” this is the shortest path.
Recommended MCP servers for this use case
| Server | Best for | Not ideal when | Auth | Permission risk |
|---|---|---|---|---|
| MCP Google Tasks Server | Explicit env-based config, task-list management, and direct Claude Desktop setup | You want persisted auth without session-style re-auth | OAuth client ID / secret env vars | Medium |
| GTasks MCP | Lightweight Google Tasks integration with search and CRUD tools | You want Gmail or Calendar in the same server | Desktop OAuth app file | Medium |
| Connect Claude to Google Workspace with MCP | Deciding between broader Workspace coverage and task-only setup | You already know Tasks is the only requirement | Mixed | Medium |
Quick selection (30 seconds)
- Pick MCP Google Tasks Server if you want a straightforward Claude Desktop env-var setup.
- Pick GTasks MCP if you want a narrower Tasks-only integration path with a simple Desktop app config.
- Do not choose a broader Workspace server if all you need is task CRUD.
Copy-paste config (Claude Desktop)
{
"mcpServers": {
"google-tasks": {
"command": "node",
"args": [
"/absolute/path/to/google-tasks-mcp/build/index.js"
],
"env": {
"GOOGLE_CLIENT_ID": "your_client_id_here",
"GOOGLE_CLIENT_SECRET": "your_client_secret_here",
"GOOGLE_REDIRECT_URI": "http://localhost:3000/oauth2callback"
}
}
}
}If you prefer the gtasks-mcp route, its Desktop config can call the built dist/index.js directly after OAuth setup.
Tasks auth checklist
| Item | Required | Sensitive | Notes |
|---|---|---|---|
| Google Tasks API enabled | Yes | No | Required before either server can authenticate |
| OAuth client ID / secret or key file | Yes | Yes | Format depends on the server you choose |
| Redirect URI | Yes | Yes | Must match the OAuth client config exactly |
| Built local server path | Yes for local installs | No | Needed if you do not use a published package |
First tool-call prompts
- “List all open tasks and group them by overdue, due soon, and later.”
- “Search my tasks for anything related to onboarding and summarize the blockers.”
- “Create three follow-up tasks from this meeting summary and place them in my default list.”
Risk and permission notes
- Task access is lower risk than inbox or calendar access, but it still reveals priorities, commitments, and sometimes internal project names.
- Start with list and search workflows before allowing task creation or deletion.
- If the server re-authenticates often, document that friction clearly so it does not look like a broken setup.
FAQ
Which Google Tasks MCP option should I start with?
Start with MCP Google Tasks Server if you want the clearest env-based setup, or GTasks MCP if you prefer a narrower Tasks-only integration.
Is Google Tasks MCP safer than Gmail MCP?
Usually yes, because the data is narrower and less likely to contain full private conversations or attachments.
What is the fastest way to reduce risk?
Use Tasks-only OAuth scopes, start with read-heavy prompts, and test creation workflows in a non-critical task list first.
Related pages
Sources and freshness
- Sources: official server pages linked above.
- Updated: March 15, 2026.