Sprint MCP Server
Related Servers
Alternatives to Sprint MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables agents to manage projects, tasks, sprints, the Black Hole, comments, invites, and workspace settings through the Sprrint API using natural language or tool calls.40MIT
- AlicenseNot gradedqualityAmaintenanceEnables governed multi-agent software factory operations through eight typed, audited tools for Sprint planning, submission, decisions, inspection, cancellation, and resumption.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceGives coding agents 73 native tools to run their own project management — filing, linking, and resolving bugs and features, planning sprints, migrating from Jira/Linear/Shortcut, and handling cross-agent contracts, channels, DMs, notifications, and audit trails. Runs locally or remotely with API-key auth, so agents track work with full intent and reasoning instead of losing it when their context window resets.346 npm1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to manage projects, epics, and tasks with atomic locking, real-time dashboard, and multi-agent coordination.MIT
- AlicenseCqualityAmaintenanceA disciplined-sprint MCP server for AI coding agents, providing structured sprint management with immutable append-only ledger, programmatic close-gates, and live dashboard.2913 npmApache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceEnables 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.-
TDQS
Scored across 2 tools
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.
Both tool names follow a consistent verb-noun pattern with hyphens (check-sprint-status, start-sprint), making the naming predictable and readable.
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.
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.