Skip to main content
Glama
bernatch22

taskops

by bernatch22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to taskops

No user-submitted related servers found.

    Related Servers

    • claude-cockpit

      shmuelix
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for a kanban task board that lets Claude Code manage tasks with priority, categories, and multi-agent safety, plus a web UI for visual drag-and-drop.
      2 npm
      MIT

    • ctx

      crodris
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for context switching across git worktrees and Claude Code agent sessions, providing a board of worktree status and distilled task summaries.
      234 npm
      MIT

    • aichat-mcp

      Wayy-Research
      A
      license
      A
      quality
      D
      maintenance
      MCP server for inter-agent communication. Gives multiple Claude Code sessions a shared message board, agent registry, and orchestration layer — backed by a cloud relay so agents can coordinate across machines, repos, and teams.
      8
      60 npm
      MIT

    • Board

      xinayida
      A
      license
      Not graded
      quality
      B
      maintenance
      A kanban board MCP server that lets Claude Code manage tasks through a local web UI, including claiming, submitting, and querying tasks with automatic git branch and PR creation.
      22 npm
      MIT

    • cc-agent

      Gonzih
      A
      license
      A
      quality
      D
      maintenance
      MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
      47
      144 npm
      2
      Apache 2.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool has a distinct job, but taskops_card, taskops_take, taskops_board, and taskops_activity all return card/board state, so an agent must read carefully to pick the right one. The descriptions clarify the differences well enough: search/detail, claim+dossier, board pulse, and activity history.

    Naming Consistency3/5

    All tools share the taskops_ prefix, but the second part mixes nouns (card, board, activity) with verbs (plan, assign, merge, take, review, update, comment) and one past-tense outlier (filed). This is readable but not a consistent verb_noun convention.

    Tool Count5/5

    With 11 tools, the set is well-scoped for a task-orchestration domain: planning, assignment, claiming, updating, commenting, review, merging, status, and history each have a dedicated tool. No tool feels redundant.

    Completeness5/5

    The toolset covers the full card lifecycle: creation via plan, assignment via assign, claiming via take, updates and drops via update, review, merging, status via board, history via activity, and report registration via filed. There are no obvious dead ends or missing critical operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources