Built for AI editors
Sprint Tickets,
Inside Cursor.
Native MCP. Drop one JSON block into Cursor settings and the agent reads your sprint, files tickets, and posts comments without leaving the editor.
5-min setup
REST API + MCP server
No card to start
Why Cursor + SprintFlint
Built around how your AI actually works.
Other trackers
- No machine-readable context (no MCP server)
- Heavy auth flows that block agent access
- UIs that hide the data your agent needs
- Per-seat pricing scales with your team, not your value
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 tier covers your first 300 tickets
Step 1: Token
Generate the token.
# In SprintFlint: Profile → API Token → Generate
# Same token works for MCP and the REST API.
Step 2: Cursor → Settings → MCP
Add the MCP server in Cursor.
Open Cursor → Settings → MCP → Add server, paste the JSON below, replace YOUR_TOKEN with the SprintFlint token from step 1, and save.
{
"mcpServers": {
"sprintflint": {
"url": "https://mcp.sprintflint.com",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
Step 3: Run
Ask Cursor about your sprint.
"What's in my SprintFlint sprint this week?"
Cursor calls list-sprints and list-issues, summarises state, and offers to file follow-up issues.
- 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.
Stop Tab-Switching to Jira.
Native MCP, native bearer auth.
300 free tickets. Set up in under 2 minutes.