# GitScrum Sprints MCP > GitScrum Sprints manages your entire agile development lifecycle through an AI agent. It lets you plan sprints, track user stories from epic to task, and generate detailed performance reports on demand. You can monitor velocity trends, review burndown charts, and manage multiple project backlogs without leaving your chat window. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** sprint-planning, agile-methodology, burndown-charts, velocity-tracking, user-stories, epic-management, kpi-analytics ## Description Forget navigating separate dashboards just to see if the team hit their goal. This MCP connects directly to GitScrum, giving your AI agent a single source of truth for all things development progress. You ask it about sprint status or velocity, and it synthesizes data across every connected workspace instantly. It aggregates complex metrics—like burnup charts and task completion rates—and gives you plain English answers, instead of spreadsheets full of raw numbers. By connecting the GitScrum Sprints MCP via Vinkius, your agent gains instant visibility into everything from initial epic creation to final sprint updates, letting you focus on product strategy, not data gathering. ## Tools ### all_sprints Retrieves a list of all active and past sprints across every workspace in your account. ### create_user_story Adds a new user story to the project backlog. ### list_epics Fetches all epics associated with a specific project or portfolio. ### create_sprint Sets up a brand new sprint cycle with defined start and end dates. ### get_sprint Pulls detailed information for one specific sprint ID. ### sprint_kpis Calculates and returns a set of key performance indicators for the current sprint cycle. ### list_sprints Gets a list of sprints that belong to a single, defined project. ### sprint_metrics Provides deep, detailed statistics covering effort, type distribution, and task counts for a given sprint. ### sprint_progress Calculates the current completion percentage of an active sprint against its goal. ### sprint_reports Generates comprehensive reports, including data needed for burndown and burnup charts. ### sprint_stats Gathers general statistical summaries about a specific sprint's performance history. ### update_sprint Modifies the date range or name of an existing sprint cycle. ### get_task Retrieves granular details about a single task using its unique identifier. ### list_tasks Shows tasks in a project, allowing you to filter them by specific sprints and statuses (To Do, In Progress, Done). ### list_user_stories Lists all user stories currently available within the project backlog. ## 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 ### Plan and structure entire sprints Create new sprints or review existing ones with specific date ranges. ### Manage project backlogs List, browse, and create user stories and epics to map out future development work. ### Track task status in real time Retrieve all tasks within a specific sprint, filtering them by their current status (To Do, In Progress, Done). ### Analyze team performance metrics Access detailed Key Performance Indicators and velocity reports for any completed or active sprint. ### Generate visual progress reports Pull data needed for burndown, burnup, and distribution charts for deep-dive analysis. ## Use Cases ### The Product Owner needs to justify the next quarter's budget. Instead of compiling data from three different boards, ask your agent: 'What were our key performance indicators (`sprint_kpis`) and overall velocity trends across the last four sprints?' The agent aggregates all `sprint_metrics` and delivers a ready-to-present summary. ### The Scrum Master is running a complex retro meeting. You prompt: 'Show me the full report on Sprint 13, including member distribution and type breakdown.' The agent uses `sprint_reports` to deliver everything needed for discussion—who did what, and which parts of the backlog were hardest. ### The Engineering Manager needs to check resource capacity. You ask: 'What is the current progress (`sprint_progress`) and total task count for the Auth Module sprint?' The agent uses `get_sprint` combined with `list_tasks`, giving you a definitive, real-time number. ### The PM is onboarding a new feature into the roadmap. You prompt: 'List all epics in the Payments domain and suggest user stories for the first sprint.' The agent uses `list_epics` to find the scope, then prompts you to use `create_user_story` to start populating the backlog. ## Benefits - Instant KPI checks: Instead of digging through reports to find the velocity number, ask for `sprint_kpis` and get an immediate read on team health. This is huge during standups. - Full lifecycle view: Need to see how a new feature (an epic) translates into actionable tasks? You can list epics and then drill down through user stories and tasks using the available tools. - Multi-workspace oversight: The `all_sprints` tool lets your agent check status across every project in your portfolio, which is critical for executive reporting without switching tabs. - Deep historical analysis: Don't just know *if* you finished; know *how*. Use the `sprint_reports` function to pull data needed for burndown and burnup charts immediately. - Structured planning: Quickly set up the next cycle using `create_sprint`. Then, prompt your agent to list backlogged items so you can assign them right away. - Task status clarity: Need to know which tasks are stuck? Run a query that uses `list_tasks` filtered by a specific sprint and status to pinpoint bottlenecks. ## How It Works The bottom line is: the MCP translates complex agile data into simple conversations with your AI client. 1. Subscribe to the GitScrum Sprints MCP from Vinkius. Then, enter your required GitScrum API token and company slug into the connection settings. 2. Give a natural language prompt to your AI client, asking it to review sprint progress or analyze velocity trends for a specific project. 3. Your agent pulls all necessary data—like task status or KPI metrics—and delivers structured, actionable insights directly back to you. ## Frequently Asked Questions **How do I check progress on multiple projects? (all_sprints)** You use the `all_sprints` tool to get a consolidated view of every sprint across all your workspaces. This is essential for portfolio-level oversight when you need to compare different teams' performance side-by-side. **What kind of reports can I generate using sprint_reports?** The `sprint_reports` tool generates several types of data, including the information needed for burndown charts, burnup charts, and task type distribution. This gives you a full picture of effort versus completion. **How do I get all user stories in the current project? (list_user_stories)** Running `list_user_stories` pulls every story from the backlog for that project. This is your starting point when you need to scope out a new feature or update the roadmap. **Can I see all tasks assigned to one sprint? (list_tasks)** Yes, using `list_tasks` and filtering by the sprint slug is the way to go. This shows you every task associated with that cycle, allowing you to check status or identify bottlenecks. **What details must I provide when running the `create_user_story` tool?** You need to specify a title, detailed description, and optionally link it to an existing epic. This action immediately adds the story to the project's backlog for review. **What information can I retrieve about a single item using the `get_task` tool?** The `get_task` tool requires a unique UUID and returns all associated details. You get the task's current status, assignee, estimated effort, and its parent story or epic. **Before planning, how does `list_epics` help me see the full scope of a project?** It provides an overview of major project containers. Instead of navigating through hundreds of individual stories, you can list all epics to grasp the overall structure and planned features. **What parameters must I provide when calling the `create_sprint` tool?** You must define a unique name for the sprint, along with a clear start date and an end date. The MCP uses this information to correctly set the boundaries for all related tasks. **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.