mcp-jira-server
by: 1broseidon
mcp jira server
📌Overview
Purpose: To provide a Model Context Protocol server that facilitates integration with Jira's REST API, enabling AI assistants to manage Jira issues programmatically.
Overview: Jira MCP Server offers a suite of tools for efficient management of Jira issues, allowing users to create, update, list, and delete issues while also managing comments. It is designed to streamline Jira interactions via a straightforward API interface.
Key Features:
-
Create New Issues: Allows users to create various types of Jira issues (Tasks, Epics, Subtasks), specifying title and description.
-
List Issues: Enables users to retrieve issues from a project with optional status filtering, facilitating easy tracking of issue progress.
-
Update Existing Issues: Provides functionality to modify a Jira issue's summary, description, and status, ensuring current information management.
-
Get Detailed Issue Information: Retrieves comprehensive details about specific issues, aiding in informed decision-making.
-
Delete Issues: Empowers users to remove Jira issues that are no longer needed, maintaining an organized project space.
-
Add Comments to Issues: Lets users contribute comments to existing issues, enhancing collaboration and communication within the team.
Jira MCP Server
A Model Context Protocol server that integrates with Jira's REST API, enabling AI assistants to manage Jira issues programmatically.
Features
The server supports:
- Creating new issues (Tasks, Epics, Subtasks)
- Listing issues with optional status filtering
- Updating existing issues (summary, description, status)
- Retrieving detailed issue information
- Deleting issues
- Adding comments to issues
Setup
Prerequisites
- A Jira account with API access
- Jira API token (generated from Atlassian Account Settings: https://id.atlassian.com/manage-profile/security/api-tokens)
Installation
- Install dependencies:
npm install
- Build the server:
npm run build
Configuration
- Create a
.jira-config.json
file in your working directory:
{
"projectKey": "YOUR_PROJECT_KEY"
}
- Configure the MCP server with your Jira credentials:
- On MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- On Windows:
%APPDATA%/Claude/claude_desktop_config.json
Example configuration:
{
"mcpServers": {
"jira": {
"command": "node",
"args": ["/path/to/jira-server/build/index.js"],
"env": {
"JIRA_EMAIL": "your-email@example.com",
"JIRA_API_TOKEN": "your-api-token",
"JIRA_DOMAIN": "your-domain"
}
}
}
}
Available Tools
create_issue
Creates a new Jira issue.
- Required parameters:
- working_dir: Directory containing
.jira-config.json
- summary: Issue title
- description: Issue description
- type: Issue type (Task, Epic, or Subtask)
- working_dir: Directory containing
list_issues
Lists issues in the project.
- Required parameters:
- working_dir: Directory containing
.jira-config.json
- working_dir: Directory containing
- Optional parameters:
- status: Filter by status (e.g., "To Do", "In Progress", "Done")
update_issue
Updates an existing issue.
- Required parameters:
- working_dir: Directory containing
.jira-config.json
- issue_key: Issue key (e.g., PRJ-123)
- working_dir: Directory containing
- Optional parameters:
- summary: New title
- description: New description
- status: New status
get_issue
Retrieves detailed information about a specific issue.
- Required parameters:
- working_dir: Directory containing
.jira-config.json
- issue_key: Issue key (e.g., PRJ-123)
- working_dir: Directory containing
delete_issue
Deletes a Jira issue.
- Required parameters:
- working_dir: Directory containing
.jira-config.json
- issue_key: Issue key (e.g., PRJ-123)
- working_dir: Directory containing
add_comment
Adds a comment to an existing issue.
- Required parameters:
- working_dir: Directory containing
.jira-config.json
- issue_key: Issue key (e.g., PRJ-123)
- comment: Comment text to add
- working_dir: Directory containing
Development
For development with auto-rebuild:
npm run watch
Error Handling
The server handles errors such as:
- Invalid project keys
- Missing configuration
- Invalid issue types
- API authentication errors
- Invalid status transitions
Output Formatting
Issue information includes:
- Issue key and summary
- Issue type and status
- Creation date and creator
- Description
- Comments (with author and timestamp)