Provides tools for searching and retrieving Jira issues, comments, subtasks, and attachments, enabling AI agents to interact with Jira projects and tickets.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@copilot-jira-mcp Show me my assigned Jira tickets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quick Start • Features • Supported Clients • Available Tools • Examples • Marketing & Community
No manual file editing required. Run the guided installer in 1 command:
curl -fsSL https://raw.githubusercontent.com/GiDanis/copilot-jira-mcp/main/setup/install.sh | bashirm https://raw.githubusercontent.com/GiDanis/copilot-jira-mcp/main/setup/install.ps1 | iexnpx copilot-jira-mcp setupThe setup wizard will test your credentials and automatically register the server across GitHub Copilot CLI, Claude Desktop, and Cursor!
Related MCP server: Jira Cloud MCP Server
Without Copilot Jira MCP 😫 | With Copilot Jira MCP 🚀 |
🔀 Constantly alt-tabbing between IDE and browser | 💬 Ask your AI assistant directly in your editor |
📋 Manually hunting down acceptance criteria | 📝 Instant Markdown-rendered specs & subtasks |
🖱️ 15 clicks to move a ticket to In Progress | ⚡ "Move PROJ-42 to In Progress with comment..." |
🔎 Writing manual JQL in Jira search bars | 🧠 AI translates plain English into precise JQL |
⏳ Context loss during code reviews | 🔍 Pull requirements right alongside the diff |
sequenceDiagram
autonumber
actor Dev as 👨💻 Developer
participant AI as 🤖 AI Assistant (Copilot / Claude / Cursor)
participant MCP as 🎫 Copilot Jira MCP Server
participant Jira as ☁️ Atlassian Jira Cloud
Dev->>AI: "Summarize PROJ-123 requirements and move it to In Progress"
AI->>MCP: Call jira_get_issue(issue_key: "PROJ-123")
MCP->>Jira: GET /rest/api/3/issue/PROJ-123
Jira-->>MCP: Raw Atlassian Document Format (ADF)
MCP-->>AI: Clean Markdown spec, fields & subtasks
AI->>MCP: Call jira_transition_issue(issue_key: "PROJ-123", transition: "In Progress")
MCP->>Jira: POST /rest/api/3/issue/PROJ-123/transitions
Jira-->>MCP: 204 No Content (Success)
MCP-->>AI: Transition confirmed
AI-->>Dev: "Here are the requirements for PROJ-123. I've updated the status to In Progress!"🔍 Smart JQL Search - Search issues via natural language or raw JQL with full pagination support
📝 Native ADF ➔ Markdown Parser - Converts Atlassian Document Format (ADF) into clean Markdown (code blocks, lists, tables, quotes, headings)
⚡ Workflow Transitions - Advance ticket statuses (e.g., To Do ➔ In Progress ➔ Done) with optional resolution comments
💬 Comment Threads - Read discussions and append new comments to issues
🆕 Create & Update Issues - Create new Tasks, Bugs, and Stories; edit summaries, descriptions, priorities, and labels
🔗 Subtasks & Issue Links - Inspect parent-child hierarchies and linked blocking issues
📁 Project Discovery - List all accessible Jira projects and metadata
👤 My Work Overview - Instant access to issues assigned to you
🔌 1-Click Multi-Client Auto-Registration - Configures Copilot CLI, Claude Desktop, and Cursor automatically
🔒 Enterprise-Grade Security - Credentials strictly stay in local environment variables; zero third-party telemetry
Client | Status | Configuration File |
GitHub Copilot CLI | ✅ Native |
|
Claude Desktop | ✅ Native |
|
Cursor IDE | ✅ Native |
|
Windsurf & VS Code | ✅ Supported | Standard MCP Stdio Configuration |
Antigravity / Gemini | ✅ Supported | Local Stdio Transport |
Copilot Jira MCP exposes 12 comprehensive tools spanning read, write, and workflow actions:
Tool | Action | Description |
| 🔍 Read | Comprehensive issue details, markdown description, subtasks, links, priority |
| 🔍 Read | Search Jira issues using JQL syntax with pagination |
| 🔍 Read | Quick query for tickets assigned to current user, optional status filter |
| 🔍 Read | Retrieve discussion history with author, date, and formatted text |
| 🔍 Read | List all subtasks and child issues linked to a parent ticket |
| 🔍 Read | List all Jira projects accessible by authenticated account |
| 🔍 Read | List valid status transitions for an issue workflow |
| 🔍 Read | Test connection and display authenticated user details |
| ✏️ Write | Create new issue (Task, Bug, Story) with summary, description, priority, labels |
| ✏️ Write | Modify existing issue summary, description, priority, or labels |
| ✏️ Write | Post a new comment to an issue (plain text or markdown supported) |
| ⚡ Action | Move an issue through workflow states (In Progress, Done, etc.) |
(Legacy aliases jira_get_ticket, jira_search_tickets, and jira_get_my_tickets are maintained for 100% backwards compatibility).
Once installed, simply talk naturally to your AI:
# In Copilot CLI, Claude Desktop, or Cursor:
> "Show me my open tickets in project PROJ"
> "What are the acceptance criteria for PROJ-1234?"
> "Add a comment to PROJ-1234: 'PR #42 is up for review.'"
> "Move PROJ-1234 to 'In Progress'"
> "Create a high priority bug: 'Payment gateway timeout on checkout'"
> "List all blockers linked to PROJ-567"
> "Who am I logged in as in Jira?"The jira-mcp CLI provides interactive management commands:
# Interactive dashboard (wizard, client registration, diagnostics)
npx copilot-jira-mcp
# Guided setup wizard
jira-mcp setup
# Register with all detected MCP client configs
jira-mcp register
# Test Jira credentials and print connection info
jira-mcp test
# Start server directly (used by AI clients)
jira-mcp start
# Show help
jira-mcp --helpIf you prefer configuring manually, set these environment variables:
export JIRA_URL="https://your-company.atlassian.net"
export JIRA_EMAIL="your-email@company.com"
export JIRA_API_TOKEN="your-atlassian-api-token"Then add this block to your client config (~/.copilot/mcp.json or claude_desktop_config.json):
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "copilot-jira-mcp", "start"],
"env": {
"JIRA_URL": "${JIRA_URL}",
"JIRA_EMAIL": "${JIRA_EMAIL}",
"JIRA_API_TOKEN": "${JIRA_API_TOKEN}"
}
}
}
}# Run unit test suite (10/10 tests pass)
npm test
# Run ESLint check
npm run lintZero Plaintext Storage: Tokens are stored strictly in user-level environment variables or .env.
Zero Third-Party Relays: Direct HTTPS communication with your Jira Cloud/Server instance.
.gitignore Enforced: Credential files are never tracked by version control.
See SECURITY.md for vulnerability disclosure.
If Copilot Jira MCP saves you time and context-switching:
⭐ Star this repository on GitHub
🐦 Share on X / Twitter: Click to Tweet
💼 Share on LinkedIn: Check out ready-made posts in MARKETING.md
💡 Suggest features in Discussions
MIT © 2026 Giuseppe Danise — see LICENSE for details.
Recupera tutti i ticket assegnati all'utente corrente
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Filtra per stato (es. "In Progress", "Open", "To Do") | |
| max_results | No | Numero massimo di risultati (default: 20) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It only states the primary action and scope but does not disclose read-only nature, default statuses, ordering, pagination behavior, or any authentication/rate-limit considerations. The max_results parameter hints at pagination but the description does not elaborate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence that directly states the tool's purpose without any filler or repetition. It is appropriately front-loaded and concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with two optional parameters and no output schema, the description covers the core functionality. However, it lacks usage differentiation from siblings and does not describe the return format or default behavior, which could be important for an agent to fully understand the tool's output.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with clear descriptions for 'status' and 'max_results'. The tool description adds no extra meaning beyond those schema definitions, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Recupera tutti i ticket assegnati all'utente corrente' (Retrieves all tickets assigned to the current user), specifying a concrete action and resource with scope. It distinguishes from siblings by focusing on current-user assignment rather than a single ticket (jira_get_ticket) or general search (jira_search_tickets).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus the siblings. The description does not mention alternatives or contexts where jira_search_tickets might be more appropriate, nor any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recupera i dettagli di un ticket Jira specifico tramite la sua chiave (es. IIAB-81069)
| Name | Required | Description | Default |
|---|---|---|---|
| ticket_key | Yes | La chiave del ticket Jira (es. IIAB-81069) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It states it retrieves details, implying a read-only operation, but does not disclose any additional behavioral traits such as error handling, required permissions, or side effects. The behavior is simple and inferable, so a 3 is appropriate—clear but not rich in context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that contains all essential information: the action, the target, and the parameter format. No filler or redundancy. It is front-loaded with the verb and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple retrieval tool with one parameter and no output schema, the description is complete. It tells the agent exactly what the tool does and what input is needed. The lack of output structure is not a gap because the tool's purpose is clear—returning ticket details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description already covers the parameter fully (Key of the Jira ticket with example IIAB-81069). The tool description repeats the same example, adding no new semantic value beyond what the schema provides. Since schema coverage is 100%, baseline 3 is warranted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Recupera i dettagli' - retrieves the details), the resource (a specific Jira ticket), and the unique identifier (its key). It distinguishes itself from siblings by emphasizing 'specifico tramite la sua chiave', which clearly separates it from searching or getting my tickets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the use case: when you have a specific ticket key and need its details. It doesn't explicitly compare with sibling tools (jira_search_tickets, jira_get_my_tickets), but the context is clear enough that this is the tool for a known key. Missing explicit exclusions or alternative recommendations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Cerca ticket Jira usando JQL (Jira Query Language). Esempi: "project = IIAB AND status = Open", "assignee = currentUser()", "labels = backend"
| Name | Required | Description | Default |
|---|---|---|---|
| jql | Yes | Query JQL per cercare i ticket | |
| max_results | No | Numero massimo di risultati (default: 20) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Non sono presenti annotations, quindi la descrizione deve indicare il comportamento. Dice solo che esegue una ricerca con JQL, ma non specifica se è read-only, il formato di ritorno (es. array di ticket), l'ordine, la paginazione o eventuali limiti. Manca trasparenza su aspetti comportamentali rilevanti.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Descrizione in una frase breve con tre esempi immediatamente utili. Nessuna parola superflua, il contenuto è front-loaded e facilmente consultabile.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Per uno strumento semplice con due parametri ben documentati e una funzione di ricerca ben exemplificata, la descrizione è quasi completa. Manca però la forma del risultato (output non definito) e un riferimento esplicito ai casi d'uso alternativi, ma il tutto resta comunque utilizzabile.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Lo schema copre al 100% i parametri con descrizioni chiare. La descrizione aggiunge valore con esempi concreti di JQL che chiariscono la sintassi del parametro jql, pur non aggiungendo nulla su max_results oltre allo schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
La descrizione usa un verbo specifico ('Cerca') e indica chiaramente l'oggetto ('ticket Jira') e il metodo (JQL). Gli esempi illustrano il tipo di query, differenziando il tool dai sibling come jira_get_ticket e jira_get_my_tickets che non eseguono ricerche libere.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
L'uso è implicito: si usa quando si vuole cercare ticket tramite JQL, come mostrato dagli esempi. Tuttavia non vengono esplicitati quando usare questo tool rispetto ai sibling (come jira_get_ticket per un ticket singolo o jira_get_my_tickets per i propri) né le esclusioni.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0jira_get_my_ticketsjira_get_ticketjira_search_ticketsScored across 3 tools
Each tool targets a distinct retrieval mode: by key, by JQL query, and by assignee. Although search could mimic get_my_tickets with a JQL, the dedicated tool adds convenience and clarity.
All tools follow a consistent 'jira_<verb>_<noun>' pattern, making the tool set predictable and easy to navigate.
With only 3 tools, the set is concise but reasonable for a read-only Jira assistant. It is within the ideal range, though slightly sparse.
The server only supports reading tickets. Missing create, update, transition, and comment operations leaves significant gaps for typical Jira workflows, so the surface feels incomplete.
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
The Jam MCP server provides AI tools with instant bug context without manual prompting, enabling a streamlined workflow from bug identification to ticket creation and pull request generation without switching between tools.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
