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.

GitScrum Sprints MCP Server for Cursor 15 tools — connect in under 2 minutes

Name: GitScrum Sprints
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 15 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install GitScrum Sprints and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "gitscrum-sprints": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About GitScrum Sprints MCP Server

What you can do

Sprint lifecycle — create, update, delete, and inspect sprints with precise date ranges and configurations
Performance analytics — access sprint KPIs, detailed statistics, progress tracking, and velocity metrics in real-time
Visual reports — retrieve burndown, burnup, performance, and distribution chart data for any sprint
Backlog management — list and create user stories, browse epics, and view tasks filtered by sprint
Cross-workspace visibility — list sprints across all workspaces for portfolio-level oversight

Cursor's Agent mode turns GitScrum Sprints into an in-editor superpower. Ask Cursor to generate code using live data from GitScrum Sprints and it fetches, processes, and writes. all in a single agentic loop. 15 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

The GitScrum Sprints MCP Server exposes 15 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect GitScrum Sprints to Cursor via MCP

Follow these steps to integrate the GitScrum Sprints MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using GitScrum Sprints

Open Agent mode in chat and ask: "Using GitScrum Sprints, help me...". 15 tools available

Why Use Cursor with the GitScrum Sprints MCP Server

Cursor AI Code Editor provides unique advantages when paired with GitScrum Sprints through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

GitScrum Sprints + Cursor Use Cases

Practical scenarios where Cursor combined with the GitScrum Sprints MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

GitScrum Sprints MCP Tools for Cursor (15)

These 15 tools become available when you connect GitScrum Sprints to Cursor via MCP:

all_sprints

List sprints across all workspaces

create_sprint

Create a new sprint

create_user_story

Create a user story

get_sprint

Get sprint details

get_task

Get task details by UUID

list_epics

List epics in a project

list_sprints

List sprints in a project

list_tasks

Use the sprint_slug filter to see only tasks belonging to a specific sprint. Filter by status (todo, in-progress, done). List tasks in a project, optionally filtered by sprint

list_user_stories

List user stories in a project

sprint_kpis

Get sprint KPIs

sprint_metrics

Get detailed sprint metrics

sprint_progress

Get current sprint progress

sprint_reports

Resource: burndown, burnup, performance, types, efforts, member_distribution, task, type_distribution. Get sprint reports with charts

sprint_stats

Get sprint statistics

update_sprint

Update an existing sprint

Example Prompts for GitScrum Sprints in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with GitScrum Sprints immediately.

"What's the progress of our current sprint in the web-app project?"

"Create a new sprint 'Sprint 15 — Payments' from April 14 to April 28."

"Show me the velocity metrics for the last completed sprint."

Troubleshooting GitScrum Sprints MCP Server with Cursor

Common issues when connecting GitScrum Sprints to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

GitScrum Sprints + Cursor FAQ

Common questions about integrating GitScrum Sprints MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.