A
licenseNot graded
qualityD
maintenanceEnables AI assistants to manage Google Tasks, including listing, creating, updating, deleting, and completing tasks via the Google Tasks API.
39 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 gradedqualityAmaintenanceEnables AI assistants to manage Google Tasks through natural language interactions. Supports creating, updating, deleting, searching, and listing tasks with secure OAuth2 authentication.95 npm10MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing Google Tasks through natural language, including listing, creating, completing, deleting, and updating tasks.62 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.25 npm-
TDQS
A4.7/5.0
Scored across 15 tools
Disambiguation5/5
Each tool targets a distinct action and resource: list vs. single, list-level vs. task-level, mutation vs. completion vs. movement. The descriptions reinforce boundaries, such as update_task explicitly deferring status changes to complete_task/reopen_task and reordering to move_task, so an agent should not misselect.
Naming Consistency5/5
Tool names consistently follow a verb-first snake_case pattern (get_, list_, create_, update_, delete_, move_, complete_, reopen_, clear_). The naming is predictable across both task lists and tasks, with raw_request as the only deliberate outlier that clearly signals its escape-hatch role.
Tool Count5/5
15 tools is at the upper bound but not inflated: the server covers both task lists and tasks, including lifecycle, completion state, reordering, and clearing. Every typed tool maps to a meaningful Google Tasks API operation, and raw_request handles edge cases without adding redundant surface.
Completeness5/5
The surface covers full CRUD for both task lists and tasks, plus task-specific operations: completion, reopen, move, and clear completed. The raw_request escape hatch fills any remaining API gaps, and stated limitations are API constraints rather than missing tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues