tasks-mcp
Related Servers
Alternatives to tasks-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP-capable clients to drive Worksection projects, tasks, subtasks, comments, tags, people, time tracking, files, search, and reporting through a consistent set of tools over stdio.53MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to query projects, fetch findings, trigger analysis, upload CycloneDX BOMs, and check async token status against an OWASP Dependency-Track instance via stdio.24 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage Toggl Track time entries, timers, projects, clients, tags, and reports through a self-hosted stdio server.298 npmMIT
- AlicenseAqualityBmaintenanceEnables AI clients to read, search, comment on, create, update, assign, and move tickets and sprints in a mini-Jira platform via a personal access token. It runs locally over stdio and respects token permissions and project scope.12661 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to manage a filesystem-based issue tracker through typed MCP tools such as list_tasks, create_task, change_task_status, log_work, and get_sprint, instead of shelling out to a CLI. Tasks and sprints are plain folders of Markdown files, so agents can create, claim, comment on, and move work by topic without any database or server state.20MIT
- AlicenseBqualityDmaintenanceStdio-based MCP server exposing Jira tools for searching, creating, getting, commenting on, assigning, and transitioning issues, as well as listing projects, with authentication via token or basic auth.71,364 npmApache 2.0
TDQS
Scored across 19 tools
tasks_move and tasks_mv are effectively the same operation (both 'move an item to another parent, renumbers the subtree'), creating clear duplicate ambiguity. Additionally, the read surface (tasks_overview, tasks_sprint, tasks_stats, tasks_list, tasks_show, tasks_view, tasks_brief) overlaps heavily with only subtle distinctions between count views, table views, and rendered views.
A consistent tasks_ prefix is applied throughout, but the suffix convention is mixed: noun-based (overview, stats, sprint, brief, log, view) alongside verb-based (add, edit, move, set_status, remove). The duplication between tasks_move and tasks_mv further erodes predictability.
19 tools sits at the heavy end of the borderline range. Several read-oriented tools could be consolidated, and one is a straight duplicate, so not every tool clearly earns its place.
The surface covers the full lifecycle: create/edit/move/remove for sprints, tasks, and subtasks, plus status, notes, links, audit log, and derived-state views. Minor gaps like keyword search and bulk filtering exist but agents can work around them with list/view calls.