An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Jira Service Management Jsm to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Automate your IT support and service desk workflows.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Jira Service Management.

  1. 01

    List organizations

    This capability lists all organizations within JSM. It's useful for grouping support data by customer or business entity.

  2. 02

    List service desks

    This capability lists all available service desks. It returns project keys, names, and IDs so your agent can identify the correct desk to query.

  3. 03

    Get info

    This capability retrieves system information for your JSM instance. You can use it to monitor the health of your system.

  4. 04

    Get request

    This capability pulls the full details for a specific customer request using its ID or key. It provides descriptions, participants, and custom field values for deep investigation.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Jira Service Management.

  1. 05

    Get service desk

    This capability retrieves details for a specific service desk. It returns project information and branding details to help understand portal configurations.

  2. 06

    List customers

    This capability lists all customers for a specific service desk. Use it to identify support recipients and their account details.

  3. 07

    List knowledge bases

    This capability lists all knowledge base articles for a specific service desk. It helps your agent find documentation to resolve common issues.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Jira Service Management.

  1. 08

    List queues

    This capability lists all queues for a specific service desk. Use it to see how tickets are triaged or to check the count of items in the backlog.

  2. 09

    List request types

    This capability returns the request types available in a portal. It helps your agent understand the service catalog for a specific team.

  3. 10

    List requests

    This capability lists all customer requests. It provides request keys, summaries, and current statuses to help monitor the support queue.

Real work

What teams actually run

01

Automated Ticket Triage

Your agent monitors queues and identifies urgent requests based on their status.

02

Customer Support Assistance

Your agent pulls request details and knowledge base articles to help resolve user inquiries.

03

Service Catalog Management

Your agent checks available request types to inform users what services are offered.

04

Organization Auditing

Your agent lists organizations to help you understand which business entities are using support.

Automate a task

Put Jira Service Management to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Jira Service Management works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Jira Service Management to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

877ms average. Fast in production.

Jira Service Management is checked daily against the live service.

Daily averagePeak 1004ms
Oct 3Today
Fastest day
720ms
Slowest day
1004ms
14-day trend
Slowing+20%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Jira Service Management, so you can see the experience inside your AI.

It does not authenticate your account with Jira Service Management. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Jira Service Management Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_tI7XM1qch201nTS7j7hYErs51QO1nPjtHqKTsPsi/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Jira Service Management capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "jira-service-management-jsm-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_tI7XM1qch201nTS7j7hYErs51QO1nPjtHqKTsPsi/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Jira Service Management in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Jira Service Management owners hand off.

This MCP is built for teams running IT or customer service operations through Jira Service Management.

  • 01

    IT Support Agents

    They hand off ticket lookups and queue monitoring to their agent.

  • 02

    Service Desk Managers

    They use the agent to get high-level views of service desks and organizations.

  • 03

    DevOps Engineers

    They use the agent to monitor system health and service desk configurations.

FAQ

Questions Jira Service Management owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You connect once through your MCP-compatible client like Claude, Cursor, or Windsurf. Vinkius hosts the MCP and manages the connection for you.

  • 02

    Do I need to manage my own API keys?

    Vinkius manages the credentials and hosting, so you don't have to deal with the underlying API management yourself.

  • 03

    Which AI clients can use this JSM MCP?

    Any MCP-compatible client works, including Claude, Cursor, Windsurf, and VS Code.

  • 04

    Can my agent read my knowledge base articles?

    Yes, the MCP includes a capability to list knowledge base articles for your specific service desks.

  • 05

    Is this only for IT support?

    While it is built for ITSM, any team using Jira Service Management for customer requests or service delivery can use these capabilities.

  • 06

    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.

  • 07

    Can I see requests from all service desks?

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

  • 08

    Are knowledge base articles supported?

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

Explore

More in Industry Titans

Suggestions

Connect Jira Service Management to Claude, Cursor, ChatGPT & more