Skip to main content
Glama
SunWooBang

Jira MCP Server

by SunWooBang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Jira MCP Server

Jira와 Claude를 연결하는 Model Context Protocol (MCP) 서버입니다.

기능

  • 이슈 검색: JQL을 사용하여 Jira 이슈 검색

  • 이슈 조회: 특정 이슈의 상세 정보 확인

  • 이슈 생성: 새로운 Jira 이슈 생성

  • 이슈 업데이트: 기존 이슈 수정 (제목, 설명, 상태, 담당자)

  • 댓글 추가: 이슈에 댓글 추가

  • 프로젝트 정보: 프로젝트 정보 조회

Related MCP server: Atlassian Jira MCP Server

설치 및 설정

1. 환경 변수 설정

.env 파일을 생성하고 다음 정보를 입력하세요:

JIRA_URL=https://your-domain.atlassian.net
JIRA_USERNAME=your-email@domain.com
JIRA_API_TOKEN=your-api-token
DEFAULT_PROJECT_KEY=PROJ

참고: 설정 파일들은 config/ 폴더에 자동으로 생성됩니다.

2. Jira API 토큰 생성

  1. Jira에 로그인

  2. 계정 설정 > 보안 > API 토큰 생성

  3. 생성된 토큰을 .env 파일의 JIRA_API_TOKEN에 입력

3. 의존성 설치

npm install

4. 자동 설정 (권장)

대화형 설정 도구를 사용하여 쉽게 설정할 수 있습니다:

npm run setup

이 명령어는:

  • Jira 연결 정보를 입력받습니다

  • config/.env 파일을 자동으로 생성합니다

  • config/claude_desktop_config.json 파일을 자동으로 생성합니다

  • Claude Desktop 설정 방법을 안내합니다

5. 수동 설정 (선택사항)

자동 설정 대신 수동으로 설정하려면 config/.env.example 파일을 복사하여 config/.env로 이름을 바꾸고 값을 수정하세요.

6. 서버 실행

npm start

Claude Desktop 설정

Claude Desktop에서 이 MCP 서버를 사용하려면 설정 파일을 수정해야 합니다.

Windows

%APPDATA%\\Claude\\claude_desktop_config.json 파일을 편집:

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["C:\\path\\to\\jira-mcp-server\\index.js"],
      "env": {
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your-email@domain.com",
        "JIRA_API_TOKEN": "your-api-token",
        "DEFAULT_PROJECT_KEY": "PROJ"
      }
    }
  }
}

macOS

~/Library/Application Support/Claude/claude_desktop_config.json 파일을 편집:

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["/path/to/jira-mcp-server/index.js"],
      "env": {
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your-email@domain.com", 
        "JIRA_API_TOKEN": "your-api-token",
        "DEFAULT_PROJECT_KEY": "PROJ"
      }
    }
  }
}

사용 예시

Claude에서 다음과 같은 명령을 사용할 수 있습니다:

이슈 검색

"프로젝트 PROJ에서 상태가 Open인 이슈들을 찾아줘"

이슈 생성

"PROJ 프로젝트에 '새로운 기능 개발' 제목으로 Task 이슈를 생성해줘"

이슈 업데이트

"PROJ-123 이슈의 상태를 'In Progress'로 변경해줘"

댓글 추가

"PROJ-123 이슈에 '작업을 시작했습니다' 댓글을 추가해줘"

지원하는 도구

  1. search_issues: JQL로 이슈 검색

  2. get_issue: 특정 이슈 조회

  3. create_issue: 새 이슈 생성

  4. update_issue: 이슈 업데이트

  5. add_comment: 댓글 추가

  6. get_project_info: 프로젝트 정보 조회

문제 해결

인증 오류

  • Jira URL이 올바른지 확인

  • API 토큰이 유효한지 확인

  • 사용자 이메일이 정확한지 확인

권한 오류

  • 사용자가 해당 프로젝트에 접근 권한이 있는지 확인

  • 이슈 생성/수정 권한이 있는지 확인

라이선스

MIT License

Available Tools

1 tool
example_toolC

An example tool that processes messages

ParametersJSON Schema
NameRequiredDescriptionDefault
messageNoMessage to process

TDQS

C2.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided and the description lacks any behavioral traits such as side effects, permissions, or read-only/mutating nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While short, the description is under-specified and does not earn its place with substantive information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple schema and no output schema or annotations, the description fails to provide complete context, e.g., what the output is or expected behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the description adds no value beyond the schema definition for the only parameter 'message'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'processes messages' is vague and does not specify what kind of processing or distinguish from sibling tools like api-client, data-processor, and file-handler.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives; no exclusions or prerequisites mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedexample_tool
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'example_tool' stands alone with a distinct purpose, so agents cannot misselect between multiple options.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'example_tool' follows a clear noun-based pattern, and with no other tools to compare, there are no inconsistencies in naming conventions.

Tool Count2/5

A single tool is too few for a server named 'Jira MCP Server', which implies a domain related to Jira project management. This minimal set fails to cover the expected scope, such as CRUD operations for issues, projects, or workflows, making it inadequate for typical agent tasks.

Completeness1/5

The tool set is severely incomplete for the Jira domain. With only an 'example_tool' that processes messages, it lacks any operations for managing issues, projects, users, or other Jira entities, leaving obvious gaps that will cause agent failures in real-world scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • JIRA MCP Server

    rajsodhi-2
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables Claude AI to interact with JIRA for project management and issue tracking, supporting JQL queries, comprehensive issue details retrieval with subtasks and linked issues, and release planning analysis.
    MIT

  • Atlassian Jira MCP Server

    aashari
    A
    license
    Not graded
    quality
    D
    maintenance
    Connects AI assistants like Claude to Jira projects, enabling natural language queries and operations for issue management, project tracking, comments, and workflows through the Jira REST API.
    11,532 npm
    77
    ISC

  • Jira MCP Server

    rui-branco
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.
    135 npm
    2
    MIT

  • jira-mcp-server

    fkesheh
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI assistants like Claude to interact with Jira for project management tasks, including issue creation, updates, workflow transitions, and bulk operations.
    19 npm
    4
    MIT

Appeared in Searches