Skip to main content
Glama
Jira MCP Server

Jira MCP Server

by KS-GEN-AI

Jira 커뮤니케이션 서버 MCP 서버

지라와 대화하세요

Jira와 상호 작용하는 도구를 제공하는 TypeScript 기반 MCP 서버입니다. 다음을 통해 핵심 MCP 개념을 보여줍니다.

  • JQL 쿼리 실행을 위한 도구

  • Jira 티켓 생성, 편집 및 삭제 도구

  • Jira 프로젝트 및 상태를 나열하기 위한 도구

특징

Related MCP server: JIRA MCP Server

지라 도구

execute_jql

  • 목적 : JQL 쿼리를 실행합니다.

  • 매개변수 : jql , number_of_results (기본값: 1).

get_only_ticket_name_and_description

  • 목적 : 티켓 이름과 설명을 가져옵니다.

  • 매개변수 : jql , number_of_results (기본값: 1).

create_ticket

  • 목적 : Jira 티켓을 만듭니다.

  • 매개변수 : project.key , summary , description , issuetype.name , parent (선택 사항).

list_projects

  • 목적 : Jira 프로젝트 나열.

  • 매개변수 : number_of_results (기본값: 1).

delete_ticket

  • 목적 : 티켓을 삭제합니다.

  • 매개변수 : issueIdOrKey .

edit_ticket

  • 목적 : 티켓을 수정합니다.

  • 매개변수 : issueIdOrKey , summary (선택 사항), description (선택 사항), labels (선택 사항), parent (선택 사항).

get_all_statuses

  • 목적 : 모든 상태를 검색합니다.

  • 매개변수 : number_of_results (기본값: 1).

assign_ticket

  • 목적 : 사용자에게 티켓을 할당합니다.

  • 매개변수 : accountId , issueIdOrKey .

query_assignable

  • 목적 : 프로젝트에서 할당 가능한 사용자를 찾습니다.

  • 매개변수 : project_key .

add_attachment

  • 목적 : 티켓에 첨부 파일을 추가합니다.

  • 매개변수 : issueIdOrKey , imageUrl .

개발

종속성 설치:

지엑스피1

서버를 빌드하세요:

npm run build

자동 재빌드를 사용한 개발의 경우:

npm run watch

설치

Claude Desktop과 함께 사용하려면 서버 구성을 추가하세요.

MacOS의 경우: ~/Library/Application Support/Claude/claude_desktop_config.json Windows의 경우: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "Jira communication server": {
      "command": "node",
      "args": [
        "/PATH_TO_THE_PROJECT/build/index.js"
      ],
      "env": {
        "JIRA_URL": "https://XXXXXXXX.atlassian.net",
        "JIRA_API_MAIL": "Your email",
        "JIRA_API_KEY": "KEY_FROM : https://id.atlassian.com/manage-profile/security/api-tokens"
      }
    }
  }
}

디버깅

MCP 서버는 stdio를 통해 통신하므로 디버깅이 어려울 수 있습니다. 패키지 스크립트로 제공되는 MCP Inspector를 사용하는 것이 좋습니다.

npm run inspector

검사기는 브라우저에서 디버깅 도구에 액세스할 수 있는 URL을 제공합니다.

Available Tools

11 tools
add_attachment_from_confluenceC

Add an attachment to a ticket on Jira from a Confluence page by its name on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query.

Inputs: issueIdOrKey (required), pageId (required), attachmentName (required).

add_attachment_from_public_urlA

Add an attachment from a public url to a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/attachments. Do not use markdown in your query.

Inputs: issueIdOrKey (required), imageUrl (required).

assign_ticketB

Assign a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}/assignee. Do not use markdown in your query.

Inputs: accountId (required), issueIdOrKey (required).

create_ticketC

Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field.

Inputs: project (required), summary (required), description (required), issuetype (required), +1 more.

delete_ticketC

Delete a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in your query.

Inputs: issueIdOrKey (required).

edit_ticketC

Edit a ticket on Jira on the api /rest/api/3/issue/{issueIdOrKey}. Do not use markdown in any field.

Inputs: issueIdOrKey (required), summary, description, labels, +1 more.

execute_jqlC

Execute a JQL query on Jira on the api /rest/api/3/search/jql. Do not use markdown in your query.

Inputs: jql (required), number_of_results.

get_all_statusesC

Get all the status on Jira on the api /rest/api/3/status. Do not use markdown in your query.

Inputs: number_of_results.

get_only_ticket_name_and_descriptionC

Get the name and description of the requested tickets on the api /rest/api/3/search/jql. Do not use markdown in your query.

Inputs: jql (required), number_of_results.

list_projectsC

List all the projects on Jira on the api /rest/api/3/project. Do not use markdown in your query.

Inputs: number_of_results.

query_assignableC

Query assignables to a ticket on Jira on the api /rest/api/3/user/assignable/search?project={project-name}. Do not use markdown in your query.

Inputs: project_key (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific Jira operations like create, edit, delete, assign, query, and list. However, 'execute_jql' and 'get_only_ticket_name_and_description' both query tickets via JQL, creating some overlap that could cause confusion, though their descriptions clarify different output focuses.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case throughout, such as 'create_ticket', 'assign_ticket', and 'list_projects'. This predictability makes it easy for agents to understand and navigate the tool set without naming conflicts.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a Jira server, covering core operations like ticket management, attachments, queries, and project listing. Each tool appears to serve a specific function without unnecessary bloat, fitting typical server tool ranges.

    Completeness4/5

    The tool set provides good coverage for Jira workflows, including CRUD operations for tickets, assignment, attachments, and project/status queries. Minor gaps exist, such as missing tools for comments, transitions, or watchers, but core functionalities are present and agents can likely work around these omissions.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Jira, allowing for project management tasks such as listing projects, searching issues, creating tickets, and managing sprints through natural language queries.
      7
      1,667 npm
      2
      TypeScript
      MIT