Skip to main content
Glama
cnavta

Sprint MCP Server

by cnavta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Sprint MCP Server

No user-submitted related servers found.

    Related Servers

    • sprrint

      ejasmuhamed
      A
      license
      C
      quality
      B
      maintenance
      Enables agents to manage projects, tasks, sprints, the Black Hole, comments, invites, and workspace settings through the Sprrint API using natural language or tool calls.
      40
      MIT

    • Forja MCP Server

      rvbernucci
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables governed multi-agent software factory operations through eight typed, audited tools for Sprint planning, submission, decisions, inspection, cancellation, and resumption.
      1
      Apache 2.0

    • sprinty

      ebursztein
      A
      license
      C
      quality
      A
      maintenance
      A disciplined-sprint MCP server for AI coding agents, providing structured sprint management with immutable append-only ledger, programmatic close-gates, and live dashboard.
      29
      35 npm
      Apache 2.0

    • MCP Product Development

      NeoTecDigital
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to track and manage product development projects through structured 7-phase lifecycles with sprint tracking, role-based collaboration, and multi-project support. Provides phase management, progress tracking, and team coordination tools for complete product development workflows.
      -
    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.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    check-sprint-status and start-sprint have clearly distinct purposes: one queries current state, the other initiates a new sprint. There is no functional overlap between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb-noun pattern with hyphens (check-sprint-status, start-sprint), making the naming predictable and readable.

    Tool Count3/5

    With only 2 tools, the server feels thin. While the scope appears focused on sprint lifecycle basics, the count is borderline and would benefit from additional tools to be considered well-scoped.

    Completeness2/5

    The tool set only covers starting and checking sprints. Missing operations like ending a sprint, updating sprint details, or listing historical sprints leave significant gaps in the sprint management lifecycle.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources