F
licenseB
qualityC
maintenanceConnects Claude to Google Tasks, enabling users to list, create, update, complete, reopen, and delete tasks through natural language.
9
-
google-tasks-mcp
by lorocopey
Related Servers
Alternatives to google-tasks-mcp
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables Claude to create, search, update, and complete tasks in a user's own Google Tasks account through natural language, running self-hosted on the user's machine with guided setup and guarded, approval-aware writes.-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs like Claude to manage Google Tasks by listing, creating, updating, completing, and deleting tasks and task lists, including setting due dates and notes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to view and manage Google Tasks, including lists, tasks, subtasks, due dates, completion, moves, and deletion, through a self-hosted Vercel deployment.4 npm1MIT
- FlicenseAqualityDmaintenanceEnables managing Google Tasks (list, add, complete, delete, update) using natural language commands in Claude Code through an Apps Script webhook.64 npm-
- AlicenseNot gradedqualityBmaintenanceGives Claude seven tools to list, create, update, complete and delete Google Tasks and task lists in your own account, including tasks assigned from Google Docs and Chat. It runs as a remote MCP server you deploy to your own Vercel account, where Claude connects over OAuth with a self-renewing Google sign-in.46 npmMIT
TDQS
A3.9/5.0
Scored across 9 tools
Disambiguation4/5
Each tool targets a distinct resource+action pair, and descriptions explicitly route overlapping cases (e.g. update_task says to use gtasks_complete_task for finishing a task, delete_task says to use complete_task to keep a record). The only real overlap is that update_task can set status, which duplicates complete_task, but the descriptions handle it well.
Naming Consistency5/5
Every tool follows the same gtasks_<verb>_<noun> snake_case pattern (create/delete/list/get/update/complete). No style mixing or inconsistent verb conventions.
Tool Count5/5
Nine tools cleanly cover the domain: three for lists, six for tasks. Each tool earns its place with no redundant or filler operations.
Completeness4/5
Full lifecycle coverage for tasks (create, get, list, update, complete, delete) and near-full for lists (create, list, delete). Minor gaps: no way to rename a task list, and no explicit tools for subtasks, moving/reordering tasks, or clearing completed tasks, though most can be worked around.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues