/ 目錄 / 演練場 / jira-skill
← 全部伺服器 ↗ GitHub
● 社群 netresearch ⚡ 即開即用

jira-skill

作者 netresearch · netresearch/jira-skill

Two skills (jira-communication + jira-syntax) wrapping Jira Server/DC and Cloud APIs via shell — issues, JQL, sprints, worklogs, attachments, no Docker needed.

A Claude Code skill pack for Jira with no container dependency. jira-communication covers API operations (get / update / search by JQL / transition / comment / link / worklog / attach / board + sprint management). jira-syntax helps with Jira wiki markup. Works with Server/DC and Cloud via env-based credentials, includes an interactive jira-setup.py for config.

▶ 觀看演示 📦 安裝 💡 使用場景

為什麼要用

核心特性

即時演示

實際使用效果

jira-skill.replay ▶ 就緒
0/0

安裝

選擇你的客戶端

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "jira-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/netresearch/jira-skill",
        "~/.claude/skills/jira-skill"
      ],
      "_inferred": true
    }
  }
}

開啟 Claude Desktop → Settings → Developer → Edit Config。儲存後重啟應用。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "jira-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/netresearch/jira-skill",
        "~/.claude/skills/jira-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor 使用與 Claude Desktop 相同的 mcpServers 格式。專案級設定優先於全域。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "jira-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/netresearch/jira-skill",
        "~/.claude/skills/jira-skill"
      ],
      "_inferred": true
    }
  }
}

點擊 Cline 側欄中的 MCP Servers 圖示，然後選 "Edit Configuration"。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "jira-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/netresearch/jira-skill",
        "~/.claude/skills/jira-skill"
      ],
      "_inferred": true
    }
  }
}

格式與 Claude Desktop 相同。重啟 Windsurf 生效。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "jira-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/netresearch/jira-skill",
        "~/.claude/skills/jira-skill"
      ]
    }
  ]
}

Continue 使用伺服器物件陣列，而非映射。

~/.config/zed/settings.json
{
  "context_servers": {
    "jira-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/netresearch/jira-skill",
          "~/.claude/skills/jira-skill"
        ]
      }
    }
  }
}

加入 context_servers。Zed 儲存後熱重載。

claude mcp add jira-skill -- git clone https://github.com/netresearch/jira-skill ~/.claude/skills/jira-skill

一行命令搞定。用 claude mcp list 驗證，claude mcp remove 移除。

使用場景

實戰用法： jira-skill

Triage a sprint backlog and unstick blocked issues

👤 Scrum masters, tech leads ⏱ ~20 min beginner

何時使用： Mid-sprint when velocity is dropping and you suspect blockers.

前置條件
  • Jira credentials configured — Run jira-setup.py and provide URL + email + API token (Cloud) or PAT (Server/DC)
  • Skill installed — git clone https://github.com/netresearch/jira-skill ~/.claude/skills/jira-skill
步驟
  1. List sprint issues by status
    Use jira-skill. List issues in sprint 'Sprint 42' grouped by status. Flag anything not updated in 3 days.✓ 已複製
    → Grouped table with staleness markers
  2. Drill into blockers
    For the blocked issues, pull the last comment and linked issues — who's waiting on what?✓ 已複製
    → Dependency summary
  3. Nudge owners
    Draft a comment on each blocked issue pinging the responsible party.✓ 已複製
    → Per-issue drafts

結果： A clear list of unblock actions to drive in standup.

注意事項
  • Over-pinging — comments cost attention — Let Claude draft; post manually only the ones that matter
搭配使用： github

Generate release notes from closed issues

👤 Release managers ⏱ ~15 min beginner

何時使用： Cutting a release and need user-facing notes from the issue list.

步驟
  1. JQL for the release
    JQL: fixVersion = 1.42 AND status = Done. Pull summaries and types.✓ 已複製
    → Ordered issue list
  2. Draft notes
    Group by type (Feature / Bug / Improvement) and write user-facing release notes — no internal jargon.✓ 已複製
    → Markdown notes ready to publish

結果： Release notes in minutes instead of hours.

搭配使用： github

Bulk-transition issues through a workflow

👤 Project admins ⏱ ~10 min intermediate

何時使用： Moving a batch of issues between statuses (e.g. deploy-complete).

步驟
  1. Dry-run first
    Find all 'In Staging' issues with fixVersion = 1.42. Don't transition yet — just list.✓ 已複製
    → List to confirm
  2. Transition
    Transition those to 'Done' with a comment 'Deployed to production in 1.42'.✓ 已複製
    → Per-issue transition result

結果： Clean workflow state, nothing left in 'In Staging'.

注意事項
  • Missing required fields on transition — Skill surfaces the required field; supply it in the prompt

Summarize a team's worklog for the month

👤 Engineering managers, PMs tracking capacity ⏱ ~20 min intermediate

何時使用： Month-end capacity review.

步驟
  1. Query worklogs
    Pull all worklogs for team members in project ACME for last month.✓ 已複製
    → Per-person, per-issue hour totals
  2. Summarize
    Roll up to epic and share of total.✓ 已複製
    → Top-level breakdown

結果： Capacity picture grounded in actual logged work.

注意事項
  • Worklogs aren't filled in — bad data — Flag people with 0 logs; don't draw conclusions from missing data

組合

與其他 MCP 搭配，撬動十倍槓桿

jira-skill + github

Link PRs to Jira issues or create Jira issues from GitHub bugs

For each GitHub issue labeled 'bug' opened this week, create a Jira ticket in project ACME.✓ 已複製

工具

此 MCP 暴露的能力

工具輸入參數何時呼叫成本
get_issue issue key Anytime 1 API call
search_jql JQL string Discovery 1 API call
create_issue project, type, summary, description Filing new issue 1 API call (write)
transition_issue key, transition id/name Workflow moves 1 API call (write)
add_comment key, body (jira-syntax ok) Nudges + notes 1 API call (write)
link_issues key, inward, link type Dependencies 1 API call
add_worklog key, time, comment Time tracking 1 API call
sprint_manage board, sprint, action Scrum ops 1 API call

成本與限制

運行它的成本

API 配額
Jira Cloud: 10 req/sec per user typical; Server/DC is instance-configured
每次呼叫 Token 數
Low — mostly API responses
費用
Free skill; Jira license separate
提示
Use JQL server-side filters rather than pulling all and filtering client-side

安全

權限、密鑰、影響範圍

最小權限： Read project; write only where needed (transition/comment)
憑證儲存： JIRA_URL + JIRA_USER + JIRA_TOKEN in env; don't check into git
資料出站： Only to your Jira host
切勿授予： Admin on the instance

故障排查

常見錯誤與修復

401 Unauthorized

Token missing or revoked; re-run jira-setup.py

驗證： curl -u $JIRA_USER:$JIRA_TOKEN $JIRA_URL/rest/api/2/myself
400 on transition

Transition requires a field you didn't provide — inspect transitions with get_transitions

Search returns 0 but issues exist

Your JQL or project permissions; verify the user can see the project

替代方案

jira-skill 對比其他方案

替代方案何時用它替代權衡
Atlassian's official MCPYou prefer first-party integrationLess control over shell access

更多

資源

📖 閱讀 GitHub 上的官方 README

🐙 查看未解決的 issue

🔍 瀏覽全部 400+ MCP 伺服器和 Skills