sprinty
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sprint_newC | Start a sprint with explicit git_dir and a worktree-scoped, uncommitted data_dir; returns orientation. |
| sprint_resumeB | Resume an existing sprint by binding this MCP session to an existing git_dir and data_dir without creating a sprint. |
| sprint_detachB | Detach this MCP session from its current Sprinty binding and stop the dashboard. |
| sprint_listB | List existing sprint ledgers in a data_dir, or the current binding when already attached. |
| sprint_closeC | Close the sprint after a programmatic re-check of all gates. |
| sprint_archiveA | Archive the sprint with a recovery reason, bypassing normal close gates. |
| overviewB | Compact sprint overview: title, details, notes, artifacts, and subsprint counts. |
| nextC | Compact work window for choosing the next item. |
| subsprint_newC | Create a subsprint (description, goals, gates). |
| subsprint_getC | Read one subsprint with compact item rows. |
| subsprint_listC | List subsprints with compact rows. |
| item_addC | Add an atomic item (bounded title, bounded description, code locations, gates — all required). |
| item_getB | Read one item with full untruncated detail. |
| item_updateB | Update item metadata: note, title, description, high_priority, and/or replacement dependency ids. |
| item_doneC | Resolve an item as completed with commit id + gate results. |
| item_splitC | Resolve an item as split, creating a seeded subsprint atomically. |
| item_deprecateC | Resolve an item as deprecated with a reason. |
| note_addA | Add a note to a specific item id. Notes are not substitutes for item_add(); create items for trackable work. |
| note_getC | Read notes attached to an item id. |
| note_listC | List notes for an item as compact rows. |
| note_updateB | Update a note by note id. |
| artifact_addC | Attach a file path to the sprint, optionally related to item ids. |
| artifact_getC | Read one artifact by id. |
| artifact_listA | List active sprint artifacts as compact rows. |
| artifact_updateC | Update an artifact by id. |
| searchA | Regex search over sprint text with character context around each match. |
| changelogB | Render the sprint changelog as Markdown with change-map and coverage tables. |
| dashboard_infoA | Return the current dashboard URL and port without starting or restarting it. |
| dashboard_restartA | Restart the follow-along dashboard and return its URL and port. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| how-to-run-a-sprint | |
| using-sprinty |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ebursztein/sprinty'
If you have feedback or need assistance with the MCP directory API, please join our Discord server