API & MCP

Everything a person can do on Trackwell Sprint Burndown, a program or AI agent can do with the same inputs and get the identical result.

HTTP API

POST https://trackwellburndown.usefulweb.app/api/v1/calculate – run Trackwell Sprint Burndown
GET https://trackwellburndown.usefulweb.app/api/v1/tool – inputs, output schema, examples
OpenAPI 3.1: /openapi.json · /openapi.yaml
Errors: application/problem+json; 422 includes per-field errors.

Trackwell Sprint Burndown

Draws the burndown (remaining work per day against the ideal line) and burnup (completed work and scope) of a sprint. Reads a Trackwell project and rebuilds the sprint from the issue history, or takes a simple table of items with points and the moments they were added, removed and finished.

Inputs of Trackwell Sprint Burndown
Field	Type	Default	Description
`project`	textarea	—	Trackwell project (JSON, optional). A .trackwell.json project with sprints. Leave empty to use the items table below.
`sprint`	text	—	Sprint name. Empty = the active sprint (or the last completed one).
`start`	date	—	Sprint start (items table only)
`end`	date	—	Sprint end (items table only)
`items`	table	[]	Sprint items. Dates as YYYY-MM-DD (counted at the end of that day) or YYYY-MM-DDTHH:MM.
`unit`	select (points, issues)	"points"	Measure
`asOf`	date	—	Today is. Days after this date are left empty. Empty = today.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

Streamable HTTP endpoint: https://trackwellburndown.usefulweb.app/mcp – protocol revisions 2026-07-28 (stateless) and 2025-11-25 / 2025-06-18 / 2025-03-26 (initialize handshake).
Tools: trackwell_burndown
Local stdio connector: node src/mcp-stdio.ts --tool=trackwell-burndown

{
  "mcpServers": {
    "trackwell-burndown": { "type": "http", "url": "https://trackwellburndown.usefulweb.app/mcp" }
  }
}