2,500+ MCP servers ready to use
Vinkius

Jira Service Management (JSM) MCP Server for Cursor 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 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 Jira Service Management (JSM) 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": {
    "jira-service-management-jsm": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Jira Service Management (JSM)
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 Jira Service Management (JSM) MCP Server

Empower your AI agents with Jira Service Management's leading ITSM platform. This MCP server allows you to list service desks, retrieve customer requests, manage organizations and queues, and access knowledge base articles directly through the Jira JSM API. Ideal for automating IT support and service delivery workflows.

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

The Jira Service Management (JSM) MCP Server exposes 10 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 Jira Service Management (JSM) to Cursor via MCP

Follow these steps to integrate the Jira Service Management (JSM) 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 Jira Service Management (JSM)

Open Agent mode in chat and ask: "Using Jira Service Management (JSM), help me..."10 tools available

Why Use Cursor with the Jira Service Management (JSM) MCP Server

Cursor AI Code Editor provides unique advantages when paired with Jira Service Management (JSM) 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

Jira Service Management (JSM) + Cursor Use Cases

Practical scenarios where Cursor combined with the Jira Service Management (JSM) 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

Jira Service Management (JSM) MCP Tools for Cursor (10)

These 10 tools become available when you connect Jira Service Management (JSM) to Cursor via MCP:

01

get_info

Use for system health monitoring. Retrieves system information for the JSM instance

02

get_request

g., "SD-123") or ID. Returns full descriptions, participants, and custom field values. Use this for deep investigation of a specific customer inquiry. Retrieves details for a specific customer request

03

get_service_desk

Returns project information and branding details. Useful for understanding the configuration of a specific support portal. Retrieves details for a specific service desk

04

list_customers

Useful for identifying support recipients and their account details. Lists all customers for a specific service desk

05

list_knowledge_bases

Essential for identifying available documentation that might help resolve common customer issues. Lists all knowledge base articles for a specific service desk

06

list_organizations

Useful for understanding which business entities are being supported and grouping support data by customer. Lists all organizations in JSM

07

list_queues

g., "All Open", "Unassigned") defined for a service desk. Useful for understanding how tickets are triaged and identifying backlog counts. Lists all queues for a specific service desk

08

list_request_types

g., "IT Help", "Hardware Request") available in a portal. Useful for understanding the service catalog of a specific team. Lists all request types for a specific service desk

09

list_requests

Includes request keys, summaries, and current status. Essential for monitoring the support queue and identifying urgent issues. Lists all customer requests

10

list_service_desks

Returns project keys, names, and IDs. Use this to identify the service desk ID before querying requests or queues. Lists all service desks

Example Prompts for Jira Service Management (JSM) in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Jira Service Management (JSM) immediately.

01

"List all active service desks in JSM."

02

"Show me the latest customer requests."

03

"Check the queues for service desk ID '1'."

Troubleshooting Jira Service Management (JSM) MCP Server with Cursor

Common issues when connecting Jira Service Management (JSM) 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.

Jira Service Management (JSM) + Cursor FAQ

Common questions about integrating Jira Service Management (JSM) 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 Jira Service Management (JSM) to Cursor

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