What it does
Every Jira Service Management Cloud request-API (servicedeskapi) and Assets endpoint in one binary
- Connects 在你的电脑上运行
- Account or key Needs JIRA_SERVICE_MANAGEMENT_API_TOKEN, JIRA_SERVICE_MANAGEMENT_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE · 2 settings to fill in (JIRA_SERVICE_MANAGEMENT_EMAIL, JIRA_SERVICE_MANAGEMENT_SITE)
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
双击文件,然后在电脑版 Claude 应用中点击 Install
试一试
用 Jira Service Management MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Jira Service Management MCP,或回答中出现 Jira Service Management MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Jira Service Management MCP
Jira Service Management MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
你可以改用这些方式
A · 使用能连接 Jira Service Management MCP 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
B · 开发者工具 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code 暂时无法连接 Jira Service Management MCP
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Jira Service Management MCP 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
Cursor 暂时无法连接 Jira Service Management MCP
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Jira Service Management MCP 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
VS Code 暂时无法连接 Jira Service Management MCP
开发者只提供了电脑版 Claude 应用的安装文件
你可以改用这些方式
A · 使用能连接 Jira Service Management MCP 的应用
- 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
开发者专用:终端命令和 JSON 设置
需要你填写的值
JIRA_SERVICE_MANAGEMENT_API_TOKEN机密 必填 envAtlassian API token from id.atlassian.com/manage-profile/security/api-tokens (Basic auth password).JIRA_SERVICE_MANAGEMENT_CLOUD_IDenvAssets only: your site's cloudId. Leave blank if you do not use Assets; 'cmdb discover' prints it.JIRA_SERVICE_MANAGEMENT_EMAIL必填 envAtlassian account email (Basic auth username).JIRA_SERVICE_MANAGEMENT_SITE必填 env您的 Atlassian 站点子域名:例如 acme 对应 acme.atlassian.net查看英文原文
Your Atlassian site subdomain: acme for acme.atlassian.net.JIRA_SERVICE_MANAGEMENT_WORKSPACE_IDenvAssets only: your Assets workspaceId. Leave blank if you do not use Assets; 'cmdb discover' prints it.JIRA_SERVICE_MANAGEMENT_BASE_URLenv可选。替换根据您的站点构建的 request-API 根地址。建议留空,改为设置站点,因为此覆盖也会重定向 Assets 调用。查看英文原文
Optional. Replaces the request-API root built from your site. Leave blank: set the site instead, because this override also redirects Assets calls.JIRA_SERVICE_MANAGEMENT_MCP_READ_ONLYenv可选。设置为 1 可移除 MCP 服务器的写入工具,并拒绝任何非 GET 的 execute 调用。查看英文原文
Optional. Set to 1 to drop the MCP server's write tools and refuse any non-GET execute call.JIRA_SERVICE_MANAGEMENT_MCP_HTTP_TOKEN机密 必填 envRequired only when running the MCP server with --transport http (a remote/hosted deployment); callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transpo…JIRA_SERVICE_MANAGEMENT_USER_AGENTenv可选。覆盖 CLI 发送到 Atlassian 的 User-Agent。留空则使用内置值。查看英文原文
Optional. Overrides the User-Agent the CLI sends to Atlassian. Leave blank to use the built-in one.PRINTING_PRESS_CLIENT_PROFILE机密 必填 envJIRA_SERVICE_MANAGEMENT_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses: reads go to the API, the response cache is off, and sync refuses to run. Leave blank to keep the local store.JIRA_SERVICE_MANAGEMENT_MCP_UPLOAD_ROOTenvOptional. Leave blank: MCP file uploads then take the file as base64 content and the server never opens a local path. Set it to a folder only to let MCP uploads read files from inside that folder.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Servosity 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于今天
- ! 注意
有许可证
GitHub 无法识别许可证类型;请打开文件自行查看
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/servosity-jira-service-management-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6136 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6136 个服务器的 88% 更新
- 基础检查结果等于或优于此分类中其他 6136 个服务器的 45%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
Jira Service Management MCP 安全吗?
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:JIRA_SERVICE_MANAGEMENT_API_TOKEN, JIRA_SERVICE_MANAGEMENT_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于今天,最新版本(0.1.9)于5天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 Jira Service Management MCP | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 2/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | NOASSERTION | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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):
| Your AI agent | How to install the Jira Service Management skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register jira-service-management-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add jira-service-management-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add jira-service-management-mcp to mcp.json under the servers key, then pick Agent mode. |
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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/jira-service-management/install.ps1 | iex. Then authenticate per the README and runjira-service-management-cli --helpto 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 theopenclaw: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
| Question your MSP keeps asking | Command |
|---|---|
| Which tickets breach SLA in the next two hours, across every queue? | jira-service-management-cli breaches --within 2h |
| What happened on this ticket, internal notes included, before I reply? | jira-service-management-cli request timeline SD-123 |
| Add a note for the other techs that the customer will never see | jira-service-management-cli request note SD-123 "Escalated to network team" |
| How are Acme Corp's open tickets doing before my client call? | jira-service-management-cli client "Acme Corp" |
| What was our SLA breach rate by request type over the last 30 days? | jira-service-management-cli sla-report --since 30d --group-by requesttype |
| Which client staff are in no organization, or in two? | jira-service-management-cli roster 3 |
| Which tickets have touched this server? | jira-service-management-cli cmdb tickets srv-01 |
| Which laptops are in our RMM export but missing from Assets? | jira-service-management-cli cmdb reconcile --type Laptop --file rmm.csv --key Name --compare Serial,OS |
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