# Jira Service Management MCP

Connects your AI agent to Jira Service Management Cloud and Assets CMDB. It tracks SLA breaches across queues and manages internal ticket updates.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed · ★ 63
- Author: Servosity
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Servosity/msp-skills/tree/HEAD/skills/jira-service-management
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/jira-service-management-mcp

## What it 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.

## Requirements
- Environment variables: `JIRA_SERVICE_MANAGEMENT_API_TOKEN`, `JIRA_SERVICE_MANAGEMENT_CLOUD_ID`, `JIRA_SERVICE_MANAGEMENT_EMAIL`, `JIRA_SERVICE_MANAGEMENT_SITE`, `JIRA_SERVICE_MANAGEMENT_WORKSPACE_ID`, `JIRA_SERVICE_MANAGEMENT_BASE_URL`, `JIRA_SERVICE_MANAGEMENT_MCP_READ_ONLY`, `JIRA_SERVICE_MANAGEMENT_MCP_HTTP_TOKEN`, `JIRA_SERVICE_MANAGEMENT_USER_AGENT`, `PRINTING_PRESS_CLIENT_PROFILE` — keys and tokens: ask the human for the values, never commit them or put them in shared files.
- Works with: Jira

## Install

### Claude Code (native platform)

**Install**
- The MCP registry has no launch command for it: see the repository README

## When to use it
- 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
- 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

## Similar
- [Reactive Resume](https://affpapa.org/en/nevibecode/mcp/reactive-resume.md) — MCP server · ★ 44908
- [screenpipe](https://affpapa.org/en/nevibecode/mcp/screenpipe.md) — MCP server · ★ 22082
- [Inbox Zero](https://affpapa.org/en/nevibecode/mcp/inbox-zero.md) — MCP server · ★ 12826
- [kaneo](https://affpapa.org/en/nevibecode/mcp/kaneo.md) — MCP server · ★ 9623
- [Mindwtr](https://affpapa.org/en/nevibecode/mcp/mindwtr.md) — MCP server · ★ 2330
- [Azure DevOps (ADO)](https://affpapa.org/en/nevibecode/mcp/azure-devops-ado.md) — MCP server · ★ 2071

From the same set: [servosity/msp-skills](https://affpapa.org/en/nevibecode/by/servosity/msp-skills.md) — 73 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md