Create, track, and manage Google Tasks and task lists directly from your AI workflows. This stateless, multi-tenant MCP server exposes the Google Tasks API for listing, creating, updating, completing, and deleting both tasks and task lists. Mutating tools such as update_task and update_tasklist return both the before and after state of the resource, making it easy to build assistants and automations that manage to-do lists and reminders on a users behalf
Hermes is Nous Research's command-line agent. MCP servers are declared in its YAML config and reloaded without a restart.
This guide connects Google Tasks to Hermes through MewCP, so Hermes can use Google Tasks's 12 tools, like list_task_lists, add_task and get_task, without your Google Tasks credentials ever reaching the app.
Google Tasks signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Work with pages, databases, blocks and collaborative knowledge stored in Notion. Create, update and organize content while building workflows around structured information and documentation.
Todoist enables AI agents to manage personal tasks and projects by creating, searching, updating, completing, and organizing to-do lists, helping users plan and track their work through natural-language instructions.
Linear is a project management and issue-tracking platform used by software and product teams. Its MCP server enables AI assistants to search, create, and update issues, projects, and other work-management objects directly through natural language.
TickTick helps users organize daily work by creating and updating tasks, managing to-do lists, setting due dates and reminders, organizing tasks with tags, and tracking progress across projects and routines.
Other clients
Google Tasks works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Google Tasks tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Edit config.yaml in your Hermes config directory (~/.hermes).
Put this under the top-level "mcp_servers:" key.
Run /reload-mcp in Hermes, or start a fresh session. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
List all task lists accessible by the user. Returns task list IDs, titles, and metadata. Use the task list ID from the response to access tasks within a list.
Create a new task in a specific task list. Provide the task list ID, title, and optional notes and due date. Returns the created task with its assigned ID.
Gets the detail of a specific task from the task list. Returns the full task object including title, notes, due date, status, and position.
Get the task details from the name of the task. Searches a task list for a task by its title and returns the matching task details.
DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently deletes a specific task from the task list. This action is irreversible — the deleted task and all its data cannot be recovered. NEVER call this tool autonomously or as part of an automated flow. You MUST stop, tell the user exactly what will be deleted and that it is permanent, and wait for their explicit written confirmation before proceeding.
Mark a specific task as completed from the task list. Sets the task status to 'completed'. Returns the updated task object.
Updates an existing task. Only the fields you provide are changed — others keep their current value. NOTE: this overwrites the current field values — the original state is not stored after the call. The response includes both the before and after state so you have a full record of what changed.
Create a brand new task list. Returns the created task list with its assigned ID and metadata.
Updates the name of a specific task list. The response includes both the before and after state so you have a full record of what changed.
List all the tasks present in the specific task list. Returns task IDs, titles, statuses, and other metadata for all tasks in the list.
Get the details or metadata of a specific task list. Returns the task list ID, title, and last updated timestamp.
DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently deletes an entire task list with all tasks in it. This action is irreversible — the task list and all its tasks cannot be recovered. NEVER call this tool autonomously or as part of an automated flow. You MUST stop, tell the user exactly what will be deleted and that it is permanent, and wait for their explicit written confirmation before proceeding.
