Skip to main content
Glama
michaelkerr

product-delivery

by michaelkerr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to product-delivery

No user-submitted related servers found.

    Related Servers

    • pnCore

      perniemann
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables software delivery as a sequence of named, gated workflow steps, from discovery and planning through build, review, and handoff, with verifiable gates and resumable state outside the chat.
      14 npm
      MIT

    • delivery-intelligence-mcp

      mypoorbrain
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables delivery leads to query explainable programme health, prioritized risks, dependency impacts, change request effects, blocked decisions, and evidence-backed claims with refusal on unsupported assertions, all via deterministic tools and telemetry.
      MIT
    • agileharness by kapstanhq

      agileharnessofficial

      kapstanhq
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing agile project boards with automated agent-driven workflows, enforcing stage gates and generating service and MCP client configurations.
      Apache 2.0

    • Mission

      MaximilianoColoma
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables persistent work-state coordination with identity-bound assignments, governed lifecycle transitions, bounded queries, and auditable history.
      Apache 2.0

    • worktracker

      coding-nyx
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables unified management of work items from multiple tools through a kanban, providing CRUD, status transitions, comments, links, enrichment, dispatch, and board tools via MCP.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 19 tools

    Disambiguation3/5

    Most tools map to distinct resources or actions, but workflow_check and workflow_next are nearly identical—both report available transitions and guard status. workflow_status and workflow_render also overlap in purpose, differing mainly in output format, which could cause an agent to select the wrong one.

    Naming Consistency4/5

    All tools share a consistent workflow_ prefix, and subdomains are marked with item_ and project_ segments. However, the pattern is not uniformly verb-first: workflow_projects, workflow_status, and workflow_config are noun-style, while workflow_item_add and workflow_project_remove place the verb at the end.

    Tool Count3/5

    19 tools is on the heavy side for a single server, though the breadth of workflow management—setup, state transitions, work items, guards, and project registry—partially justifies it. A few tools like workflow_check and workflow_next could be consolidated, which would tighten the surface.

    Completeness4/5

    The server covers the full delivery lifecycle: setup, detection, initialization, status, state transitions, blocking/resuming, closing, work item management, guard waiving, and configuration. Minor gaps exist, such as no way to edit or delete a work item, but these can be worked around without major agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources