/ ディレクトリ / プレイグラウンド / 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

インストール

作者のリポジトリ · Claude Skills の公式ドキュメント

ユースケース

実用的な使い方： 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.

フロー
  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と組み合わせて10倍の力を

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
呼び出しあたりのトークン
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を見る