How do I get Jira JSM API credentials?

You need your Jira instance domain (e.g., acme.atlassian.net), your account email, and an API Token. You can generate an API Token in your Atlassian Account Settings under Security > API Token.

Can I see requests from all service desks?

The list_requests tool allows you to retrieve customer requests across your Jira Service Management instance, subject to your account permissions.

Are knowledge base articles supported?

Yes, you can list knowledge base articles for a specific service desk using the list_knowledge_bases tool.

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

Name: Jira Service Management (JSM)
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

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

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 Jira Service Management (JSM) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "jira-service-management-jsm": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "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 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.

Claude Desktop is the definitive way to connect Jira Service Management (JSM) to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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

Follow these steps to integrate the Jira Service Management (JSM) MCP Server with Claude Desktop.

Open Claude Desktop Settings

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

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Jira Service Management (JSM)

Look for the 🔌 icon in the chat — your 10 tools are now available

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

Claude Desktop by Anthropic provides unique advantages when paired with Jira Service Management (JSM) through the Model Context Protocol.

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

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

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

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

Jira Service Management (JSM) + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Jira Service Management (JSM) MCP Server delivers measurable value.

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

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

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

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

Jira Service Management (JSM) MCP Tools for Claude Desktop (10)

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

get_info

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

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

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

list_customers

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

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

list_organizations

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

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

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

list_requests

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

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 Claude Desktop

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

"List all active service desks in JSM."

"Show me the latest customer requests."

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

Troubleshooting Jira Service Management (JSM) MCP Server with Claude Desktop

Common issues when connecting Jira Service Management (JSM) to Claude Desktop through the Vinkius, and how to resolve them.

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

Authentication error

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

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.

Jira Service Management (JSM) + Claude Desktop FAQ

Common questions about integrating Jira Service Management (JSM) MCP Server with Claude Desktop.

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.

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.

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.

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.

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.