Jira MCP Server
About
# Jira MCP Server This project is a server that acts as a bridge between Jira and the MCP (Model Context Protocol). It allows synchronization and interaction with Jira data through an MCP interface. ## Technologies Used - **Kotlin**: Main programming language - **Ktor**: Web framework for creating REST API -…
Explore
- Search Jira issues using JQL.
- Get detailed issue information including comments.
- Update existing Jira issues.
- Retrieve available status transitions for an issue.
- Change issue status via transitions.
- Search for and assign Jira users.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Jira MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
The project requires the following environment variables:
- JIRA_URL: The URL of your Jira instance
- JIRA_EMAIL: The email associated with your Jira account
- JIRA_API_TOKEN: The Jira API token
2 MCP modes: SSE or stdio
- Java 21 or higher
- Docker and Docker Compose
- A Jira account with appropriate permissions
Here is an example configuration for docker-compose.yml:
services:
jira-mcp-server:
image: ghcr.io/noxfr/jira-mcp-sse:latest
ports:
- "3001:3001"
environment:
- JIRA_URL=https://your-instance.atlassian.net
- [email protected]
- JIRA_PAT=your_jira_api_token
To pull and run the pre-built Docker image:
```bash
Here are examples of interactions with MCP via an AI assistant (like Claude Desktop or Cursor):
- Fix all tickets in project XXX concerning label errors and set them to review
- Suggest an implementation for ticket XXX
etc.
search_issues
Search JIRA issues using JQL.
get_issue
Get detailed information about a specific JIRA issue including comments.
update_issue
Update an existing JIRA issue.
get_transitions
Get available status transitions for a JIRA issue.
transition_issue
Change the status of a JIRA issue by performing a transition.
get_users
Search for JIRA users.
assign_issue
Assign a JIRA issue to a user.
The server exposes the following tools via MCP:
- search_issues: Search JIRA issues using JQL.
- get_issue: Get detailed information about a specific JIRA issue including comments.
- update_issue: Update an existing JIRA issue.
- get_transitions: Get available status transitions for a JIRA issue.
- transition_issue: Change the status of a JIRA issue by performing a transition.
- get_users: Search for JIRA users.
- assign_issue: Assign a JIRA issue to a user.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"jira mcp server": {
"mcp-kotlin-jira-server": {
"url": "http://127.0.0.1:3001/sse"
},
"mcp-kotlin-jira-stdio": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"JIRA_URL",
"-e",
"JIRA_EMAIL",
"-e",
"JIRA_PAT",
"docker.io/library/jira-mcp-server-jira-mcp-server"
],
"env": {
"JIRA_URL": "TBD",
"JIRA_EMAIL": "TBD",
"JIRA_PAT": "TBD"
}
}
}
}
}McpServers
{
"mcp-kotlin-jira-server": {
"url": "http://127.0.0.1:3001/sse"
},
"mcp-kotlin-jira-stdio": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"JIRA_URL",
"-e",
"JIRA_EMAIL",
"-e",
"JIRA_PAT",
"docker.io/library/jira-mcp-server-jira-mcp-server"
],
"env": {
"JIRA_URL": "TBD",
"JIRA_EMAIL": "TBD",
"JIRA_PAT": "TBD"
}
}
}This project is a server that acts as a bridge between Jira and the MCP (Model Context Protocol). It allows synchronization and interaction with Jira data through an MCP interface.
Technologies Used
- Kotlin: Main programming language
- Ktor: Web framework for creating REST API
- Gradle: Build system
- Docker: Application containerization
- MCP (Model Context Protocol): Communication protocol used for interoperability
Docker Packages
This project provides two Docker images that are built and pushed to the GitHub Container Registry:
- jira-mcp-stdio: An image configured for stdio mode communication.
- jira-mcp-sse: An image configured for SSE (Server-Sent Events) mode communication.
Note: These images are automatically built and pushed on updates to the main branch.
You can pull these images from the GitHub Container Registry using the following commands:
docker pull ghcr.io/noxfr/jira-mcp-stdio:latest
docker pull ghcr.io/noxfr/jira-mcp-sse:latest
Development prerequisites
- Java 21 or higher
- Docker and Docker Compose
- A Jira account with appropriate permissions
Configuration
The project requires the following environment variables:
- JIRA_URL: The URL of your Jira instance
- JIRA_EMAIL: The email associated with your Jira account
- JIRA_API_TOKEN: The Jira API token
2 MCP modes: SSE or stdio
Running Locally via Docker Compose
Here is an example configuration for docker-compose.yml:
services:
jira-mcp-server:
image: ghcr.io/noxfr/jira-mcp-sse:latest
ports:
- "3001:3001"
environment:
- JIRA_URL=https://your-instance.atlassian.net
- [email protected]
- JIRA_PAT=your_jira_api_token
Building and Running
To pull and run the pre-built Docker image:
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
