goby-mcp
OfficialRelated Servers
Alternatives to goby-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables managing tasks through a simple task tracker with REST API and MCP tools for listing, creating, updating, assigning, and deleting tasks.-
- AlicenseBqualityAmaintenanceEnables task management through MCP, including creating, reading, updating, deleting, and completing tasks, with filtering by status, priority, or due date and secure token-based authentication.6GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage Google Tasks, including creating, updating, deleting, and listing tasks and task lists, with optional due dates and subtasks.56MIT
- FlicenseNot gradedqualityCmaintenanceEnables task management through MCP, including creation, retrieval, update, deletion, and filtering tasks by completion status using a MySQL-backed server.-
- AlicenseNot gradedqualityCmaintenanceEnables managing LETSGO tasks, projects, comments, and history from MCP-compatible clients, with changes syncing to the LETSGO iPhone app.MIT

Tembo MCP Serverofficial
AlicenseBqualityDmaintenanceEnables interaction with the Tembo API to manage organization tasks and view enabled code repositories. Users can create, search, and list tasks or retrieve account information directly through MCP-compatible clients.5181MIT
TDQS
Scored across 18 tools
Every tool targets a distinct concern: auth introspection, task CRUD, comments, webhooks, and project tokens. The list_* getters are clearly separated by noun (statuses, members, labels, tasks), so there is no meaningful overlap or ambiguity.
Naming is highly predictable: list-* for reads, get-* for single resources, create-/update-/delete- for mutations, and add- for comments. The one outlier, whoami, is a conventional CLI-style name and does not create confusion.
18 tools is on the higher side but justified: task management, comments, history, webhooks, and token management each need their own surface. There are no redundant tools, though a few administrative helpers could potentially be consolidated.
The core domain is well covered: task CRUD (minus explicit deletion/archival), comments, history, webhooks, and token configuration. Missing task delete/archive and comment edit/delete are minor gaps, and webhook delivery inspection would round it out, but the main workflows are complete.