JIRA MCP Integration

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.