Skip to main content
Glama
Jira MCP Server

Jira MCP Server

by KS-GEN-AI

Servidor de comunicaciones Jira Servidor MCP

Hablar con Jira

Este es un servidor MCP basado en TypeScript que proporciona herramientas para interactuar con Jira. Demuestra los conceptos básicos de MCP al proporcionar:

  • Herramientas para ejecutar consultas JQL

  • Herramientas para crear, editar y eliminar tickets de Jira

  • Herramientas para listar proyectos y estados de Jira

Características

Related MCP server: JIRA MCP Server

Herramientas de Jira

execute_jql

  • Propósito : ejecutar una consulta JQL.

  • Parámetros : jql , number_of_results (predeterminado: 1).

get_only_ticket_name_and_description

  • Propósito : Obtener el nombre y la descripción del ticket.

  • Parámetros : jql , number_of_results (predeterminado: 1).

create_ticket

  • Propósito : crear un ticket de Jira.

  • Parámetros : project.key , summary , description , issuetype.name , parent (opcional).

list_projects

  • Propósito : enumerar proyectos de Jira.

  • Parámetros : number_of_results (predeterminado: 1).

delete_ticket

  • Propósito : Eliminar un ticket.

  • Parámetros : issueIdOrKey .

edit_ticket

  • Propósito : Modificar un ticket.

  • Parámetros : issueIdOrKey , summary (opcional), description (opcional), labels (opcional), parent (opcional).

get_all_statuses

  • Propósito : recuperar todos los estados.

  • Parámetros : number_of_results (predeterminado: 1).

assign_ticket

  • Propósito : Asignar un ticket a un usuario.

  • Parámetros : accountId , issueIdOrKey .

query_assignable

  • Propósito : encontrar usuarios asignables en un proyecto.

  • Parámetros : project_key .

add_attachment

  • Propósito : Agregar un archivo adjunto a un ticket.

  • Parámetros : issueIdOrKey , imageUrl .

Desarrollo

Instalar dependencias:

npm install

Construir el servidor:

npm run build

Para desarrollo con reconstrucción automática:

npm run watch

Instalación

Para utilizar con Claude Desktop, agregue la configuración del servidor:

En MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json En 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"
      }
    }
  }
}

Depuración

Dado que los servidores MCP se comunican a través de stdio, la depuración puede ser complicada. Recomendamos usar el Inspector MCP , disponible como script de paquete:

npm run inspector

El Inspector proporcionará una URL para acceder a las herramientas de depuración en su navegador.

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

    ActivityNo data
    ResponsivenessOutdated 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