F
licenseNot graded
qualityC
maintenanceAn MCP server that enables AI models to securely read and manage GitHub issues with authenticated access, confirmation prompts for write operations, and metrics tracking for tool-call reliability.
-
tasks-mcp
by outputty
Related Servers
Alternatives to tasks-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server enabling AI coding agents to interact with a task tracker that enforces rules server-side, replacing markdown files and hooks with a database, CLI, and web UI.860 npm2MIT
- AlicenseAqualityBmaintenanceA reusable MCP server providing shared, versioned context across AI agents and devices via a private GitHub workspace, with tools to discover projects, bootstrap, query, and close out task state.42MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that exposes the full Task-Tracker REST API as MCP tools, enabling AI agents to manage trackers, tasks, notes, checklists, and projects conversationally.MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for managing a project backlog as Markdown files in Git, enabling AI agents to read, create, and update tasks programmatically.2-
- AlicenseNot gradedqualityBmaintenanceA production-grade MCP server that provides LLMs with safe, structured, tool-based access to GitHub repositories, including issue management, semantic search, and guarded write operations.MIT
TDQS
A3.6/5.0
Scored across 21 tools
Disambiguation4/5
Most tools map to a distinct resource+action: task CRUD, ready/planning views, roadmap, schedule, prerequisites, and blockers all have clear purposes. The main ambiguity is amend_task vs edit_task, since amend_task is largely a restricted subset of edit_task, though the descriptions explicitly call out when to use each.
Naming Consistency3/5
The majority of tools follow a verb_noun pattern like add_task, edit_task, get_task, and list_tasks, but several commands are bare nouns or verbs: roadmap, schedule, prereqs, blockers, and sync. The names are still readable and consistently lowercase snake_case, but the convention is mixed.
Tool Count3/5
At 21 tools, this server sits in the heavy band. Many read views are individually useful, but amend_task is redundant with edit_task, and several list/dependency tools overlap enough that the surface feels larger than necessary.
Completeness3/5
The task lifecycle is well covered with add, get, edit, start, close, delete, and trail operations, and the planning/read views are strong. However, roadmap targets have no update or delete path, so once a target is created its title, brief, and dependencies cannot be changed through the tool surface.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive