A
licenseNot graded
qualityD
maintenanceEnables AI assistants to manage Google Tasks, including listing, creating, updating, deleting, and completing tasks via the Google Tasks API.
89 npm
MIT
mcp-google-tasks
by A1-x-Tech
Related Servers
Alternatives to mcp-google-tasks
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables 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.139 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing Google Tasks through natural language, including listing, creating, completing, deleting, and updating tasks.87 npm1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to securely authenticate with Google Tasks and perform full CRUD operations on task lists and tasks, including moving tasks and clearing completed tasks.52 npm-
TDQS
A4.3/5.0
Scored across 21 tools
Disambiguation4/5
Core tasklist/task tools (list/get/create/update/delete/move/complete/reopen) have clearly distinct purposes and descriptions explicitly distinguish close pairs. However, the six auth/setup tools form a sequence an agent could mix up, and raw_request is a universal escape hatch overlapping every typed tool.
Naming Consistency4/5
All names use snake_case and most follow a verb_noun pattern (get_task, create_tasklist, complete_task). Minor deviations such as auth_status (noun_noun), logout (bare verb), and raw_request (adjective_noun) break the pattern slightly but remain readable.
Tool Count3/5
21 tools is on the heavy side for a single Google Tasks domain; six are OAuth/auth setup tools and raw_request duplicates typed functionality. The core CRUD plus lifecycle set is justified, but the total lands in borderline-heavy territory.
Completeness5/5
Covers full tasklist CRUD, task CRUD and lifecycle (complete, reopen, move, clear completed), auth setup/login/status/logout, and raw_request for uncovered API paths. Missing recurrence or search are API limitations, not surface gaps.
Maintenance
ActivityNo data
ResponsivenessNo issues