Sprint Tickets,
In Zed.
Zed's agent panel speaks MCP. Add SprintFlint as a context server, restart, and your sprint is one prompt away; assigned tickets, status, story points.
Why Zed + SprintFlint
Built around how your AI actually works.
Other tools
- Zed assistant can't pull live ticket data
- No bearer-token-only sprint API
- OAuth flows kill the speed Zed gives you
- Pricing assumes you have a dedicated PM tool seat
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
Generate the token.
# In SprintFlint: Profile → API Token → Generate
# Same token works for MCP and the REST API.
Add SprintFlint as a Zed context server.
Open ~/.config/zed/settings.json. Add the block below. Replace YOUR_TOKEN with the token from step 1. Restart Zed; the agent panel picks the server up automatically.
{
"context_servers": {
"sprintflint": {
"source": "custom",
"url": "https://mcp.sprintflint.com",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
Ask Zed for sprint context.
"What's the next SprintFlint ticket I should pick up?" Zed calls the MCP server, fetches active sprint state, no tab-switch.
- 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.
Zed Is Already Fast.
Native MCP. Bearer auth.
50 free tickets per month. Setup in under 2 minutes.