A
licenseNot graded
qualityC
maintenanceA Model Context Protocol (MCP) server that brings your Google Tasks into Claude and other MCP-compatible clients, enabling task and task list management through natural conversation.
73 npm
8
MIT
Google Tasks MCP
by ezrazhang7
Related Servers
Alternatives to Google Tasks MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that bridges Claude with Google Tasks, allowing users to manage task lists and tasks directly through Claude interface.1573 npm49MIT
- FlicenseNot gradedqualityDmaintenanceA task management MCP server that provides tools to create, list, complete, and delete tasks using pluggable storage backends. It enables users to interact with their task lists through natural language using MCP-compatible clients like Claude Desktop.-
- FlicenseNot gradedqualityDmaintenanceAn OAuth-authenticated MCP server that bridges Claude AI with a task management system, allowing users to list, create, and update tasks through natural language commands.1-
- FlicenseNot gradedqualityDmaintenanceA local task management MCP server that enables users to create, update, and manage tasks through natural language conversations with Claude. It provides nine tools for comprehensive task management including creation, filtering, searching, and daily planning without requiring a separate UI or backend service.-
- AlicenseNot gradedqualityDmaintenanceA Cloudflare Worker-based MCP server that enables AI assistants to read and manage Todoist tasks through tools like get_tasks, add_task, update_task, complete_task, delete_task, and move_task.283 npmMIT
TDQS
A4.2/5.0
Scored across 14 tools
Disambiguation5/5
Each tool targets a distinct resource-action pair (e.g., list_tasklists vs list_tasks, create_task vs create_tasks, clear_completed vs delete_task). The descriptions make the boundaries clear, so an agent should rarely misselect.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern (list_tasklists, create_task, move_task, etc.). The only variation is plural for batch operations (create_tasks), which is intuitive and consistent.
Tool Count5/5
With 14 tools, the set is well-scoped for Google Tasks. Each tool covers a distinct operation, and the count falls within the ideal 3-15 range without redundancy or bloat.
Completeness5/5
The surface provides full CRUD and lifecycle coverage for both task lists (list, create, rename, delete) and tasks (create, list, get, update, complete, reopen, move, delete, clear completed). No obvious gaps exist for the domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues