jira-skill MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Works with Jira Server, DC, and Cloud
No Docker — pure shell + Python
Full issue lifecycle: create, transition, comment, link, worklog, attach
JQL search helpers
Sprint + board management
Interactive jira-setup.py credential configurator
jira-syntax helper for wiki markup

라이브 데모

실제 사용 모습

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

흐름

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
Drill into blockers

For the blocked issues, pull the last comment and linked issues — who's waiting on what?✓ 복사됨

→ Dependency summary
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.

흐름

JQL for the release

JQL: fixVersion = 1.42 AND status = Done. Pull summaries and types.✓ 복사됨

→ Ordered issue list
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).

흐름

Dry-run first

Find all 'In Staging' issues with fixVersion = 1.42. Don't transition yet — just list.✓ 복사됨

→ List to confirm
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.

흐름

Query worklogs

Pull all worklogs for team members in project ACME for last month.✓ 복사됨

→ Per-person, per-issue hour totals
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

API tokens for Cloud should be user-scoped; for Server/DC use personal access tokens, not passwords.

문제 해결

자주 발생하는 오류와 해결

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 MCP	You prefer first-party integration	Less control over shell access

jira-skill