jira

This Jira MCP Server provides a Bridge between Jira and the Model Context Protocol, allowing LLMs to query Jira data and perform actions such as listing projects, boards, sprints, and issues, and creating tasks. The server exposes a set of tools that map to Jira REST API calls: list_projects, list_boards, list_sprints_from_board, list_issues_from_sprint, and create_issue (limited to Task issue type). To use it, configure the MCP server with your Jira Personal Access Token and Jira instance URL, then issue prompts that specify the desired tool and its inputs. For example, ask to list projects to retrieve Jira projects, or request the first 50 issues from a sprint by selecting the appropriate board and sprint IDs. The tools are designed to be invoked by natural language prompts that map to the tool names and required inputs described in the README, enabling dynamic Jira exploration and issue creation via LLM-assisted workflows.

Prerequisites:

• Node.js v22.12.0 or above
• npm or pnpm installed
• Access to a Jira instance with a Personal Access Token (PAT)

Installation and setup (using npx to install and run):

1. Ensure Node.js is installed and accessible in your shell.
2. Run the MCP server via npx (no local installation required):

# Start the Jira MCP server (example using latest release)
npx -y @parassolanki/jira-mcp-server@latest

3. Set the required environment variables for Jira access (either in your shell or in the config when integrating with Claude Desktop):

export JIRA_PERSONAL_ACCESS_TOKEN="email@example.com:your_personal_jira_access_token"
export JIRA_BASE_URL="https://your-domain.atlassian.net"

4. Alternative: if using a local configuration in Claude Desktop, create the mcpServers entry as shown in the example in the README. You can also run locally for development using pnpm:

pnpm install
pnpm dev

5. Build or debug locally as needed:

pnpm build
pnpm inspector

Prerequisite notes:

• Ensure Jira Base URL points to your Jira Cloud or Server instance and that the PAT has the required scopes for the operations you intend to perform.
• If using Windows, you may need to adjust the command to wrap npx appropriately (as shown in the Windows example in the README).

Tips and common issues:

• Make sure JIRA_BASE_URL is the correct base URL for REST API access (e.g., https://your-domain.atlassian.net).
• The PAT should have permissions to read projects, boards, sprints, issues, and to create issues (as needed).
• The tools support optional inputs (query, maxResults, expand, etc.). Use them to fine-tune results and payloads.
• When running locally, enable verbose or inspector debugging to troubleshoot tool invocations and API responses.
• If encountering authentication errors, double-check token formatting (username:token) and token scopes, and ensure there are no extra spaces or newline characters in the environment variables.
• The npm package name is @parassolanki/jira-mcp-server; use the exact package name when integrating with MCP clients.