Built for the fastest editor

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.

5-min setup
REST API + /llms.txt
No card to start

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 /llms.txt — agents discover the API instantly
  • 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 — context_servers

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"
      }
    }
  }
}
Step 3 — Prompt

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

Zed Is Already Fast.

Native MCP. Bearer auth.
300 tickets free. Setup in under 2 minutes.