Jira MCP Server
by 1broseidon
The Jira MCP Server provides integration with Jira's REST API, allowing AI assistants to programmatically manage Jira issues. It enables the creation, listing, updating, and deletion of Jira issues, as well as adding comments.
Last updated: N/A
What is Jira MCP Server?
The Jira MCP Server is a Model Context Protocol server designed to facilitate interaction with the Jira REST API. It allows AI assistants and other applications to manage Jira issues through a defined protocol.
How to use Jira MCP Server?
To use the server, you need a Jira account with API access and a generated API token. After installing the dependencies and building the server, configure it with your Jira credentials in the claude_desktop_config.json file. Then, utilize the available tools (create_issue, list_issues, update_issue, get_issue, delete_issue, add_comment) by providing the required parameters.
Key features of Jira MCP Server
Create new issues (Tasks, Epics, Subtasks)
List issues with optional status filtering
Update existing issues (summary, description, status)
Get detailed issue information
Delete issues
Add comments to issues
Use cases of Jira MCP Server
Automating Jira issue creation based on AI-driven insights
Programmatically updating issue statuses based on project progress
Retrieving issue details for AI-powered reporting and analysis
Integrating Jira with other systems through a standardized protocol
FAQ from Jira MCP Server
What is a Model Context Protocol (MCP)?
What is a Model Context Protocol (MCP)?
MCP is a protocol that allows different applications and services to communicate and exchange information in a standardized way.
How do I generate a Jira API token?
How do I generate a Jira API token?
You can generate an API token from your Atlassian Account Settings under the Security section.
Where should I store my Jira configuration?
Where should I store my Jira configuration?
Create a .jira-config.json file in your working directory and configure the MCP server with your Jira credentials in the claude_desktop_config.json file.
What issue types are supported?
What issue types are supported?
The server supports creating Tasks, Epics, and Subtasks.
What error handling is included?
What error handling is included?
The server includes error handling for invalid project keys, missing configuration, invalid issue types, API authentication errors, and invalid status transitions.