JIRA MCP server

Overview

A small Model Context Protocol server that lets AI clients such as Claude Code, Cursor and Open WebUI read a JIRA Data Center, Server or Cloud instance. It is read-only and stateless: no database and no volumes, only calls to the JIRA REST API, served over Streamable HTTP on port 8002. The server never writes to JIRA.

What it offers

Thirteen tools in five areas. Issues: search with JQL, full issue details with comments, links and changelog, and change requests with their custom details panel. Worklogs: for one issue, or in bulk across all projects for the last N days. Sprints: the active sprint, its issues and a board’s sprints by state. Users and groups: the members of a group, and a name or email resolved to an account. Projects: the projects a token can see and their valid statuses. Attachments come back as metadata only.

Running it

It ships as a Docker Compose service. A connectivity check calls JIRA’s server-info endpoint first and prints the real HTTP status, which tells a bad token from a wrong URL before the server starts. The same entry point works as a small CLI for ad-hoc queries, and the test suite is fully mock-driven, so it needs no live JIRA.