Skip to main content
Stay on top of your to-dos by creating, organizing, and updating Google Tasks directly from your workflows. Automate task capture, keep deadlines current, and pull task lists for reporting or daily planning using simple natural language.
Create and manage multiple task lists with titles, notes, due dates, and completion status, all synced across your Google Workspace.

​
What is Google Tasks MCP?

The Google Tasks MCP creates a customized node that understands Google Tasks so you can interact with it using plain language. You describe what you want to do, the AI configures the correct action, and the node returns structured data you can pass to the next step in your workflow.

​
What Can It Do for You?

  • Capture action items into the right list with due dates and notes
  • Keep task lists organized by listing, filtering, and retrieving task details
  • Update task fields like title, due date, and status as work progresses
  • Mark tasks complete and clean up finished items for accurate tracking

​
Available Tools

ToolWhat It DoesExample Use
List Task ListsRetrieves all your task lists”List my task lists and return structured data with name and id”
Find Task ListFinds a task list by name and returns its id”Find the task list matching task list name and return structured data with id and name”
List Tasks in a ListLists tasks within a specific task list, optionally filtered by status or due date”Using task list id task list id, list tasks and return structured data with title, status, due, and id”
Create TaskCreates a new task in a specific list with optional due date and notes”In task list id task list id, create a task titled task title with due date due date and notes notes, and return structured data with id, title, due, status”
Update TaskUpdates fields on an existing task like title and due date”Using task id task id in task list id task list id, update the title to task title and due date to due date, and return structured data with id, title, due, status”
Complete TaskMarks a task as completed”Mark task id task id in task list id task list id as completed and return structured data with id, title, status, completed time”
Delete TaskDeletes a task from a specific list”Delete task id task id from task list id task list id and return structured data confirming deletion”

​
How to Use

1

Create Your Google Tasks MCP Node

Go to your node library, search for Google Tasks, and click “Create a node with AI”
2

Add Your Prompt

Drag the Google Tasks MCP node to your canvas and add your prompt in the text box.
3

Test Your Node

Run the node to see the results. If it works as expected, you’re all set. If you run into issues, check the troubleshooting tips below.
4

Save and Reuse

Once your Google Tasks MCP node is working, save it to your library. You can now use this customized node in any workflow.

​
Example Prompts

Here are some prompts that work well with Google Tasks MCP: Get a Task List ID: “Find the task list matching task list name and return structured data with id and name” Create a Task With Details: “In task list id task list id, create a task titled task title with due date due date and notes notes, and return structured data with id, title, due, status” List Tasks for Planning: “Using task list id task list id, list tasks with status needsAction and return structured data with title, id, due, and notes” Update a Task’s Due Date: “Using task id task id in task list id task list id, update due date to new due date and return structured data with id, title, due, status”
Start simple and keep prompts focused on one action. If a tool needs an id, first create a small node that returns the id using the list or task name, then pass that structured data to the next node.

​
Troubleshooting

If your Google Tasks MCP node is not working as expected, try these best practices:

​
Keep Prompts Simple and Specific

  • Good: “Find the task list matching task list name and return structured data with id and name”
  • Bad: “Find my marketing tasks, update their due dates to next Friday, and then email me a summary”
While the bad example attempts multiple actions at once, prompts work best when focused on a single task. Create separate nodes for each action to keep workflows reliable.

​
Match What Google Tasks Can Do

  • Good: “Using task list id task list id, mark task id task id as completed and return structured data with id and status”
  • Bad: “Post a message to Slack when a task is completed”
Google Tasks MCP focuses on task management. For messaging, pair it with a Slack node in your workflow.

​
Break Complex Tasks Into Steps

Instead of trying to do everything in one prompt (which might cause timeouts or partial outputs): 
Find tasks in `task list name` due in the next `number of days` days, update due dates to `new due date`, and send an email summary to `recipient email`
Break this into smaller, focused nodes that each handle one task:
1

Step 1: Get Task List ID

Find the task list matching task list name and return structured data with id and name
2

Step 2: List Upcoming Tasks

Using task list id task list id, list tasks due in the next number of days days and return structured data with id, title, due
3

Step 3: Update Due Dates

Using task id task id, update the due date to new due date and return structured data with id, title, due, status
Connect these nodes sequentially in your workflow. The task list id output from Step 1 feeds Step 2, and each task id from Step 2 feeds Step 3.

​
Focus on Data Retrieval

Google Tasks MCP is excellent at getting information from Google Tasks. For analysis or content creation, connect it to other nodes. Example:
  • Good prompt: “Using task list id task list id, list tasks with status needsAction and return structured data with title, id, due”
  • Bad prompt: “List tasks and summarize the top priorities in a paragraph”
Use the Ask AI node for summaries or prioritization. Keep Google Tasks prompts centered on retrieving or updating task data.

​
Troubleshooting Node Creation

If you see empty outputs in the node creation window (or if you’ve already created the node, hover over it and click “Edit”), open the chat interface and ask the AI to add debug logs and verify the API response. Mention that you received empty outputs.
In the node creation window (or if you’ve already created the node, hover over it and click “Edit”), describe what you expected versus what you received. The AI will adjust the node based on your feedback.
First click “Fix with Gummie”. If multiple attempts still result in errors, simplify your prompt or contact support.
MCP node creation often benefits from small tweaks. Use the chat interface in the node creation window to refine filters, output fields, or pagination.

​
Need More Help?