copilot-jira-mcp
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.
π« Copilot Jira MCP Server
Turn your Jira into an AI-powered co-pilot.
Quick Start β’ Features β’ Supported Clients β’ Available Tools β’ Examples β’ Marketing & Community
β‘ 10-Second Quick Start
No manual file editing required. Run the guided installer in 1 command:
macOS / Linux
curl -fsSL https://raw.githubusercontent.com/GiDanis/copilot-jira-mcp/main/setup/install.sh | bashWindows (PowerShell)
irm https://raw.githubusercontent.com/GiDanis/copilot-jira-mcp/main/setup/install.ps1 | iexOr using NPX (Any OS)
npx 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
π‘ Why Copilot Jira MCP?
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 |
π How It Works
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!"β¨ Key Features
π 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
π± Supported Clients
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 |
π οΈ Available MCP Tools
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).
π¬ Interactive Query Examples
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?"π» CLI Commands
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 --helpβοΈ Manual Configuration
If 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}"
}
}
}
}π§ͺ Testing & Quality Assurance
# Run unit test suite (10/10 tests pass)
npm test
# Run ESLint check
npm run lintπ Security & Privacy
Zero 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.
.gitignoreEnforced: Credential files are never tracked by version control.See SECURITY.md for vulnerability disclosure.
π’ Spread the Word!
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
π License
MIT Β© 2026 Giuseppe Danise β see LICENSE for details.
Available Tools
3 toolsjira_get_my_ticketsB
Recupera tutti i ticket assegnati all'utente corrente
Inputs: status, max_results.
jira_get_ticketA
Recupera i dettagli di un ticket Jira specifico tramite la sua chiave (es. IIAB-81069)
Inputs: ticket_key (required).
jira_search_ticketsA
Cerca ticket Jira usando JQL (Jira Query Language). Esempi: "project = IIAB AND status = Open", "assignee = currentUser()", "labels = backend"
Inputs: jql (required), max_results.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored 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.
Maintenance
Related MCP Connectors
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.
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Jira to fetch issues by key and perform JQL searches. It provides a foundation for integrating multiple work systems, with planned support for Slack and GitHub.ISC
- AlicenseNot gradedqualityBmaintenanceMCP server for interacting with Jira Cloud instances. Enables issue management, JQL queries, project and sprint management, and batch operations via natural language interfaces.141 npm4MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for end-to-end Jira and GitHub integration, enabling AI agents in the IDE to automate workflows from issue tracking to pull request management.MIT
- AlicenseAqualityBmaintenanceMCP server for Jira Cloud enabling issue tracking, comments, transitions, and attachments management through natural language.5MIT