Jira Service Management MCP

Jira Service Management + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Jira Service Management

API. Not affiliated with, endorsed by, or sponsored by Atlassian Pty Ltd.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every Jira Service Management Cloud request-API (servicedeskapi) and Assets endpoint in one binary, plus SLA breach ranking across queues, internal notes that stay internal, ticket timelines, and Assets (CMDB)-to-ticket joins. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs jira-service-management-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Jira Service Management MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Jira Service Management release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install jira-service-management@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Jira Service Management Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.ps1 | iex. Then authenticate per the README and run jira-service-management-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.sh)

The installer drops both jira-service-management-cli (the CLI) and jira-service-management-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

jira-service-management-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update jira-service-management@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/jira-service-management --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/jira-service-management --force

Hermes speaks MCP natively, so it can also use the jira-service-management-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the jira-service-management skill from https://github.com/servosity/msp-skills/tree/main/skills/jira-service-management. The skill defines how its required CLI (jira-service-management-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Create an Atlassian API token at id.atlassian.com/manage-profile/security/api-tokens, signed in as an agent on your JSM site. Then set three variables: your site subdomain (acme for acme.atlassian.net), your Atlassian email, and the token.

macOS / Linux:

export JIRA_SERVICE_MANAGEMENT_SITE=acme

export JIRA_SERVICE_MANAGEMENT_EMAIL=you@example.com export JIRA_SERVICE_MANAGEMENT_API_TOKEN= jira-service-management-cli doctor

Windows (PowerShell):

$env:JIRA_SERVICE_MANAGEMENT_SITE = "acme"

$env:JIRA_SERVICE_MANAGEMENT_EMAIL = "you@example.com" $env:JIRA_SERVICE_MANAGEMENT_API_TOKEN = " " jira-service-management-cli doctor

Assets (CMDB) commands also need your site's cloudId and Assets workspaceId (Assets is part of JSM Premium and Enterprise). Run jira-service-management-cli cmdb discover --save once per client site to look both up and store them in the config file for that site; saved ids apply only to the site they were found for. As a backstop, every Assets call is refused unless its cloudId is the current site's (checked once per run against the site's public tenant_info) and its workspaceId is one the site lists, so a leftover JIRA_SERVICE_MANAGEMENT_CLOUD_ID or _WORKSPACE_ID from another client can never point Assets at that client's CMDB. Environment values win over saved ids, so unset them when you switch sites.

doctor checks config and paths, names any missing SITE, EMAIL or API_TOKEN, and verifies the token with one authenticated read (GET /servicedesk).

What this skill does

client and sla-report read the local copy: run jira-service-management-cli sync --resources organization,request,requesttype,servicedesk first. Everything else reads live.

Through the MCP server, cmdb reconcile reads an export only from inside the server's working directory, and refuses to run when that directory is a filesystem root or your home folder (so it cannot be used to read arbitrary files). If your MCP host starts servers from / or your home folder, run cmdb reconcile from the CLI in the folder that holds the export instead.

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Jira Service Management integrations and MCP servers proxy each question into a live API call. That's fine for one record. It breaks down when you ask "which of our 300 open tickets breach SLA next": no single API