mcpField
J
Jira MCP Server

Jira MCP Server

Remote
github.com/NoxFrVersion Control1Updated 68w ago
Repository

About Jira MCP Server

Jira MCP Server connects Jira data and operations to MCP clients. It supports issue search and updates, status transitions, user lookup, and assignment over stdio or SSE.

Key features

  1. 01Search issues with JQL
  2. 02Retrieve issue details and comments
  3. 03Update issues and change status
  4. 04Search users and assign issues
  5. 05Run over stdio or SSE

Use cases

  1. 01Find Jira issues by JQL
  2. 02Review issue details and comments
  3. 03Update issue fields or status
  4. 04Assign issues to Jira users

MCP support

Exposes Jira issue and user operations as tools for MCP clients. Supports stdio and SSE communication modes.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttp://127.0.0.1:3001/sse
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
ocidocker.io/library/jira-mcp-server-jira-mcp-server

Tools

Details

From the project README

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
  • 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:

# Pull the Docker image
docker pull ghcr.io/noxfr/jira-mcp-sse:latest

# Run the service with Docker Compose
docker-compose up

Alternatively, if you prefer to build the image locally:

# Build the Docker image
docker-compose build

# Start the service
docker-compose up

The server will be accessible on port 3001.

Adding MCP

Configuration within the IDE

HTTP (using jira-mcp-sse image)

{
  "mcpServers": {
    "mcp-kotlin-jira-server": {
      "url": "http://127.0.0.1:3001/sse"
    }
  }
}

Stdio (using jira-mcp-stdio image)

{
  "mcpServers": {
    "mcp-kotlin-jira-stdio": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "JIRA_URL",
        "-e",
        "JIRA_EMAIL",
        "-e",
        "JIRA_PAT",
        "ghcr.io/noxfr/jira-mcp-stdio:latest"
      ],
      "env": {
        "JIRA_URL": "TBD",
        "JIRA_EMAIL": "TBD",
        "JIRA_PAT": "TBD"
      }
    }
  }
}

Usage Examples with an AI Assistant

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.

Available Tools

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.