Provides JQL search and issue detail retrieval for Jira via MCP clients.
Configuration
View docs{
"mcpServers": {
"camdenclark-jira-mcp": {
"command": "npx",
"args": [
"-y",
"jira-mcp"
],
"env": {
"JIRA_API_KEY": "your-api-token",
"JIRA_USER_EMAIL": "[email protected]",
"JIRA_INSTANCE_URL": "https://your-instance.atlassian.net"
}
}
}
}This MCP server lets you interact with JIRA from your preferred MCP client, enabling you to search issues with JQL and fetch detailed issue data using standardized tools. It streamlines querying Jira data and integrating it into your workflows.
You connect to the JIRA MCP Server from an MCP client by using the provided tools to run JQL searches and retrieve issue details. Use the JQL Search tool to query issues with pagination and selective fields, then use Get Issue to pull comprehensive information about a specific issue. Combine results to build workflows that monitor project status, triage work, or automate reporting.
To start, set up the server configuration in your MCP client of choice (for Claude Desktop, you’ll provide environment values so the client can launch the server locally). Then call the JQL Search tool to locate issues that match your criteria, and use Get Issue to inspect individual issues in detail. You can tailor the fields and expansions you request to limit data and optimize response times.
Prerequisites you need before installing the server include Node.js and npm installed on your system, a Jira instance with API access, and a Jira API token associated with a user email.
If you want to install the Jira MCP Server through an automated installer, run:
npx -y @smithery/cli install jira-mcp --client claudeFor manual installation, clone and install dependencies, then prepare to run the server locally:
git clone <repository-url>
cd jira-mcp
npm installOptionally, for development and testing, you can inspect the MCP setup with the inspector:
npm run inspectCreate a local environment configuration file with your Jira connection details. The values below are placeholders you should replace with your actual Jira instance URL, user email, and API token.
JIRA_INSTANCE_URL=https://your-instance.atlassian.net
[email protected]
JIRA_API_KEY=your-api-tokenThe Jira MCP Server is designed to be run as a local process that your MCP client can invoke. It relies on environment variables to connect to Jira and does not require exposing the Jira API to the public internet from the MCP client side.
Treat your Jira API token like a password. Store it securely in environment variables or a secrets manager and never commit it to source control.
If you encounter authentication errors, double‑check that your JIRA_API_KEY matches the token generated for the Jira user email and that the JIRA_INSTANCE_URL points to your Jira instance. Ensure the API token has not expired and that the user has the required permissions for the queries you execute.
The server exposes two core tools you can use from your MCP client: JQL Search and Get Issue. Configure your client to use the stdio command to start the Jira MCP Server with the necessary environment variables.
Executes a JQL search with pagination and optional fields to return a subset of Jira issues that match your query.
Retrieves detailed information about a specific Jira issue, with options to specify fields and expansions.