2,500+ MCP servers ready to use
Vinkius

GitScrum MCP Server for VS Code Copilot 16 tools — connect in under 2 minutes

Built by Vinkius GDPR 16 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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 and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "gitscrum": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
GitScrum
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 MCP Server

What you can do

  • Browse workspaces — list all your organizational workspaces and retrieve details for each one
  • Manage projects — list, create, and inspect projects with full metadata including members and settings
  • Configure workflows — view and manage Kanban column definitions and workflow templates
  • Organize with labels — list, create, and update color-coded labels to categorize work
  • Access your profile — retrieve the authenticated user's profile across all workspaces

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

The GitScrum MCP Server exposes 16 tools through the Vinkius. Connect it to VS Code Copilot 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 to VS Code Copilot via MCP

Follow these steps to integrate the GitScrum MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using GitScrum

Ask Copilot: "Using GitScrum, help me...". 16 tools available

Why Use VS Code Copilot with the GitScrum MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with GitScrum through the Model Context Protocol.

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

GitScrum + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GitScrum MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

GitScrum MCP Tools for VS Code Copilot (16)

These 16 tools become available when you connect GitScrum to VS Code Copilot via MCP:

01

create_project

Create a new project

02

create_workspace

Create a new workspace

03

find_project

Find a project by name

04

get_me

Get authenticated user profile

05

get_project

Get project details

06

get_task

Get task details by UUID

07

get_workspace

Get workspace details

08

list_labels

List labels in a project

09

list_project_members

List members in a project

10

list_projects

List projects in a workspace

11

list_tasks

Filter by status (todo, in-progress, done). Essential for understanding project scope and workload. List tasks in a project

12

list_workflows

List workflows (columns) in a project

13

list_workspaces

List all GitScrum workspaces

14

my_role

Get my role in the workspace

15

project_stats

Get project statistics

16

workspace_stats

Get workspace statistics

Example Prompts for GitScrum in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with GitScrum immediately.

01

"Show me all the workspaces I have access to on GitScrum."

02

"Create a new project called 'Mobile App v2' in the acme-eng workspace with a description."

03

"What labels are available in the web-app project?"

Troubleshooting GitScrum MCP Server with VS Code Copilot

Common issues when connecting GitScrum to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

GitScrum + VS Code Copilot FAQ

Common questions about integrating GitScrum MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect GitScrum to VS Code Copilot

Get your token, paste the configuration, and start using 16 tools in under 2 minutes. No API key management needed.