# GitScrum Sprints MCP for AI Agents AI Agent Connect > GitScrum Sprints lets you manage agile project cycles directly through your AI agent. You can plan sprints, track velocity, and manage user stories without leaving your chat interface. It pulls real-time data from GitScrum so you can stay on top of your team's progress without manual dashboard hunting. ## Overview - **Category:** productivity - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_gl0YafYnxyRI6m0DWiP1wBYnwK8MYx5Y5DVvPrri/ai-agent-connect - **Tags:** sprint-planning, agile-methodology, burndown-charts, velocity-tracking, user-stories, epic-management, kpi-analytics ## Description Managing a complex agile workflow usually means jumping between different tabs to check progress, look at burndown charts, and update user stories. It's a constant context switch that breaks your focus. This Connector changes that by bringing your GitScrum data directly into your workspace. Instead of hunting for a specific KPI or trying to remember how many story points are left in a sprint, you just ask your agent. You can get a summary of a team's velocity, check the status of specific tasks, or create new user stories on the fly. It's about getting answers in seconds rather than clicking through three levels of navigation. Because Vinkius hosts this integration, you get a reliable way to connect your project management data to the tools you already use every day. You stop being a data entry clerk for your own project and start actually managing the work. ## Tools ### get_task Pull details for a specific task using its UUID. It helps you drill down into individual items. ### all_sprints List every sprint across all your workspaces. It helps you see the big picture of your entire portfolio. ### create_user_story Create a new user story in your project. This makes adding requirements to your backlog much faster. ### list_epics See all epics within a specific project. It helps you stay aligned with high-level goals. ### create_sprint Start a new sprint cycle. You can set specific dates and configurations quickly. ### delete_sprint Remove an existing sprint from your project. Use this only when a sprint is no longer needed. ### sprint_metrics Get a deep dive into your sprint metrics. It provides the raw data needed for detailed analysis. ### sprint_progress Check the current progress of a sprint. It shows you exactly what's done and what's left. ### sprint_stats Get a high level summary of sprint statistics. This is great for a quick health check. ### get_sprint Pull specific details for a single sprint. Use this to see the full configuration of a cycle. ### sprint_kpis Get your key performance indicators for a sprint. It highlights the most important success metrics. ### list_sprints See all sprints within one specific project. This helps you manage a single product's timeline. ### sprint_reports Get burndown, burnup, and performance reports. It provides visual data for your team's progress. ### update_sprint Modify an existing sprint's details. Use this to adjust dates or configurations as needed. ### list_tasks See all tasks in a project or a specific sprint. You can filter by status like todo or done. ### list_user_stories See all user stories in a project. It gives you a full view of your project requirements. ## Prompt Examples **Prompt:** ``` What's the progress of our current sprint in the web-app project? ``` **Response:** ``` Sprint 'Sprint 14 — Auth Module' is at 68% completion: 17 of 25 tasks done, 5 in progress, 3 in backlog. Velocity is tracking above average at 34 story points. The sprint ends in 4 days. Shall I show you the burndown chart or the remaining in-progress tasks? ``` **Prompt:** ``` Create a new sprint 'Sprint 15 — Payments' from April 14 to April 28. ``` **Response:** ``` Sprint created! 'Sprint 15 — Payments' runs from 2026-04-14 to 2026-04-28 (2-week cycle). The sprint is empty. Would you like me to list the backlog tasks to assign into it, or create user stories for the payments feature? ``` **Prompt:** ``` Show me the velocity metrics for the last completed sprint. ``` **Response:** ``` Sprint 13 metrics: velocity of 31 story points (vs 28 average), throughput of 22 tasks completed, cycle time averaging 2.1 days per task. The team improved 11% over Sprint 12. Member distribution: johndoe (12 tasks), janedoe (7), alexdev (3). Want me to compare with earlier sprints? ``` ## Capabilities ### Track sprint velocity See how much work your team actually finishes over time. ### Manage user stories Create and organize new requirements without manual entry. ### Monitor burndown charts Get a clear picture of remaining work in any sprint. ### View project epics See the high-level goals and stories grouped by project. ### Analyze team throughput Identify bottlenecks by looking at task completion stats. ## Use Cases ### Standup Check A Scrum Master asks "What's the progress of our current sprint?" and gets a summary of tasks done vs. in progress. ### Velocity Review An Engineering Manager asks for velocity metrics from the last sprint to see if the team improved. ### Backlog Grooming A Product Owner tells the agent to create a new sprint and then asks it to list backlog tasks to assign. ### Portfolio Audit A manager uses all_sprints to see the status of every active sprint across all company workspaces. ## Benefits - Stop manual dashboard hopping by using sprint_progress to get instant updates. - Get real-time velocity data with sprint_metrics to see how your team is actually performing. - Manage your backlog faster by using create_user_story to add requirements via chat. - View high-level goals easily with list_epics to keep the team aligned on the big picture. - Monitor your burn rate with sprint_reports to see if you'll hit your sprint goals on time. - Track team output across your whole company using all_sprints for portfolio oversight. ## How It Works The bottom line is you get instant access to your agile project data without opening a browser. 1. Connect your GitScrum account to the Vinkius marketplace. 2. Provide your company slug and API token in the configuration. 3. Ask your agent for sprint updates or to create new backlog items. ## Frequently Asked Questions **Can GitScrum Sprints help me track my team's velocity?** Yes, it pulls your velocity metrics directly. You can ask your agent to compare current performance against past sprints to see if your team is getting faster. **How do I use GitScrum Sprints for sprint planning?** You can ask your agent to create new sprints with specific dates. It can also list your existing backlog so you can decide which tasks to pull into the next cycle. **Can I see burndown charts with GitScrum Sprints?** Yes, it retrieves data for burndown and burnup charts. Your agent can summarize these reports to tell you if you're on track to finish your sprint goals. **Does GitScrum Sprints work with Claude or Cursor?** Yes, it works with any MCP-compatible client. Once you connect it through Vinkius, you can use it in Claude, Cursor, Windsurf, or VS Code. **Can I manage user stories using GitScrum Sprints?** You can create new user stories and list existing ones within your projects. This helps you manage your backlog without having to switch away from your chat interface. **Is GitScrum Sprints good for Engineering Managers?** It's great for tracking throughput and identifying bottlenecks. You can pull stats across multiple workspaces to get a high-level view of your entire engineering organization. **Can my AI agent show me the burndown chart data for the current sprint?** Yes! Use `sprint_reports` with the resource set to 'burndown'. Your agent returns the ideal versus actual burn-down data points, so you can visualize or analyze sprint health instantly. You can also request 'burnup', 'performance', or 'member_distribution' reports. **Can I see what tasks are in a specific sprint?** Absolutely. Use `list_tasks` with the `sprint_slug` filter to see only tasks belonging to that sprint. You can further filter by status (todo, in-progress, done) to focus on what matters. Then use `get_task` to drill into any specific task for full details. **Does this integration support sprint velocity and metrics tracking?** Yes. Use `sprint_metrics` for detailed velocity, throughput, and efficiency data. Combined with `sprint_kpis` for high-level indicators and `sprint_stats` for task distribution analysis, you get a complete performance picture across any sprint.