SprintFlint
About
Opinionated sprint tracker. Read/update tickets, sprints, velocity from Claude/Cursor/Zed.
Details
- Author
- Unknown
- Categories
- Productivity, Project Management
Jump to
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 youraccount settings. Free tier covers 300 tickets; no card.
Day-one tools, mapped 1:1 onto the actions a developer takes during a sprint.
Search projects in your organisation (paginated). Returns id, name, slug, and counts.
Search sprints inside a project (paginated). Returns sprint id, goal, start/end dates, and issue counts by status.
Search issues inside a sprint (paginated). Filter by status. Returns id, title, status, story points, assignee, labels.
Issues assigned to the calling user. The default opening question for any agent: "what am I working on?"
Read a single issue by reference (e.g.PROJ-123) including full markdown description and comment thread.
File a new issue into a sprint. Title, description, sprint id, optional priority/labels/assignee.
Update title, description, status, story points, or assignee on an existing issue. All mutations reversible from the UI.
Post a markdown comment to an issue. Used by agents to log PR links, status updates, and surfaced blockers.
Two operations we didnotship on day one; both irreversible (or hard to undo) and unsafe to expose blindly to a model that occasionally hallucinates an argument. Update operationsareavailable (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. TheMCP Config Generatoremits the right snippet for each.
PastemcpServersblock intoclaude_desktop_config.json. Restart.
Settings → MCP → Add server. Same JSON shape.
One CLI command:claude mcp add sprintflint --transport http ...
context_serversblock in~/.config/zed/settings.json.
- Auth:Authorization: Bearer YOUR_TOKEN. Same token as theREST 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.429withRetry-Afterheader on exceed.
Everything you need to know about the MCP server.
What protocol version does the server speak?
2025-06-18(current stable). Also accepts2024-11-05for 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.
Does the server support resources or prompts (the other two MCP primitives)?
Tools today. Resources and prompts are on the roadmap; see/roadmap. The capabilities handshake currently advertisestools,prompts,resources,logging; tool calls are the only fully-implemented primitive on day one.
Can I use this server with my own agents (LangChain, autogen, etc.)?
Anything that speaks MCP works. Bring your own client. Some non-MCP clients work better with theREST API: same data, same auth.
What happens if the agent hallucinates a sprint or ticket id?
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.
Is the server hosted, or can I self-host?
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[](https://sprintflint.com/cdn-cgi/l/email-protection#accfc3c2d8cdcfd8ecdfdcdec5c2d8cac0c5c2d882cfc3c1)<<<[email protected]. We read everything.
Still have a question?; we usually reply within an hour.
Interact with Atlassian tools like Confluence and Jira.
Integrates AI with Atlassian Jira to manage projects, search for issues, and view development information like commits and pull requests.
A server for querying Jira issues, requiring a Jira token for authentication.
Integrate with Jira's REST API to manage projects, track issues, and perform analytics.
Interact with Jira to manage issues, projects, and workflows using the Jira Cloud Platform REST API.
An MCP server for interacting with Jira's REST API to manage projects, issues, and users.
Interact with JIRA to search for issues using JQL and retrieve detailed issue information.
Access and manage JIRA issues, projects, and users with optimized data payloads for AI context windows.
Integrate with JIRA to allow AI assistants to directly interact with JIRA issues.
Integrate Atlassian JIRA into any MCP-compatible application to manage issues and projects.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
