Skip to main content
Glama
enesjakozh
CamdenClark

jira-mcp

by CamdenClark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Servidor JIRA MCP

insignia de herrería

Un servidor MCP que permite que los Modelos de Lenguaje Grandes (LLM) interactúen con JIRA mediante herramientas y contexto estandarizados. Este servidor ofrece funciones para buscar incidencias mediante JQL y recuperar información detallada sobre ellas.

Características

  • Búsqueda JQL : Ejecute consultas JQL complejas con soporte de paginación

  • Detalles del problema : recupera información detallada sobre problemas específicos de JIRA

Related MCP server: JIRA MCP Server

Prerrequisitos

  • npm instalado

  • Una instancia de JIRA con acceso a API

  • Token de API de JIRA o token de acceso personal

  • Correo electrónico del usuario de JIRA asociado con el token de API

Obtención de credenciales de API de JIRA

  1. Inicie sesión en su cuenta de Atlassian en https://id.atlassian.com

  2. Vaya a Configuración de seguridad

  3. En Tokens de API, seleccione "Crear token de API".

  4. Dale a tu token un nombre significativo (por ejemplo, "Servidor MCP")

  5. Copia el token generado: ¡no podrás volver a verlo!

  6. Utilice este token como su JIRA_API_KEY

  7. Utilice la dirección de correo electrónico asociada a su cuenta Atlassian como JIRA_USER_EMAIL

Uso

Integración con Claude Desktop

  1. Agregue la configuración del servidor al archivo de configuración de Claude Desktop:

macOS : ~/Library/Application Support/Claude/claude_desktop_config.json Windows : %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "jira-mcp"],
      "env": {
        "JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
        "JIRA_USER_EMAIL": "your-email@company.com",
        "JIRA_API_KEY": "your-api-token"
      }
    }
  }
}

  1. Reinicie Claude Desktop para cargar la nueva configuración.

Herramientas disponibles

1. Búsqueda JQL ( jql_search )

Ejecuta una consulta de búsqueda JQL con parámetros personalizables.

Parámetros :

  • jql (obligatorio): cadena de consulta JQL

  • nextPageToken : Token para paginación

  • maxResults : Número máximo de resultados a devolver

  • fields : Matriz de nombres de campos a incluir

  • expand : Información adicional para incluir

Ejemplo :

{
  "jql": "project = 'MyProject' AND status = 'In Progress'",
  "maxResults": 10,
  "fields": ["summary", "status", "assignee"]
}

2. Obtener problema ( get_issue )

Recupera información detallada sobre un problema específico.

Parámetros :

  • issueIdOrKey (obligatorio): ID del problema o clave

  • fields : Matriz de nombres de campos a incluir

  • expand : Información adicional para incluir

  • properties : Matriz de propiedades a incluir

  • failFast : si se debe fallar rápidamente ante errores

Ejemplo :

{
  "issueIdOrKey": "PROJ-123",
  "fields": ["summary", "description", "status"],
  "expand": "renderedFields,names"
}

Desarrollo

Configuración

Configure las variables de entorno antes de ejecutar el servidor. Cree un archivo .env en el directorio raíz:

JIRA_INSTANCE_URL=https://your-instance.atlassian.net
JIRA_USER_EMAIL=your-email@company.com
JIRA_API_KEY=your-api-token

Reemplace los valores con:

  • La URL real de su instancia de JIRA

  • La dirección de correo electrónico asociada a su cuenta de JIRA

  • Su token de API de JIRA (se puede generar en la configuración de la cuenta de Atlassian)

Instalación

Instalación mediante herrería

Para instalar JIRA para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install jira-mcp --client claude

Instalación manual

  1. Clonar este repositorio:

git clone <repository-url>
cd jira-mcp

  1. Instalar dependencias:

npm install

Ejecutando con MCP Inspector

Para pruebas y desarrollo, puede utilizar el Inspector MCP:

npm run inspect

Agregar nuevas herramientas

Para agregar nuevas herramientas, modifique el controlador ListToolsRequestSchema en index.js :

server.setRequestHandler(ListToolsRequestSchema, async () => {
  return {
    tools: [
      // Existing tools...
      {
        name: "your_new_tool",
        description: "Description of your new tool",
        inputSchema: {
          // Define input schema...
        }
      }
    ]
  };
});

Luego implemente la herramienta en el controlador CallToolRequestSchema .

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Contribuyendo

¡Agradecemos sus contribuciones! No dude en enviar un PR.

Available Tools

2 tools
get_issueC

Retrieve details about an issue by its ID or key.

ParametersJSON Schema
NameRequiredDescriptionDefault
issueIdOrKeyYesID or key of the issue
fieldsNoFields to include in the response
expandNoAdditional information to include in the response
propertiesNoProperties to include in the response
failFastNoFail quickly on errors

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details, implying a read-only operation, but doesn't mention error handling (e.g., what happens if the ID/key is invalid), rate limits, authentication needs, or response format. This leaves significant gaps for an agent to understand how to use it effectively.

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

Conciseness5/5

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

The description is a single, clear sentence that efficiently conveys the core purpose without any unnecessary words. It's front-loaded and easy to parse, making it highly concise and well-structured for quick understanding.

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 complexity of 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what details are retrieved, how to handle optional parameters like 'fields' or 'expand', or what the response looks like. For a tool with multiple parameters and no structured output information, more context is needed to guide proper usage.

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?

The input schema has 100% description coverage, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond implying retrieval by 'ID or key', which aligns with the 'issueIdOrKey' parameter but doesn't elaborate on usage. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Retrieve') and resource ('details about an issue'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from the sibling tool 'jql_search', which likely serves a different purpose (searching vs. retrieving by ID/key).

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?

The description provides no guidance on when to use this tool versus alternatives like 'jql_search'. It mentions retrieving by 'ID or key', which implies a specific use case, but doesn't clarify when to choose this over a search tool or address any prerequisites or exclusions.

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. 2 tool updates
    • First observedget_issue
    • First observedjql_search
Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

B3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_issue retrieves a single issue by ID/key, while jql_search performs broader queries using JQL. There is no overlap or ambiguity between them, as they serve different use cases (specific lookup vs. flexible search).

Naming Consistency5/5

Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: get_issue and jql_search. The naming is predictable and readable, with no deviations or mixed conventions.

Tool Count2/5

With only 2 tools, this server feels severely under-scoped for a Jira integration. A typical Jira MCP would need more operations like create_issue, update_issue, or list_projects to cover basic workflows. The current set is too thin for meaningful agent interaction.

Completeness2/5

The tool surface is significantly incomplete for Jira's domain. While get_issue and jql_search provide read/search capabilities, there are major gaps in CRUD operations (no create, update, or delete) and missing lifecycle management (e.g., transitions, comments). This will cause agent failures in common scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches