MCP.so
Sign In

JIRA MCP Server (Async)

@judexzhu

Basic information

Category

Version Control

Transports

stdio

Author

judexzhu

About JIRA MCP Server

A high-performance, asynchronous Model Context Protocol (MCP) server that integrates with JIRA using stdio transport

JIRA MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-jira-judexzhu": {
      "command": "uv",
      "args": [
        "sync"
      ]
    }
  }
}

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 (Async)?

A high-performance, asynchronous Model Context Protocol (MCP) server that integrates with JIRA using stdio transport. It allows AI assistants to perform JIRA operations—search, create, update issues, and track relationships—via MCP tools. Designed for developers using MCP clients like Claude Desktop.

How to use JIRA MCP Server (Async)?

Install with uv sync, configure environment variables JIRA_SERVER_URL and JIRA_API_TOKEN, then add the server to your MCP client’s configuration (e.g., Claude Desktop’s mcpServers block). The server runs over stdio and exposes tools with jira_ prefixes.

Key features of JIRA MCP Server (Async)

  • 8 MCP tools covering search, read, and write operations
  • Asynchronous, non-blocking API calls with connection pooling
  • Built-in rate limiting to respect JIRA API limits
  • Uses stdio transport for MCP client integration
  • Environment variables for timeouts, logging, and concurrency
  • Clean, tool-focused architecture without MCP resources

Use cases of JIRA MCP Server (Async)

  • Search JIRA issues with JQL from an AI assistant
  • Retrieve detailed issue information, comments, and links
  • Create new issues or update existing ones programmatically
  • Track epics, subtasks, and workflow transitions

Frequently asked questions

1

What JIRA operations does the server support?

The server provides tools for searching issues (`jira_search_issues`), getting details (`jira_get_issue_details`), reading comments and links, managing epics/subtasks, viewing transitions, and creating/updating issues—all with a `jira_` tool prefix.

2

What environment variables are required?

`JIRA_SERVER_URL` (your JIRA instance URL) and `JIRA_API_TOKEN` are required. Optional variables include `MAX_CONCURRENT_REQUESTS` (default 2), `REQUEST_TIMEOUT` (30s), `LOG_LEVEL`, and more.

3

What transport does the server use?

It uses stdio transport, optimized for MCP client integration. No HTTP endpoints are exposed; the server communicates over standard input/output.

4

What are the runtime dependencies?

Python 3.13+ and the `uv` package manager. The server uses `aiohttp` for async HTTP calls and implements built-in connection pooling and rate limiting.

5

Are there any known limitations?

Rate limiting is built-in; the default `MAX_CONCURRENT_REQUESTS` value is 2 (requests per second). The server does not expose MCP resources—only tools—and relies entirely on the provided API token for authentication.

Comments

More Version Control MCP servers