Built for terminal-first agents
Sprint Tickets,
Claude-Native.
One command; `claude mcp add`; and Claude Code reads the sprint, picks the next ticket, ships the PR, and comments back. Native MCP, no skill files.
5-min setup
REST API + MCP server
No card to start
Why Claude Code + SprintFlint
Built around how your AI actually works.
Other tools
- API requires OAuth dances and SDK installs
- No public agent-readable spec
- UIs assume a human is clicking
- Per-seat creep; you pay for the agent's seat too
SprintFlint
- Public MCP server at mcp.sprintflint.com; native protocol
- Bearer-token auth, one header, no OAuth dance
- REST endpoints designed for agent-first workflows
- £5/user/mo, free plan includes 50 new tickets per month
Step 1: Token
Generate the token.
# In SprintFlint: Profile → API Token → Generate
# Same token works for MCP and the REST API.
Step 2: claude mcp add
Add SprintFlint as an MCP server.
One CLI command. Replace YOUR_TOKEN with the token from step 1. No file editing; Claude Code stores the server config for you.
claude mcp add sprintflint \
--transport http \
https://mcp.sprintflint.com \
--header "Authorization: Bearer YOUR_TOKEN"
Step 3: Run
Hand off the sprint.
"Claude, ship the next SprintFlint ticket."
Reads the backlog. Picks one. Branches. Codes. Tests. Comments. Done; all via MCP, no scripted REST calls.
- Agent reads sprint backlog
- Auto-updates status when work begins
- Posts progress comments as it goes
- Pairs with Autoplay for full one-click PRs
Other AI editors we support
Same setup, different tools.
Your Terminal Already Ships Code.
Now your sprint board can keep up.
50 free tickets per month. Native MCP, no skill files to maintain.