2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 28 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.

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

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

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

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

01

Open MCP Settings

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

02

Add the server config

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

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using GitScrum Tasks

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

Why Use Cursor with the GitScrum Tasks MCP Server

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

01

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

02

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

03

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

04

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

GitScrum Tasks + Cursor Use Cases

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

01

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

02

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

03

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

04

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

GitScrum Tasks MCP Tools for Cursor (28)

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

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

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

01

Tools not appearing in Cursor

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

Server shows as disconnected

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

GitScrum Tasks + Cursor FAQ

Common questions about integrating GitScrum Tasks MCP Server with Cursor.

01

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

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

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

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.

Connect GitScrum Tasks to Cursor

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