jira-mcp
The JIRA MCP Server enables Large Language Models (LLMs) to interact with JIRA through standardized tools and context. It provides two main capabilities:
Search Issues with JQL: Execute complex JQL queries with pagination and customizable parameters like fields, expand options, and max results using the
jql_searchtool.Retrieve Issue Details: Fetch detailed information about specific JIRA issues using the
get_issuetool, including fields, properties, and expanded information.
The server supports integration with Claude Desktop, features customizable environment variables for JIRA instance URL, user email, and API key, and can be installed via Smithery for seamless integration.
Allows interaction with JIRA through JQL search queries and retrieving detailed issue information
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jira-mcp search for issues assigned to me that are in progress"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JIRA MCP Server
An MCP server that enables Large Language Models (LLMs) to interact with JIRA through standardized tools and context. This server provides capabilities for searching issues using JQL and retrieving detailed issue information.
Features
JQL Search: Execute complex JQL queries with pagination support
Issue Details: Retrieve detailed information about specific JIRA issues
Related MCP server: JIRA MCP Server
Prerequisites
npminstalledA JIRA instance with API access
JIRA API token or Personal Access Token
JIRA user email associated with the API token
Getting JIRA API Credentials
Log in to your Atlassian account at https://id.atlassian.com
Navigate to Security settings
Under API tokens, select "Create API token"
Give your token a meaningful name (e.g., "MCP Server")
Copy the generated token - you won't be able to see it again!
Use this token as your
JIRA_API_KEYUse the email address associated with your Atlassian account as
JIRA_USER_EMAIL
Usage
Integration with Claude Desktop
Add the server configuration to Claude Desktop's config file:
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": "your-email@company.com",
"JIRA_API_KEY": "your-api-token"
}
}
}
}Restart Claude Desktop to load the new configuration.
Available Tools
1. JQL Search (jql_search)
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 include
Example:
{
"jql": "project = 'MyProject' AND status = 'In Progress'",
"maxResults": 10,
"fields": ["summary", "status", "assignee"]
}2. Get Issue (get_issue)
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 errors
Example:
{
"issueIdOrKey": "PROJ-123",
"fields": ["summary", "description", "status"],
"expand": "renderedFields,names"
}Development
Configuration
Set up your environment variables before running the server. Create a .env file in the root directory:
JIRA_INSTANCE_URL=https://your-instance.atlassian.net
JIRA_USER_EMAIL=your-email@company.com
JIRA_API_KEY=your-api-tokenReplace the values with:
Your actual JIRA instance URL
The email address associated with your JIRA account
Your JIRA API token (can be generated in Atlassian Account Settings)
Installation
Installing via Smithery
To install JIRA for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install jira-mcp --client claudeManual Installation
Clone this repository:
git clone <repository-url>
cd jira-mcpInstall dependencies:
npm installRunning with MCP Inspector
For testing and development, you can use the MCP Inspector:
npm run inspectAdding New Tools
To add new tools, modify the ListToolsRequestSchema handler in index.js:
server.setRequestHandler(ListToolsRequestSchema, async () => {
return {
tools: [
// Existing tools...
{
name: "your_new_tool",
description: "Description of your new tool",
inputSchema: {
// Define input schema...
}
}
]
};
});Then implement the tool in the CallToolRequestSchema handler.
License
MIT
Contributing
Contributions are welcome! Please feel free to submit a PR.
Available Tools
2 toolsget_issueC
Retrieve details about an issue by its ID or key.
Inputs: issueIdOrKey (required), fields, expand, properties, +1 more.
jql_searchC
Perform enhanced JQL search in Jira
Inputs: jql (required), nextPageToken, maxResults, fields, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_issue retrieves a single issue by ID/key, while jql_search performs broader queries using JQL. There is no overlap or ambiguity between them, as they serve different use cases (specific lookup vs. flexible search).
Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: get_issue and jql_search. The naming is predictable and readable, with no deviations or mixed conventions.
With only 2 tools, this server feels severely under-scoped for a Jira integration. A typical Jira MCP would need more operations like create_issue, update_issue, or list_projects to cover basic workflows. The current set is too thin for meaningful agent interaction.
The tool surface is significantly incomplete for Jira's domain. While get_issue and jql_search provide read/search capabilities, there are major gaps in CRUD operations (no create, update, or delete) and missing lifecycle management (e.g., transitions, comments). This will cause agent failures in common scenarios.
Related MCP Connectors
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
List, view, create, edit, delete, comment on, and see the history of Laraue Boards issues.
Search and read Zammad tickets, customers and organizations; add notes, replies and ticket updates.
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI models to search Jira issues using JQL and retrieve issue details through the Jira 9.12.14 API.20 npmMIT
- AlicenseAqualityDmaintenanceEnables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.911 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides JIRA issue search, retrieval, and update functionalities via MCP.63 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables querying Jira issues using JQL and creating new issues programmatically via natural language.876 npmMIT