TeamAPI
Who owns this? Just curl your org.
Every team has an API: what it owns, who's accountable for what, how much it can take on.
Usually it's scattered across wikis and people's heads, where it drifts out of date.
Write it down as one teamapi.yml per team and TeamAPI makes it executable.
$
npm install -g @jgalego/teamapi
Quick start
Write it down
One file per team: what it owns, who's accountable, how much it can take on.
teamapi scaffold my-team \ --type stream-aligned \ --out teamapi.yml
Serve the API
A read-only REST API and a dashboard, straight from the files. No database.
teamapi serve-api ./org # → localhost:3000/dashboard
Ask your org
Point an assistant at the MCP server and ask in plain English.
teamapi serve-mcp ./org # "which team is overloaded?"