Draft, pending editorial review · not indexed

Turn sprint issues into booked time

Dev, web & IT · SOPs & process documentation · checked 2026-10-16

Cursor reads open GitHub issues for the sprint, estimates them with you, and books focus time through Reclaim’s MCP server.

Independent review. IonBin has no partnership with any tool on this page and was not paid for this page. Our evaluation is our own, based on public documentation and our research. Product names are trademarks of their owners and are used for identification only. How disclosure works.

Goal

Plan a sprint you can actually fit into the week.

Connects through: MCP

Steps

#WhoWhat happensHowStatus
1GitHub Lists open issues for the milestone MCP Confirmed · source ↗
2Cursor Groups and estimates issues with you AI platform Confirmed
3You Approve the plan Human step Confirmed
4Reclaim Books time for each block
Reclaim’s docs name Claude; Cursor setup to verify.
MCP To verify · source ↗

Confirmed means the vendor documents it (linked). It doesn't mean IonBin has tested it. AI-platform and human steps need no source.

Human approval

You approve the plan before anything is booked.

Watch out for

Reclaim: "Books time for each block" is not confirmed in vendor docs yet. Test it before relying on it.

Starter prompt

Goal: Plan a sprint you can actually fit into the week. Tools involved: GitHub, Cursor, Reclaim. Your part: lists open issues for the milestone; groups and estimates issues with you; books time for each block. Work step by step, show me each draft or proposed change, and wait for my approval before anything is sent, published, signed, filed or changed in a live system.

Assembled from this page’s goal and steps. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
GitHubMCP github.com ↗
CursorAI platform cursor.com ↗
ReclaimMCP reclaim.ai ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) To verify Reclaim: step to verify
OpenAI Codex To verify Reclaim: pairing not named in vendor docs
Google Antigravity To verify GitHub: pairing not named in vendor docs; Reclaim: pairing not named in vendor docs
ChatGPT To verify GitHub: pairing not named in vendor docs; Reclaim: pairing not named in vendor docs
Gemini To verify Reclaim: pairing not named in vendor docs
Perplexity To verify GitHub: pairing not named in vendor docs; Reclaim: pairing not named in vendor docs

Computed from the MCP and API steps only: "Confirmed" needs the tool's docs to name the platform and the platform to support the connection. Browser, upload and human steps work from any platform.

Sources

To verify Reclaim MCP in Cursor

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.