mcp-google-tasks
Related Servers
Alternatives to mcp-google-tasks
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Google Tasks, including listing, creating, updating, deleting, and completing tasks via the Google Tasks API.52 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read and manage a user's Google Tasks, including creating, editing, completing, moving, and deleting tasks and task lists via the Google Tasks API.14MIT
- 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 AI assistants to manage Google Tasks through natural language interactions. Supports creating, updating, deleting, searching, and listing tasks with secure OAuth2 authentication.115 npm10MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to read and manage task lists and tasks through Google's official API, with search, digests, pagination, scoped OAuth, and optional read-only or write access.17MIT
- FlicenseNot gradedqualityDmaintenanceEnables managing Google Tasks through natural language, including listing, creating, completing, deleting, and updating tasks.1-
TDQS
Scored across 21 tools
Each tool targets a distinct resource+action, and the descriptions actively cross-reference each other to prevent misselection (update_task explicitly excludes status/reorder, delete_task vs complete_task vs clear_completed_tasks are carefully separated). The only potential overlap is raw_request vs the typed tools, but it is clearly framed as a last-resort escape hatch. Auth tools map to discrete steps of a single OAuth flow rather than duplicating each other.
Overwhelmingly consistent snake_case verb_noun: list_tasklists, get_tasklist, create_task, update_task, move_task, delete_task, complete_task, reopen_task, clear_completed_tasks. Minor deviations exist in the auth group (auth_status, setup_instructions are noun phrases, logout is a bare verb), but they remain readable and predictable. Nothing is ambiguous or chaotically styled.
21 tools is heavy for a task-list domain, largely because six tools are dedicated to an in-chat OAuth flow (set_client, setup_instructions, start_login, finish_login, auth_status, logout) rather than the tasks API itself. Each auth tool is defensible given the stated credential UX, but the overall surface is broader than the core purpose warrants. The 14 task/list tools are reasonably scoped.
Full lifecycle coverage: CRUD for lists and tasks, hierarchy/reorder via move_task, reversible completion (complete_task/reopen_task), bulk clear_completed_tasks, deletion with soft-delete visibility, and raw_request as an escape hatch for uncovered API shapes. Remaining gaps are mostly API limitations (no recurrence, no search) but there is no bulk delete of open tasks and no cross-list task query.