Jira Service Management MCP — Claude Code MCP server: setup guide
Connects your AI agent to Jira Service Management Cloud and Assets CMDB. It tracks SLA breaches across queues and manages internal ticket updates.
Open on GitHubWhat Jira Service Management MCP does
The server packages Jira Service Desk REST endpoints and Assets schema calls into a single binary. It gives assistants visibility into helpdesk queues, ticket histories, and configuration items. Support staff can rank issues by urgency and post private internal notes without exposing them to end customers.
Setup delivers two distinct executables to your path: jira-service-management-cli and jira-service-management-mcp. The assistant queries the Atlassian cloud directly using your provisioned credentials.
Running in HTTP mode via --transport http remains unsafe in this release because the binary lacks request size caps and execution timeouts. Stick to the default stdio transport to prevent external exploitation.
What it helps with
- link CMDB assets to incident tickets
- prioritize helpdesk tickets by SLA breach risk
- submit staff-only internal notes on requests
- inspect ticket activity timelines
Example prompts for the agent
- Check the active queue and list tickets closest to an SLA breach
- Link the affected laptop asset to ticket HD-104
- Add an internal private note to ticket SD-218 detailing the diagnostic output
How to install Jira Service Management MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Jira Service Management MCP
How do I install Jira Service Management MCP in Claude Code?
Register the marketplace with /plugin marketplace add Servosity/msp-skills, then install the component using /plugin install jira-service-management@msp-skills.
What does Jira Service Management MCP do?
It bridges AI agents with Jira Service Management and Assets endpoints to automate triage, SLA monitoring, and CMDB linking.
Can I run this server over network HTTP?
The developer advises against --transport http until incoming request limits are added. You should run the tool via local stdio communication instead.
