VS Code CopilotIDE

Why use GitScrum Sprints MCP Server with VS Code Copilot?

Bring Sprint Planning
to VS Code Copilot

Name: GitScrum Sprints MCP Server
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Create your Vinkius account to connect GitScrum Sprints to VS Code Copilot and start using all 15 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

GDPR Free for Subscribers

All SprintsCreate SprintCreate User StoryGet SprintGet TaskList EpicsList SprintsList TasksList User StoriesSprint KpisSprint MetricsSprint ProgressSprint ReportsSprint StatsUpdate Sprint

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the 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

How it works

Subscribe to the GitScrum Sprints integration from the marketplace
Enter your GitScrum API token and company slug
Ask your agent to review sprint progress, analyze velocity trends, or plan the next iteration — works in Claude, Cursor, and any MCP client

Your agent delivers sprint analytics and agile insights without requiring manual dashboard navigation.

Who is this for?

Scrum masters — review sprint KPIs and progress during standups and retrospectives
Engineering managers — track velocity trends and team throughput across sprints
Product owners — manage user stories and epics while monitoring delivery cadence

Built-in capabilities (15)

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

See what your AI agent can do with GitScrum Sprints

Why VS Code Copilot?

GitHub Copilot Agent mode brings GitScrum Sprints data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 15 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

GitScrum Sprints in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Enterprise Security

Why run GitScrum Sprints with Vinkius?

The GitScrum Sprints connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 15 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

View full GitScrum Sprints details →

Fully ManagedNo server setup

Plug & PlayNo coding needed

SecurePrivacy protected

PrivateYour data is safe

Cost ControlBudget limits

Control1-click disconnect

Auto-UpdatesMaintenance free

High SpeedOptimized for AI

Reliable99.9% uptime

Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents

Complete visibility into every agent action

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect GitScrum Sprints using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Explore Analytics

Why Vinkius

GitScrum Sprints and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect GitScrum Sprints to VS Code Copilot through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations

<40msResponse time

100%Fully managed

	Raw MCP	Vinkius
Ready-to-use MCPs	Find and configure each manually	4,000+ MCPs ready to use
Connection Setup	Manual coding & server setup	1-click instant connection
Server Hosting	You host it yourself (needs 24/7 uptime)	100% hosted & managed by Vinkius
Security & Privacy	Stored in plaintext config files	Bank-grade encrypted vault
Activity Visibility	Blind execution (no logs or tracking)	Live dashboard with real-time logs
Cost Control	Runaway AI token spend risk	Automatic budget limits
Revoking Access	Must delete files or code to stop	1-click disconnect button

View step-by-step setup guide for VS Code Copilot →

The Vinkius Advantage

How Vinkius secures
GitScrum Sprints for VS Code Copilot

Every request between VS Code Copilot and GitScrum Sprints is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

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.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.