Built for Copilot-powered teams
Sprint Tickets,
In Copilot Chat.
Copilot already knows your code. Plug in SprintFlint and it knows your sprint too; assigned tickets, story points, status, all without leaving VS Code.
5-min setup
REST API + MCP server
No card to start
Why GitHub Copilot + SprintFlint
Built around how your AI actually works.
Other trackers
- Copilot can't see your tickets without an extension dance
- OAuth flows break agent loops
- UIs assume someone's clicking, not chatting
- Pricing punishes you for adding the AI 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 tier covers your first 300 tickets
Step 1: Token
Generate the API token.
# In SprintFlint: Profile → API Token → Generate
# In your VS Code workspace, store the token:
export SPRINTFLINT_TOKEN=sf_pk_your_token_here
Step 2: Custom instructions
Add a Copilot custom instruction.
Open VS Code Settings → Copilot → Custom Instructions. Paste this block so Copilot Chat fetches sprint context whenever you ask about tickets.
# .github/copilot-instructions.md
When I ask about tickets, sprints, or velocity, fetch context
from the SprintFlint REST API at https://sprintflint.com/api/v1
using the bearer token in $SPRINTFLINT_TOKEN.
After committing code that addresses a ticket, suggest a
comment payload for POST /api/v1/comments.
Step 3: Chat
Ask Copilot for context.
"@workspace what tickets are in my SprintFlint sprint?"
Copilot Chat now answers with live data, not stale guesses.
- 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.
Copilot Already Reads Your Code.
Now it can read your sprint.
300 free tickets. No card. 5-minute setup.