This MCP server enables Large Language Models (LLMs) to interact with JIRA through standardized tools and context, providing capabilities for searching issues using JQL and retrieving detailed information about specific JIRA issues.
npm
installedJIRA_API_KEY
JIRA_USER_EMAIL
To install JIRA for Claude Desktop automatically using Smithery:
npx -y @smithery/cli install jira-mcp --client claude
npm install jira-mcp
Set up your environment variables before running the server. You can create a .env
file in your project directory:
JIRA_INSTANCE_URL=https://your-instance.atlassian.net
[email protected]
JIRA_API_KEY=your-api-token
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"jira": {
"command": "npx",
"args": ["-y", "jira-mcp"],
"env": {
"JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
"JIRA_USER_EMAIL": "[email protected]",
"JIRA_API_KEY": "your-api-token"
}
}
}
}
Executes a JQL search query with customizable parameters.
Parameters:
jql
(required): JQL query stringnextPageToken
: Token for paginationmaxResults
: Maximum number of results to returnfields
: Array of field names to includeexpand
: Additional information to includeExample:
{
"jql": "project = 'MyProject' AND status = 'In Progress'",
"maxResults": 10,
"fields": ["summary", "status", "assignee"]
}
Retrieves detailed information about a specific issue.
Parameters:
issueIdOrKey
(required): Issue ID or keyfields
: Array of field names to includeexpand
: Additional information to includeproperties
: Array of properties to includefailFast
: Whether to fail quickly on errorsExample:
{
"issueIdOrKey": "PROJ-123",
"fields": ["summary", "description", "status"],
"expand": "renderedFields,names"
}
For testing purposes, you can use the MCP Inspector:
npx jira-mcp inspect
This allows you to interactively test the tools and view their responses before integrating with Claude.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "jira" '{"command":"npx","args":["-y","jira-mcp"],"env":{"JIRA_INSTANCE_URL":"https://your-instance.atlassian.net","JIRA_USER_EMAIL":"[email protected]","JIRA_API_KEY":"your-api-token"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"-y",
"jira-mcp"
],
"env": {
"JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
"JIRA_USER_EMAIL": "[email protected]",
"JIRA_API_KEY": "your-api-token"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"jira": {
"command": "npx",
"args": [
"-y",
"jira-mcp"
],
"env": {
"JIRA_INSTANCE_URL": "https://your-instance.atlassian.net",
"JIRA_USER_EMAIL": "[email protected]",
"JIRA_API_KEY": "your-api-token"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect