google-tasks-mcp
Related Servers
Alternatives to google-tasks-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Google Tasks that enables reading, creating, editing, completing, reordering, and deleting tasks via the Google Tasks API.1418 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that connects MCP-compatible clients to Google Tasks, enabling reading, searching, creating, completing, updating, deleting, and moving tasks via 19 tools.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA self-hosted streamable-HTTP MCP server that wraps the full Google Tasks API v1, letting clients list, create, update, complete, move, search, and clear task lists and tasks using OAuth refresh-token authentication. It also adds date conveniences such as today's and due-soon tasks, with structured error codes and no local state.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for the Google Tasks API that enables AI agents to read, create, update, delete, and manage Google Tasks.46 npmMIT
- FlicenseNot gradedqualityDmaintenanceGoogle Tasks MCP Server is a local MCP server that provides AI agents with full, granular access to the Google Tasks API.1-
- AlicenseAqualityDmaintenanceA small MCP server for read-write access to Google Tasks, Calendar, and Drive, enforcing human approval for all mutating operations.1MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action. Even complete_task is clearly described as a shorthand for update_task, so no ambiguity. All tools have clear boundaries.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_tasklists, create_task, delete_task). No mixing of conventions or inconsistent verb styles.
13 tools is well-scoped for a task management domain, covering CRUD for tasklists and tasks, plus specialized actions like complete, move, and diff. Each tool earns its place.
The tool set provides complete lifecycle coverage: CRUD for tasklists and tasks, marking complete, reordering, subtask creation, and a sync mechanism via diff_tasks. No obvious gaps for the domain.