Public Model Context Protocol endpoint at mcp.sprintflint.com. Drop one JSON block into Claude Desktop, Cursor, or Zed (or one CLI command in Claude Code) and the agent reads your sprint, files issues, and posts comments without leaving the chat.
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-streamGenerate a token from your account settings. Free tier covers 300 tickets — no card.
Eight day-one tools. Mapped 1:1 onto the actions a developer takes during a sprint.
list-projectsSearch projects in your organisation (paginated). Returns id, name, slug, and counts.
list-sprintsSearch sprints inside a project (paginated). Returns sprint id, goal, start/end dates, and issue counts by status.
list-issuesSearch issues inside a sprint (paginated). Filter by status. Returns id, title, status, story points, assignee, labels.
my-issuesIssues assigned to the calling user. The default opening question for any agent: "what am I working on?"
get-issueRead a single issue by reference (e.g. PROJ-123) including full markdown description and comment thread.
create-issueFile a new issue into a sprint. Title, description, sprint id, optional priority/labels/assignee.
update-issueUpdate title, description, status, story points, or assignee on an existing issue. All mutations reversible from the UI.
create-commentPost a markdown comment to an issue. Used by agents to log PR links, status updates, and surfaced blockers.
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.
Pick your editor. The MCP Config Generator emits the right snippet for each.
Authorization: Bearer YOUR_TOKEN. Same token as the REST API.claude-desktop-macbook, cursor-work-laptop). Easier to spot orphans.429 with Retry-After header on exceed.2025-06-18 (current stable). Also accepts 2024-11-05 for older clients.
Yes — same plan rules as the REST API. Free tier (300 tickets) gets full MCP access. Paid plans (£5/user/month) get unlimited.
Tools today. Resources and prompts are on the roadmap — see /roadmap. The capabilities handshake currently advertises tools, prompts, resources, logging; tool calls are the only fully-implemented primitive on day one.
Anything that speaks MCP works. Bring your own client. Some non-MCP clients work better with the REST API — same data, same auth.
The server returns a structured error. The agent sees the error and (usually) corrects itself. We deliberately omitted destructive tools so the worst-case is a failed read, not a silent delete.
Hosted only for now (mcp.sprintflint.com). Self-hosting MCP servers makes sense for offline-first tools, less so for SaaS — your sprint data already lives on our servers.
Email [email protected]. We read everything.
Free 14-day trial of the full product. Free forever for the first 300 tickets. Same token works for MCP, REST, and OpenAPI.