JIRA MCP Integration
@MankowskiNick
About JIRA MCP Integration
A Model-Context-Protocol(MCP) server to allow Claude desktop to create Jira tickets.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"jira-mcp": {
"command": "node",
"args": [
"/path/to/project/build/index.js"
],
"env": {
"JIRA_HOST": "your-site.atlassian.net",
"JIRA_USERNAME": "[email protected]",
"JIRA_API_TOKEN": "your_api_token",
"JIRA_PROJECT_KEY": "your_project_key",
"AUTO_CREATE_TEST_TICKETS": "true",
"JIRA_ACCEPTANCE_CRITERIA_FIELD": "customfield_10429",
"JIRA_STORY_POINTS_FIELD": "customfield_10040",
"JIRA_EPIC_LINK_FIELD": "customfield_10014",
"JIRA_PRODUCT_FIELD": "customfield_10757",
"JIRA_PRODUCT_VALUE": "Your Product Name",
"JIRA_PRODUCT_ID": "12345",
"JIRA_CATEGORY_FIELD": "customfield_10636",
"USE_ALTERNATE_CATEGORY": "false",
"JIRA_DEFAULT_CATEGORY_VALUE": "Default Category",
"JIRA_DEFAULT_CATEGORY_ID": "12345",
"JIRA_ALTERNATE_CATEGORY_VALUE": "Alternate Category",
"JIRA_ALTERNATE_CATEGORY_ID": "67890"
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is JIRA MCP Integration?
A Model Context Protocol (MCP) server that integrates JIRA with Claude, enabling AI assistants to create, search, update, and link JIRA tickets, and manage Zephyr test steps directly from conversations.
How to use JIRA MCP Integration?
Install the server via git clone, npm install, and npm run build (or npm run build-win on Windows). Add a configuration entry to your Claude desktop config file (claude_desktop_config.json) with the command "node", args pointing to the built index.js, and environment variables for your JIRA instance (host, email, API token, project key). After restarting Claude, the server’s tools are available for use.
Key features of JIRA MCP Integration
- Create JIRA tickets with summary, description, acceptance criteria, and issue type
- Search JIRA tickets using flexible JQL queries or by issue type
- Assign story points to Story tickets and auto‑create linked Test tickets
- Update existing JIRA tickets with new field values
- Link JIRA tickets together with specified relationship types
- Retrieve and add test steps for Zephyr test tickets
Use cases of JIRA MCP Integration
- Create a new JIRA bug or story directly from a Claude conversation
- Search for open bugs by issue type and priority without leaving the chat
- Update a ticket’s sprint or story points during a planning discussion
- Automatically generate a linked Test ticket when a Story is created with points
- Link related tickets (e.g., duplicate, blocks) as part of a workflow
FAQ from JIRA MCP Integration
How do I get a JIRA API token?
Generate a token from your Atlassian account at https://id.atlassian.com/manage/api-tokens. Use it as the JIRA_API_TOKEN environment variable.
What environment variables are required?
The four required variables are JIRA_HOST, JIRA_USERNAME, JIRA_API_TOKEN, and JIRA_PROJECT_KEY. Optional variables control custom fields, Zephyr integration, and test ticket creation.
Can I use this server with Zephyr for test management?
Yes. Set the Zephyr environment variables (ZAPI_BASE_URL, ZAPI_ACCESS_KEY, ZAPI_SECRET_KEY, ZAPI_JWT_EXPIRE_SEC) to enable the get-test-steps and add-test-steps tools.
How do I find custom field IDs for my JIRA instance?
Open a ticket in JIRA, press F12 to open developer tools, go to the Network tab, refresh the page, and look for a request to issue/[ISSUE-KEY]. The response contains custom field IDs. Alternatively, call GET /rest/api/3/field on your JIRA instance.
What authentication does the server use?
It uses HTTP Basic Authentication with a JIRA API token. The username is your email and the password is the token provided in the JIRA_API_TOKEN environment variable.
Frequently asked questions
How do I get a JIRA API token?
Generate a token from your Atlassian account at `https://id.atlassian.com/manage/api-tokens`. Use it as the `JIRA_API_TOKEN` environment variable.
What environment variables are required?
The four required variables are `JIRA_HOST`, `JIRA_USERNAME`, `JIRA_API_TOKEN`, and `JIRA_PROJECT_KEY`. Optional variables control custom fields, Zephyr integration, and test ticket creation.
Can I use this server with Zephyr for test management?
Yes. Set the Zephyr environment variables (`ZAPI_BASE_URL`, `ZAPI_ACCESS_KEY`, `ZAPI_SECRET_KEY`, `ZAPI_JWT_EXPIRE_SEC`) to enable the `get-test-steps` and `add-test-steps` tools.
How do I find custom field IDs for my JIRA instance?
Open a ticket in JIRA, press F12 to open developer tools, go to the Network tab, refresh the page, and look for a request to `issue/[ISSUE-KEY]`. The response contains custom field IDs. Alternatively, call `GET /rest/api/3/field` on your JIRA instance.
What authentication does the server use?
It uses HTTP Basic Authentication with a JIRA API token. The username is your email and the password is the token provided in the `JIRA_API_TOKEN` environment variable.
Basic information
More Version Control MCP servers
Jira MCP
nguyenvanduocitA Go-based MCP (Model Control Protocol) connector for Jira that enables AI assistants like Claude to interact with Atlassian Jira. This tool provides a seamless interface for AI models to perform common Jira operations including issue management, sprint planning, and workflow tra
MCP Linear
tacticlaunchMCP server that enables AI assistants to interact with Linear project management system through natural language, allowing users to retrieve, create, and update issues, projects, and teams.
Integrate MCP with GitHub Copilot
skillsLearn how to use MCP Servers with GitHub Copilot
MCP Atlassian Server (by phuc-nt)
phuc-ntMCP server connecting AI assistants with Jira & Confluence for smart project management.
Atlassian Jira MCP Server
aashariNode.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.
Comments