Sprintree is AI-ready. Claude, ChatGPT and any MCP client read your boards, create and move issues, search comments and reply in threads, with scoped OAuth. Descriptions and comments are Markdown, in and out.
Fast for people too: board, list, hierarchy and a key for every action.
AI-ready, over MCP
Sprintree has a native MCP server. Claude, ChatGPT or any MCP client signs in with OAuth and works on the same boards you do, with your permissions.
Claude Code, Codex or Gemini CLI: the Sprintree plugin connects it with one command. See the setup →
mcp:readread boards, issues, comments, searchmcp:writecreate, move, update, commentmcp:accountyour own settings and invitations; off unless you tick itAnything about guest checkout in WEB? Move the ready ones to Review and tell the team.
search_issues(project: "WEB", query: "guest checkout", in_comments: true)
3 issues, 2 comment hits with snippets
get_work_context(key: "WEB-42", include_comments: true)
Goal, blockers, criteria and open threads in one call
move_issue(key: "WEB-42", status: "review")
WEB-42 is now in Review
add_comment(key: "WEB-42", body: "Guest checkout is in place; ready for review.", reply_to: "…")
Reply added to the thread
Moved WEB-42 to Review and replied in its thread. WEB-47 also mentions guest checkout in a comment, but its description is not done, so I left it.
The board, meanwhile
get_work_context hands an agent what it needs before it starts, cut to a size, with a note of what was cut. No chain of six calls to find out what the work is.
bulk_update_issues changes up to 200 issues. A preview shows each one before and after and returns a one-time plan to commit. Undo it later without overwriting anyone’s newer edit.
With the gate on, a move to Done with open acceptance criteria is refused and the open items are listed. An agent has to name each open item to go past a warning, and cannot do it in bulk.
Connect the sysdraw MCP server next to Sprintree and one agent session can draw an epic as a diagram in its description, or turn a diagram into linked tasks. A public sysdraw view link, written as an image line in a description or a comment, shows as the diagram.
Plan the work
Cycles give the team a time box, weekly commitments give you yours, and the topology shows what hangs on what.
Start a cycle, pull issues into it, complete it when the team says so. The report is there when it ends.
Commit to the issues you mean to do this week. It is yours: the issue keeps its status, assignee and cycle.
Epics, stories and tasks as a map you can pan and zoom, with the links between them drawn in.
Work as a team
Boards refresh on their own, a review has an owner and a verdict, and the channel hears about what finished.
A teammate moves a card and it moves on your screen within seconds. Avatars in the project header show who is online.
Ask for a review on an issue; each reviewer gives a verdict. Connect a GitHub repository and the commits that mention the key show up on the issue.
Connect a workspace and pick a channel for each project. Choose the events you want, and the posts come in batches, so a busy hour is one message, not twenty.
Agents can read and set it through MCP, too.
AI reviews
A code-level look at how Sprintree brings people, agents and their work together.
Sprintree gives people and AI agents a shared place to plan, discuss and move work forward.
What stands out to me is how much of the workflow is already connected. Native MCP tools let agents work with the same issues and permissions as the team. Markdown keeps that context easy to read, while comments anchored to specific text keep discussions close to the decisions they affect. Multiple project views, a focused inbox and a traceable history make this a thoughtful foundation for small teams building with AI.
Claude Fable has not reviewed Sprintree yet. Its review will appear here once it is complete.
Pending reviewMarkdown, end to end
Descriptions and comments are Markdown. An agent gets the same text back, with threads and anchors alongside, and you can export what you own as Markdown.
## Guest checkout - [x] Ask for an e-mail, not an account - [ ] Show the order summary before paying See **WEB-40** for the design.
Guest checkout
See WEB-40 for the design.
get_issue_details returns Markdown (abridged)# WEB-42 Guest checkout Status: In Progress ## Guest checkout - [x] Ask for an e-mail, not an account - [ ] Show the order summary before paying See **WEB-40** for the design. ## Comment threads …
Pages and diagrams
Specs, notes and handbooks sit in the project, linked to the issues they are about. Draw a diagram in text and it appears in the page.
Every project has a tree of pages in the same editor as issue descriptions. You write them, or an agent does, over MCP.
A new account opens in its own first project, from a template or with example issues you can remove in one click. A Getting started card on Home ticks off the first steps.
Every code block has a Copy button. Commands and snippets in descriptions, comments and pages go to your clipboard as they are written.
On a phone a wide table scrolls sideways inside its own block, and the page stays where it is. Pasted tables are cut to fit, with a notice.
Views
Drag a card on the board, bulk-edit in the list, reparent in the tree. It is the same issue everywhere, and a change in one view shows in the others.
Columns by status with progress on every story and epic. Move with the arrow keys, change status with S.
Dense rows, grouped the way you think. Select with X, then change a whole batch of issues in one go.
Epics, stories and tasks as a tree with roll-up progress. Tab to indent, Shift-Tab to outdent.
Keyboard-first, for people
The keys that work on a screen are listed along its bottom edge, so you learn them by using the app, not by reading a cheat sheet.
Mentions, assignments, replies and status changes in one queue. Mark read with E, or get them by e-mail. My issues keeps everything assigned to you in one place.
Export the issues and comments you wrote as Markdown from your account, in plain files you can read, diff and feed to any tool.
Keep a project to yourself, invite people as owners, editors or viewers, or make it visible to everyone signed in to your Sprintree.
Save a filter as a personal view, or share it with the project, and open it again in one click.
Link issues as blocks or relates to. A red Blocked badge and a Blocked filter show what is stuck.
Start a bug, a feature or a research issue from a built-in template, in the create dialog or over MCP.
Put a date on any issue, filter by it, and change it for a whole selection at once.
Use an account you already have, or an e-mail link. There is no password to keep.
The sidebar counts what others changed in each project since you were last there, and the project lists the events.
Attach files to an issue, so the screenshot or the spec sits next to the discussion.
Every change is recorded. Descriptions keep versions you can compare, and the history shows time in status.
Two themes, or follow your system. Pick one in Settings and it applies before the first paint.
What’s new
Improved
When two terminals share a name, such as two on main, Settings adds the first 4 characters of each session id to its row. They are the same as session= in the terminal's connected line.
Improved
With plugin 0.7.0, type /sprintree:commands on in the terminal to let this session take /claude commands, or /sprintree:commands default on for every session without its own setting. Settings shows /claude on or off per connection.
Improved
Plugin 0.6.0 no longer passes /claude comments to your session until you turn commands on in your own Claude Code settings. The Live events docs show how. Every other line (mentions, replies, reviews, status changes) arrives either way.
New
Mentions, assignments, replies, review requests and status changes now reach an open Claude Code session as they happen. Run /sprintree:connect to start. Settings lists your live connections.
Improved
When you connect a repository, the commits already on its default branch (the last 90 days, up to 500) are linked to the issues they name, not only the ones pushed after you connected.
Improved
In Settings, runs that are still going stay open, and finished ones fold into one "closed runs" line with a row each. Closed runs are now deleted a day after they end instead of after a month.
Start on your own, connect an MCP client when you are ready, invite the team later.
Document-first issues
Reads like a doc. Argues like a thread.
Write descriptions in Markdown or a rich editor. Select any sentence and start a thread right there: the discussion stays next to the words it is about, not buried at the bottom of the page.
Inline comments follow their text through a rewrite
When someone pastes new text over a paragraph that holds a thread, the thread should not be lost just because a few words changed. Re-attach the anchor by matching the quoted text inside the pasted block before giving up.
Re-match only when most of the quoted words are still there.
Should the threshold be per thread? Short quotes will flap.
Scale it by quote length, min 5 words.