JIRA MCP Server

@karolswdev

Repository

Basic information

About JIRA MCP Server

No overview available yet

#jira #mcp #server #integration #api

JIRA MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

JIRA MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is JIRA MCP Server?

A flexible Go server that implements the Model Context Protocol (MCP) to interact with the JIRA Cloud REST API. It bridges AI assistants or developer tools (MCP clients) with JIRA, enabling automated issue management, searching, and Epic tracking through a standardized interface.

How to use JIRA MCP Server?

Clone the repository, set required environment variables (JIRA_MCP_JIRA_URL, JIRA_MCP_JIRA_USER_EMAIL, JIRA_MCP_JIRA_API_TOKEN), and run the server using make run (Go) or Docker (build image then make docker-run). The server listens on the configured port (default 8080) and exposes MCP-compatible endpoints.

Key features of JIRA MCP Server

Exposes JIRA actions via standard MCP endpoints
Create issues, search with JQL, retrieve details, and fetch Epic issues
Flexible configuration via environment variables, config file, or defaults
Ready for containerized deployment with Docker and Docker Compose
Comprehensive unit and integration tests
Clean architecture with dependency injection and structured logging

Use cases of JIRA MCP Server

Automate issue creation from AI assistant conversations
Query and display JIRA project status in development tools
Fetch all issues in an Epic for sprint planning via LLMs
Integrate task management into custom MCP-powered workflows
Search and retrieve issue details without leaving the coding environment

Frequently asked questions

What are the prerequisites?

You need Go 1.20+ (for local build), a JIRA Cloud instance, and a JIRA API token associated with a user email. Docker and Docker Compose are optional for containerized deployment.

How do I configure the server?

Configuration is loaded from environment variables prefixed with JIRA_MCP_ (highest priority), a config.yaml file, or application defaults. Required vars: JIRA_MCP_JIRA_URL, JIRA_MCP_JIRA_USER_EMAIL, JIRA_MCP_JIRA_API_TOKEN.

What API endpoints are available?

`POST /create_jira_issue`, `POST /search_jira_issues`, `GET /jira_issue/{issueKey}`, and `GET /jira_epic/{epicKey}/issues` (the Epic endpoint requires the JIRA_MCP_EPIC_LINK_FIELD_ID config).

How do I run the server with Docker?

Build the Docker image with `make docker-build`, create a `.env` file in the server directory with JIRA_MCP_ environment variables, then run `make docker-run` (which uses docker-compose up -d). To stop, run `docker-compose down`.

Where is my API token stored?

Never commit the token to version control. Use environment variables or a secure secrets manager. In Docker, store it in a `.env` file (excluded from Git) or inject it at runtime.

Comments

More Version Control MCP servers

Integrate MCP with GitHub Copilot

skills

Learn how to use MCP Servers with GitHub Copilot

225

Jira MCP

nguyenvanduocit

A Go-based MCP (Model Control Protocol) connector for Jira that enables AI assistants like Claude to interact with Atlassian Jira. This tool provides a seamless interface for AI models to perform common Jira operations including issue management, sprint planning, and workflow tra

Gerrit Review MCP Server

cayirtepeomer

This MCP server provides integration with Gerrit code review system, allowing AI assistants to review code changes and their details through a simple interface.

Git

modelcontextprotocol

Model Context Protocol Servers

88.1K

Atlassian Bitbucket MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get, comment, search). Connects AI directly to version control workflows through the standard MCP interface.

157