Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
infoD

Startup orientation and compact sprint discovery before binding to one sprint.

sprint_newB

Start a sprint with explicit git_dir and a worktree-scoped, uncommitted data_dir; returns orientation.

sprint_resumeA

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_closeB

Re-check all gates, write the canonical SemVer changelog, and close the sprint.

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_getB

Read one subsprint with compact item rows.

subsprint_listA

List subsprints with compact rows.

item_addA

Add an atomic item (bounded title, bounded description, code locations, gates — all required; gate_timeout_ms defaults to 5000 and null disables it).

item_getB

Read one item with full untruncated detail.

item_updateA

Update an item by id: metadata, open-item gates/timeout, completed-item commit_id, and/or dependency ids.

item_doneA

Resolve an item as completed with a commit id and a semver changelog verb (added/fixed/changed/removed/deprecated/security). Sprinty runs the item's executable gates itself; only manual gates take agent-supplied gate_results.

item_splitC

Resolve an item as split, creating a seeded subsprint atomically.

item_deprecateA

Resolve an item as deprecated with a reason, or drop a whole subsprint by passing its id (its open items are deprecated too).

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_listA

List notes for an item as compact rows.

note_updateC

Update a note by note id.

artifact_addC

Attach a file path to the sprint, optionally related to item ids.

artifact_getA

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.

changelog

Preview or export the current SemVer Markdown changelog and return only its path; sprint_close writes the canonical changelog automatically.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
how-to-run-a-sprint
using-sprinty

Latest Blog Posts

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