Can my AI agent list all workspaces and drill into specific project details?

Absolutely. Use `list_workspaces` to browse all your organizational workspaces, then `list_projects` to see every project within a workspace. Your agent returns full metadata including member counts, settings, and creation dates — all without leaving your conversation.

I need to set up a new project with custom workflows and labels — can I do it all conversationally?

Yes. Tell your agent to create the project, then ask it to configure the workflow columns and create color-coded labels. The agent chains `create_project`, `list_workflows`, and `create_label` tools automatically to set up your board exactly as you describe it.

Does this integration let me modify or delete projects?

This core integration focuses on workspace exploration, project creation, and configuration management — including workflows and labels. For task-level operations like CRUD, subtasks, and checklists, use the dedicated GitScrum Tasks integration. All actions respect your GitScrum account permissions.

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

Name: GitScrum
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

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.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "gitscrum": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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

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

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

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

Open MCP Settings

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

Add the server config

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

Save the file

Cursor will automatically detect the new MCP server

Start using GitScrum

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

Why Use Cursor with the GitScrum MCP Server

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

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

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

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

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

GitScrum + Cursor Use Cases

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

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

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

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

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

GitScrum MCP Tools for Cursor (16)

These 16 tools become available when you connect GitScrum to Cursor via MCP:

create_project

Create a new project

create_workspace

Create a new workspace

find_project

Find a project by name

get_me

Get authenticated user profile

get_project

Get project details

get_task

Get task details by UUID

get_workspace

Get workspace details

list_labels

List labels in a project

list_project_members

List members in a project

list_projects

List projects in a workspace

list_tasks

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

list_workflows

List workflows (columns) in a project

list_workspaces

List all GitScrum workspaces

my_role

Get my role in the workspace

project_stats

Get project statistics

workspace_stats

Get workspace statistics

Example Prompts for GitScrum in Cursor

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

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

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

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

Troubleshooting GitScrum MCP Server with Cursor

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

Tools not appearing in Cursor

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

Server shows as disconnected

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

GitScrum + Cursor FAQ

Common questions about integrating GitScrum MCP Server with Cursor.

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.

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.

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.

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.