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
      C
      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

    • MCP GitHub Project Manager

      sanarossi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to register, claim tasks atomically, coordinate via heartbeats, review each other's work, enforce token budgets, and ship code using GitHub Projects v2 as the backing store. It also gives humans AI-powered PRD generation, sprint planning, issue triage, and roadmap creation without external infrastructure.
      35 npm
      MIT

    • MCP GitHub Project Manager

      Klaush230
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to use GitHub Projects v2 as an autonomous task backbone, with task checkout, atomic claims, heartbeats, peer review, token budgets, and PRD-to-issues automation. It also supports AI-powered sprint planning, issue triage, roadmap generation, and MCP resources/prompts.
      35 npm
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources