SprintFlint

Endpoint

One URL, one auth header. Same bearer token as the REST API.

POST https://mcp.sprintflint.com
Authorization: Bearer YOUR_TOKEN
Content-Type: application/json
Accept: application/json, text/event-stream

Generate a token from your account settings. Free tier covers 300 tickets; no card.

Tools

Day-one tools, mapped 1:1 onto the actions a developer takes during a sprint.

  <div class="comparison-grid">
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-folder"></i></div>
      <h3><code>list-projects</code></h3>
      <p>Search projects in your organisation (paginated). Returns id, name, slug, and counts.</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-flag"></i></div>
      <h3><code>list-sprints</code></h3>
      <p>Search sprints inside a project (paginated). Returns sprint id, goal, start/end dates, and issue counts by status.</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-list-ul"></i></div>
      <h3><code>list-issues</code></h3>
      <p>Search issues inside a sprint (paginated). Filter by status. Returns id, title, status, story points, assignee, labels.</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-user"></i></div>
      <h3><code>my-issues</code></h3>
      <p>Issues assigned to the calling user. The default opening question for any agent: "what am I working on?"</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-magnifying-glass"></i></div>
      <h3><code>get-issue</code></h3>
      <p>Read a single issue by reference (e.g. <code>PROJ-123</code>) including full markdown description and comment thread.</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-plus"></i></div>
      <h3><code>create-issue</code></h3>
      <p>File a new issue into a sprint. Title, description, sprint id, optional priority/labels/assignee.</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-pen"></i></div>
      <h3><code>update-issue</code></h3>
      <p>Update title, description, status, story points, or assignee on an existing issue. All mutations reversible from the UI.</p>
    </div>
    <div class="comparison-card">
      <div class="comparison-card__icon"><i class="fa-regular fa-comment"></i></div>
      <h3><code>create-comment</code></h3>
      <p>Post a markdown comment to an issue. Used by agents to log PR links, status updates, and surfaced blockers.</p>
    </div>
  </div>
</div>

What's deliberately not exposed

Two operations we did not ship on day one; both irreversible (or hard to undo) and unsafe to expose blindly to a model that occasionally hallucinates an argument. Update operations are available (every mutation is reversible from the UI) but destruction stays a human decision.

• delete-issue: silent destruction of work history. Cost asymmetry too high. Click delete in the UI.
• delete-sprint: silent breakage of velocity history and sprint planning. Use the board.

Read the design rationale: Sprint state in your agent: the practitioner's guide.

Connect in 30 seconds

Pick your editor. The MCP Config Generator emits the right snippet for each.

  <div class="comparison-grid">
    <a class="comparison-card" href="/for/claude-desktop">
      <div class="comparison-card__icon"><i class="fa-regular fa-comment"></i></div>
      <h3>Claude Desktop</h3>
      <p>Paste <code>mcpServers</code> block into <code>claude_desktop_config.json</code>. Restart.</p>
      <span class="comparison-card__link">Setup <i class="fa-regular fa-arrow-right"></i></span>

Cursor

Settings → MCP → Add server. Same JSON shape.

Claude Code

One CLI command: claude mcp add sprintflint --transport http ...

Zed

context_servers block in ~/.config/zed/settings.json.

Auth, scoping, security

• Auth: Authorization: Bearer YOUR_TOKEN. Same token as the REST API.
• Scope: tokens are scoped to your organisation. No cross-org access.
• Revocation: tokens listed by name + last-used time in account settings. Revoke instantly.
• Recommendation: one token per device (e.g. claude-desktop-macbook, cursor-work-laptop). Easier to spot orphans.
• TLS: Heroku ACM with Let's Encrypt. HSTS preloaded.
• Rate limit: 600 requests/min/token. 429 with Retry-After header on exceed.