Skip to main content
Glama
Jira MCP Server

Jira MCP Server

by KS-GEN-AI

Сервер связи Jira MCP Server

Поговорите с Джирой

Это MCP-сервер на основе TypeScript, который предоставляет инструменты для взаимодействия с Jira. Он демонстрирует основные концепции MCP, предоставляя:

  • Инструменты для выполнения JQL-запросов

  • Инструменты для создания, редактирования и удаления тикетов Jira

  • Инструменты для составления списка проектов и статусов Jira

Функции

Related MCP server: JIRA MCP Server

Инструменты Jira

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 .

Разработка

Установить зависимости:

npm install

Сборка сервера:

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,677 npm
      2
      TypeScript
      MIT