Sprint MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (debug, info, warn, error). Default is info if not set. | info |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start-sprintA | Initialize a new sprint with manifest and directory structure. Checks for active sprints first. |
| check-sprint-statusA | Verify current sprint state and check for active sprints. Returns active sprint info or confirms no active sprints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.