Skip to main content
Glama
Jira MCP Server

Jira MCP Server

by KS-GEN-AI

Jira-Kommunikationsserver MCP-Server

Sprechen Sie mit Jira

Dies ist ein TypeScript-basierter MCP-Server, der Tools für die Interaktion mit Jira bereitstellt. Er veranschaulicht die wichtigsten MCP-Konzepte anhand von:

  • Tools zum Ausführen von JQL-Abfragen

  • Tools zum Erstellen, Bearbeiten und Löschen von Jira-Tickets

  • Tools zum Auflisten von Jira-Projekten und -Status

Merkmale

Related MCP server: JIRA MCP Server

Jira-Tools

execute_jql

  • Zweck : Führen Sie eine JQL-Abfrage aus.

  • Parameter : jql , number_of_results (Standard: 1).

get_only_ticket_name_and_description

  • Zweck : Ticketname und -beschreibung abrufen.

  • Parameter : jql , number_of_results (Standard: 1).

create_ticket

  • Zweck : Erstellen Sie ein Jira-Ticket.

  • Parameter : project.key , summary , description , issuetype.name , parent (optional).

list_projects

  • Zweck : Jira-Projekte auflisten.

  • Parameter : number_of_results (Standard: 1).

delete_ticket

  • Zweck : Ein Ticket löschen.

  • Parameter : issueIdOrKey .

edit_ticket

  • Zweck : Ein Ticket ändern.

  • Parameter : issueIdOrKey , summary (optional), description (optional), labels (optional), parent (optional).

get_all_statuses

  • Zweck : Alle Status abrufen.

  • Parameter : number_of_results (Standard: 1).

assign_ticket

  • Zweck : Einem Benutzer ein Ticket zuweisen.

  • Parameter : accountId , issueIdOrKey .

query_assignable

  • Zweck : Zuweisbare Benutzer in einem Projekt finden.

  • Parameter : project_key .

add_attachment

  • Zweck : Einem Ticket einen Anhang hinzufügen.

  • Parameter : issueIdOrKey , imageUrl .

Entwicklung

Installieren Sie Abhängigkeiten:

npm install

Erstellen Sie den Server:

npm run build

Für die Entwicklung mit automatischem Rebuild:

npm run watch

Installation

Zur Verwendung mit Claude Desktop fügen Sie die Serverkonfiguration hinzu:

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

Debuggen

Da MCP-Server über stdio kommunizieren, kann das Debuggen eine Herausforderung darstellen. Wir empfehlen die Verwendung des MCP Inspector , der als Paketskript verfügbar ist:

npm run inspector

Der Inspector stellt eine URL für den Zugriff auf Debugging-Tools in Ihrem Browser bereit.

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