Google Tasks
Google Tasks provides a simple to-do list and task management system integrated into Gmail and Google Calendar for quick and easy tracking
Verdict
Common use cases
- Add meeting action items to shared list
- Check sprint backlog during standup
- Mark completed tasks without switching apps
- Create subtasks while discussing implementation
- Archive finished lists after project wrap
Integration
- Vendor
- Google Tasks
- Category
- other
- Auth
- OAUTH2
- Tools
- 14
- Composio slug
googletasks
Tools
- Clear tasks
Permanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent.
- Create a task list
Creates a new task list with the specified title.
- Delete taskdestructive
Deletes a specified task from a given task list in google tasks.
- Delete task listdestructive
Permanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible.
- Get Task
Use to retrieve a specific google task if its `task id` and parent `tasklist id` are known.
- Get task list
Retrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user.
- Insert Task
Creates a new task in a given `tasklist id`, optionally as a subtask of an existing `task parent` or positioned after an existing `task previous` sibling, where both `task parent` and `task previous` must belong to the same `tasklist id` if
- List task lists
Fetches the authenticated user's task lists from google tasks; results may be paginated.
- List Tasks
Retrieves tasks from a google tasks list; all date/time strings must be rfc3339 utc, and `showcompleted` must be true if `completedmin` or `completedmax` are specified.
- Move Task
Moves the specified task to another position in the destination task list.
- Patch Task
Partially updates an existing task (identified by `task id`) within a specific google task list (identified by `tasklist id`), modifying only the provided attributes from `taskinput` (e.g., `title`, `notes`, `due` date, `status`) and requir
- Patch task list
Updates the title of an existing google tasks task list.
- Update Task
Updates the specified task.
- Update Task List
Updates the authenticated user's specified task list.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Find Google Tasks in the MCP directory and click Connect. 3. You'll redirect to Google's OAuth consent screen—sign in with the account that owns the task lists you want to access. 4. Grant permission for Switchy to view and manage your Google Tasks (the scope includes read, write, and delete). 5. Google redirects you back to Switchy with a success message. 6. Open any Space, type '@Google Tasks list task lists' and send—you should see your task lists appear in the response. 7. To create a task, try '@Google Tasks insert task' followed by the list ID and task title. 8. If the connection fails, check that third-party app access is enabled in your Google account security settings.
What teammates see: by default, memories from Google Tasks are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Show My Task Lists
@Google Tasks list all my task lists so we can decide which one to update during this meeting.Open in a Space →
Add Action Item
@Google Tasks create a task in the 'Sprint 12' list with the title 'Review PR #847 before Friday standup'.Open in a Space →
Check Task Details
@Google Tasks get the task with ID abc123 from the 'Marketing' list and show me its due date and notes.Open in a Space →
Mark Task Complete
@Google Tasks mark task xyz789 in the 'Q1 Goals' list as completed now that we've shipped the feature.Open in a Space →
Clear Finished Tasks
@Google Tasks clear all completed tasks from the 'Launch Checklist' list since the project is wrapped.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Google Tasks show me all my task lists and tell me which one has the most incomplete tasks
I found 4 task lists in your Google Tasks account: 'Work Projects' (12 incomplete tasks), 'Personal Errands' (7 incomplete), 'Team Onboarding' (3 incomplete), and 'Reading List' (18 incomplete). Your 'Reading List' has the most outstanding items at 18 tasks. This example illustrates fetching all lists and synthesizing a count-based comparison across them.
This read-heavy example shows the MCP retrieving task lists and the AI reasoning over the results. Requires OAuth scope for read access to Google Tasks. The MCP returns list metadata; the AI infers task counts from subsequent queries or list properties—actual count accuracy depends on API pagination and task completion states at query time.
@Google Tasks create a new task in my 'Work Projects' list called 'Review Q1 budget deck' with a due date of next Friday
I've created the task 'Review Q1 budget deck' in your 'Work Projects' list with a due date of March 14, 2025. The task ID is `MTIzNDU2Nzg5MA` and it's now visible in your Google Tasks app. This example demonstrates creating a task with a title, parent list, and due date in a single action.
This write example shows task creation with metadata. Requires OAuth scope for write access. The MCP accepts ISO 8601 date formats; the AI translates 'next Friday' into the correct date. Side-effect: the task immediately appears in the user's Google Tasks across all synced devices. Task IDs are opaque strings returned by the API.
@Google Tasks look at my 'Team Onboarding' list and draft a status email summarizing what's done versus what's still pending
Based on your 'Team Onboarding' list: **Completed (3 tasks):** Set up Slack account, Send welcome email, Schedule 1:1 with manager. **Pending (2 tasks):** Complete compliance training (due tomorrow), Submit I-9 documents (due in 3 days). This example shows the MCP fetching task details and the AI synthesizing them into a stakeholder-ready summary format.
This synthesis example pairs the MCP's read capability with the AI's summarization. The MCP retrieves task titles, completion status, and due dates; the AI structures them into an email draft. Useful for status updates or handoff documentation. Note that task ordering and subtask hierarchies are preserved in the API response, so nested tasks can be reflected in the summary.
Use-case deep-dives
When Google Tasks beats project tools for external handoffs
A 6-person creative agency uses Switchy to manage client deliverables that live outside their internal project tracker. The Google Tasks MCP shines here because clients already use Gmail and Tasks—no onboarding friction. The team creates one task list per active client, uses Insert Task to log deliverable milestones during kickoff calls, and pulls Get Task during status syncs to confirm what's overdue. The OAuth2 flow means each account manager authenticates once and Switchy handles the rest. This setup breaks down if you need dependency chains or Gantt views; past 15 active clients, the List task lists call gets noisy and you'll want a dedicated PM tool. For agencies under that threshold doing simple milestone tracking with non-technical clients, this MCP closes the loop without forcing clients into Asana.
Why this MCP works for hybrid personal-team workflows
A 3-person startup uses Google Tasks for individual to-dos and Switchy for shared context. During daily standups, the founder asks Switchy to pull tasks from each person's default list using Get Task and List task lists, then verbally reassigns blockers. The team uses Create a task list to spin up ad-hoc lists for one-off projects like conference prep or hiring sprints. The 14-tool scope is overkill for pure personal use, but the real win is OAuth2 letting each person authenticate their own Google account—no shared credentials, no manual export-import dance. This stops working around 8-10 people when you need structured sprint planning or burn-down charts. For tiny teams where everyone juggles personal and shared work in the same standup, this MCP keeps Google Tasks in the loop without migrating to a heavier tool.
When to route support actions into Google Tasks via Switchy
A 5-person SaaS support team uses Switchy to summarize Zendesk threads and route follow-ups. The Google Tasks MCP handles the last mile: after Switchy drafts a response, it calls Insert Task to log manual follow-ups like "check staging deploy for customer X" in the on-call engineer's personal task list. The team uses Clear tasks weekly to archive completed items and Delete task when a ticket gets escalated to Jira. The OAuth2 setup means each support rep's tasks stay in their own Google account, visible in Gmail's sidebar during email triage. This pattern falls apart if you need SLA tracking or task dependencies—past 20 follow-ups per day, you'll want a proper ticketing system's task layer. For small support teams doing under 50 tickets weekly where follow-ups are lightweight and personal, this MCP bridges Switchy's context into the tools reps already live in.
Frequently asked
What does the Google Tasks MCP do in Switchy?
It connects your Google Tasks account so AI agents can read, create, update, and delete tasks and task lists on your behalf. The MCP exposes 14 tools covering the full lifecycle — from listing task lists and retrieving individual tasks to clearing completed items and permanently deleting lists. Agents can also create subtasks and position tasks relative to siblings.
Which OAuth scopes does the Google Tasks MCP request?
Google Tasks uses OAuth2, and the MCP requests the tasks.readonly scope (to read lists and tasks) plus tasks scope (to create, update, delete, and clear tasks). You'll authenticate through Google's standard consent screen. No admin access is required — any Google account with Tasks enabled can connect.
Can the MCP manage task due dates and reminders?
Yes for due dates — the Insert Task and update tools accept a due field in RFC 3339 format. Reminders are not exposed by the Google Tasks API itself, so the MCP cannot set or modify them. If you need reminder logic, handle that in your agent's workflow or use Google Calendar MCP alongside.
How does this compare to using the Google Tasks app directly?
The MCP is faster for bulk operations — an agent can create twenty tasks in one conversation instead of you tapping through the mobile UI. You lose the visual drag-and-drop reordering and the native reminder notifications. Use the MCP when you want programmatic task management; use the app for quick manual edits.
Who on the team should connect the Google Tasks MCP?
Whoever owns the task lists you want agents to access. Google Tasks is per-user, not shared like Asana or Monday, so each team member needs their own connection if they want agents acting on their personal lists. One connection cannot read another user's tasks.