2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 28 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 Tasks 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-tasks": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
GitScrum Tasks
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 Tasks MCP Server

What you can do

  • Full task lifecycle — create, update, delete, and toggle completion on tasks with rich metadata including types, effort levels, and dates
  • Advanced filtering — query tasks by status, sprint, user story, assignee, label, type, effort, workflow column, blocker flag, and date ranges
  • Subtask management — list, link, unlink subtasks and discover related tasks across your project
  • Checklists — add checklist items with sub-items and toggle completion for granular progress tracking
  • Team coordination — assign and unassign members, duplicate tasks, move between projects, and set story points
  • Comments — list, create, update, and delete task comments for rich collaboration context

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

The GitScrum Tasks MCP Server exposes 28 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 Tasks to VS Code Copilot via MCP

Follow these steps to integrate the GitScrum Tasks 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 Tasks

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

Why Use VS Code Copilot with the GitScrum Tasks MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with GitScrum Tasks 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 Tasks + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GitScrum Tasks 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 Tasks MCP Tools for VS Code Copilot (28)

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

01

assign_member

Assign a user to a task

02

create_checklist_item

Use parent_id to create sub-items. Add a checklist item to a task

03

create_comment

Supports rich text content. Add a comment to a task

04

create_task

Create a new task

05

create_task_type

g., Chore, Tech Debt) with a hex color code. Create a new task type

06

delete_comment

Delete a comment

07

delete_task

This action cannot be undone. Delete a task permanently

08

duplicate_task

Duplicate a task

09

get_task

Get task details by UUID

10

get_task_by_code

g., WEB-42) instead of UUID. Get task by human-readable code

11

link_subtask

Link an existing task as a subtask

12

list_checklists

List checklists on a task

13

list_comments

Comments support rich text. List comments on a task

14

list_effort_levels

List effort/priority levels

15

list_subtasks

List subtasks of a task

16

list_task_types

) with their colors. List task types in a project

17

list_tasks

Filter by status (todo, in-progress, done), sprint, user_story, users, labels, type, effort, workflow, is_blocker, is_archived, unassigned, created_at (YYYY-MM-DD=YYYY-MM-DD), closed_at, per_page. List tasks with advanced filters

18

move_task_to_project

Move a task to a different project

19

my_tasks

Get all tasks assigned to me

20

my_today_tasks

Get tasks due today

21

related_tasks

Get tasks related to a task

22

set_task_estimate

Set story points / estimate for a task

23

toggle_checklist_item

Toggle a checklist item done/undone

24

toggle_task_done

Toggle task completion status

25

unassign_member

Remove a user from a task

26

unlink_subtask

Unlink a subtask

27

update_comment

Edit an existing comment

28

update_task

Update an existing task

Example Prompts for GitScrum Tasks in VS Code Copilot

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

01

"Show me all in-progress tasks in the web-app project."

02

"Create a bug task 'Login timeout on slow connections' in web-app and assign it to janedoe."

03

"Add a checklist to task WEB-42 with items for 'Write unit tests', 'Update docs', and 'Deploy to staging'."

Troubleshooting GitScrum Tasks MCP Server with VS Code Copilot

Common issues when connecting GitScrum Tasks 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 Tasks + VS Code Copilot FAQ

Common questions about integrating GitScrum Tasks 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 Tasks to VS Code Copilot

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