2,500+ MCP servers ready to use
Vinkius

GitScrum Tasks MCP Server for Claude Desktop 28 tools — connect in under 2 minutes

Built by Vinkius GDPR 28 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "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

Claude Desktop is the definitive way to connect GitScrum Tasks to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 28 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

The GitScrum Tasks MCP Server exposes 28 tools through the Vinkius. Connect it to Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the GitScrum Tasks MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using GitScrum Tasks

Look for the 🔌 icon in the chat. your 28 tools are now available

Why Use Claude Desktop with the GitScrum Tasks MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with GitScrum Tasks through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

GitScrum Tasks + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the GitScrum Tasks MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

GitScrum Tasks MCP Tools for Claude Desktop (28)

These 28 tools become available when you connect GitScrum Tasks to Claude Desktop 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 Claude Desktop

Ready-to-use prompts you can give your Claude Desktop 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 Claude Desktop

Common issues when connecting GitScrum Tasks to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

GitScrum Tasks + Claude Desktop FAQ

Common questions about integrating GitScrum Tasks MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect GitScrum Tasks to Claude Desktop

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