A
licenseA
qualityC
maintenanceAn MCP server for Google Tasks with full API support including task-list CRUD, task CRUD, reordering, and a diff_tasks change-harvester that detects hidden completions.
13
55 npm
MIT
google-tasks-mcp
by oskarengl
Related Servers
Alternatives to google-tasks-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the Google Tasks API that enables AI agents to read, create, update, delete, and manage Google Tasks.55 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that connects MCP-compatible clients to Google Tasks, enabling reading, searching, creating, completing, updating, deleting, and moving tasks via 19 tools.2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceGoogle Tasks MCP Server is a local MCP server that provides AI agents with full, granular access to the Google Tasks API.1-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage Google Tasks, including creating, updating, deleting, and listing tasks and task lists, with optional due dates and subtasks.55 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides an MCP interface to Google Tasks, enabling reading, creating, updating, and completing tasks and task lists, with support for date filtering to generate weekly reports.55 npmMIT
TDQS
A4/5.0
Scored across 14 tools
Disambiguation5/5
Each tool targets a distinct action and resource: list vs. get vs. search vs. create vs. update vs. complete vs. move vs. delete are clearly separated. The batch create_tasks and completion helpers are explicitly distinguished from their single counterparts, leaving no ambiguity.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern (list_task_lists, create_task, update_task, etc.). The plural variants like create_tasks and complete_tasks are predictable, and clear_completed is the only slight deviation but still uses a verb+noun form.
Tool Count5/5
14 tools is well within the ideal 3-15 range for a domain-specific server. Each tool covers a necessary operation on tasks or task lists without unnecessary bloat or redundancy.
Completeness4/5
The surface covers the core lifecycle of tasks and lists thoroughly: create, read, update, delete, complete, move, and search. Minor gaps exist, such as no way to rename a task list or explicitly filter tasks by completion status via list_tasks, but these are workable and do not severely impact typical usage.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive