Skip to main content
Glama

Related Servers

Alternatives to tasks-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      53
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      12
      661 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      20
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Stdio-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.
      7
      1,364 npm
      Apache 2.0

    TDQS

    B3/5.0

    Scored across 19 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues