Google Tasks MCP Server
Google Tasks is Google's to-do list service. The tools list, create, update, move and delete task lists and tasks.
What is the Google Tasks MCP Server?
The Google Tasks MCP server gives AI agents structured, permission-aware access to Google Tasks through the Model Context Protocol. With 12 pre-built actions, agents can read, create, and update Google Tasks data on behalf of authorized users.
Willow ships the Google Tasks MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Google Tasks is being used by every AI agent in your stack.
Tools
List Task Lists
Lists the user's task lists. Use it to find a task list id for the task tools.
Get Task List
Gets one task list by id. Use '@default' for the default list.
Create Task List
Creates a new task list. A user can have up to 2000 lists.
Update Task List
Renames a task list.
Delete Task List
Deletes a task list and every task in it. The default task list can't be deleted.
List Tasks
Lists tasks in a task list. For overdue work, set dueMax to the start of today and showCompleted to false.
Get Task
Gets one task by id.
Create Task
Creates a task. Set parent to make it a subtask, and previous to place it after a sibling.
Update Task
Changes a task's title, notes, due date or status. Only the fields you send change. Set status to completed to finish a task, or needsAction to reopen it.
Move Task
Moves a task under a new parent, after a sibling, or to another task list. Repeating and assigned tasks have limits on nesting and cross-list moves.
Delete Task
Deletes a task. If the task was assigned from Docs or a Chat space, the original task there is deleted too.
Clear Completed Tasks
Hides every completed task in a task list. They stop appearing in List Tasks unless showHidden is true.
Customize Tools
Edit descriptions, modify arguments, select tools, or add new ones
Edit descriptions
Change arguments
Select tools
Set Up Your Google Tasks MCP Server in Minutes
Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.
Claude Desktop
{
"mcpServers": {
"willow-google-tasks": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/google-tasks"
}
}
}Cursor
{
"mcpServers": {
"willow-google-tasks": {
"type": "http",
"url": "https://<org>.mcp-s.com/mcp/mcp/google-tasks"
}
}
}Claude Code
claude mcp add willow-google-tasks --transport http https://<org>.mcp-s.com/mcp/mcp/google-tasksn8n
{
"url": "https://<org>.mcp-s.com/mcp/mcp/google-tasks",
"method": "POST"
}Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.
Enterprise Governance for Google Tasks
Willow adds the layer Google Tasks and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.
Google Tasks MCP Server FAQ
What is the Google Tasks MCP server?
The Google Tasks MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Google Tasks data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.
How is Willow's Google Tasks MCP server different from the official one?
The official Google Tasks MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.
Which AI clients work with the Google Tasks MCP server?
Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.
Is the Google Tasks MCP server secure? How does Willow handle authentication?
Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Google Tasks, nothing more. No credentials reach the LLM. Every action writes to an audit trail.
Can I limit which Google Tasks actions agents can take?
Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.
How do I detect shadow Google Tasks MCP servers in my org?
Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Google Tasks MCP locally, you'll see it.
What does the Google Tasks MCP server cost?
Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.
How do I install the Google Tasks MCP server with Willow?
Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.
Compare Willow MCP Gateway
See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.
Your agents are already in the wild.
Give them a Basecamp. Go from AI chaos to AI work, in minutes.