JIRA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_TOKEN | Yes | Personal Access Token for JIRA authentication | |
| MCP_UI_HOST | No | Host for the local MCP UI (default: 127.0.0.1) | 127.0.0.1 |
| MCP_UI_PORT | No | Port for the local MCP UI (default: 8787) | 8787 |
| NL_AI_MODEL | No | AI model for NL mode (default: gpt-4o-mini) | gpt-4o-mini |
| JIRA_BASE_URL | Yes | Base URL of the JIRA instance (e.g., https://jira.springlab.enel.com) | |
| NL_AI_API_KEY | No | API key for natural language AI mode (required if using NL) | |
| NL_AI_BASE_URL | No | Base URL for AI API (default: https://api.openai.com/v1) | https://api.openai.com/v1 |
| JIRA_API_VERSION | No | JIRA API version (default: 2) | 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_searchA | Cerca issue JIRA tramite query JQL. Restituisce id, key, sommario, status, assegnatario e priorità. |
| jira_get_issueA | Recupera i dettagli completi di una issue JIRA tramite la sua chiave (es. ABC-123). |
| jira_create_issueC | Crea una nuova issue JIRA. |
| jira_update_issueB | Aggiorna i campi di una issue JIRA esistente (summary, description, priority, assignee, labels, ecc.). |
| jira_add_commentB | Aggiunge un commento a una issue JIRA. |
| jira_get_transitionsA | Restituisce le transizioni di stato disponibili per una issue (es. per passarla a 'In Progress' o 'Done'). |
| jira_transition_issueA | Cambia lo stato di una issue JIRA tramite una transizione (usa jira_get_transitions per trovare l'id). |
| jira_get_projectsC | Elenca i progetti JIRA accessibili con chiave, nome e tipo. |
| jira_get_project_rolesB | Elenca i ruoli definiti in un progetto JIRA con il relativo ID. |
| jira_get_project_role_membersB | Restituisce i membri (actors) assegnati a un ruolo specifico di un progetto JIRA. |
| jira_assign_issueA | Assegna una issue JIRA a un utente specifico. |
| jira_get_issue_commentsC | Recupera i commenti di una issue JIRA. |
| xray_get_test_stepsA | Recupera gli step di un Test Xray tramite la chiave issue (es. PROJ-123). Restituisce id, step, dati, risultato atteso e allegati per ogni step. |
| confluence_searchC | Cerca contenuti Confluence tramite query CQL (Confluence Query Language). |
| confluence_get_pageB | Recupera il contenuto completo di una pagina Confluence tramite il suo ID. |
| confluence_get_page_by_titleB | Cerca e recupera una pagina Confluence tramite spazio e titolo. |
| confluence_create_pageB | Crea una nuova pagina Confluence in uno spazio specificato. |
| confluence_update_pageC | Aggiorna il contenuto di una pagina Confluence esistente. |
| confluence_get_spacesB | Elenca gli spazi Confluence accessibili. |
| confluence_get_space_pagesB | Elenca le pagine di primo livello di uno spazio Confluence. |
| confluence_add_commentB | Aggiunge un commento a una pagina Confluence. |
| confluence_get_calendar_eventsA | Recupera gli eventi da un Team Calendar di Confluence tramite il suo ID calendario (estratto da una pagina con macro calendar). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Tools are clearly separated by prefixes (confluence_, jira_, xray_), and each tool targets a distinct action on a specific resource. There is no overlap or ambiguity between tools, as even similar operations like adding comments are scoped to different platforms.
All tools follow a consistent verb_noun pattern with snake_case, prefixed by platform (confluence_, jira_, xray_). This makes the naming predictable and easy for agents to parse and select tools.
With 22 tools covering Jira, Confluence, and Xray, the count is well-scoped for a combined server. It provides enough functionality without overwhelming the agent, and each tool serves a clear purpose.
The set covers core CRUD-like operations for both Jira and Confluence, including search, comments, transitions, and project roles. Missing delete operations (common in MCP) and some advanced features, but the main workflows are supported. The Xray tool is limited but fits the domain.