Log inSubmit server
MCP Jira Stdio logo

MCP Jira Stdio

Connects MCP clients to Jira for searching, creating, updating, and managing issues, projects, comments, users, and metadata.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Jira Stdio

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-jira-stdio": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-jira-stdio@latest"
      ],
      "env": {
        "JIRA_BASE_URL": "YOUR_VALUE_HERE",
        "JIRA_EMAIL": "YOUR_VALUE_HERE",
        "JIRA_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The mcp-jira-stdio MCP server connects MCP clients to Jira through the Jira REST API. It exposes tools for browsing projects, searching and editing issues, creating subtasks, adding comments, and inspecting Jira metadata. The server runs over stdio and authenticates with a Jira base URL, account email, and API token. Reach for it when an agent needs to read or change Jira data from Claude Code, Claude Desktop, or another MCP-compatible client.

Use cases

  • Search Jira issues with JQL
  • Create and update project issues
  • Inspect Jira fields before creating issues
  • Add comments to existing issues
  • Review issues assigned to the current user

Key features

  • Jira project and issue access
  • JQL issue search with pagination
  • Issue creation, updates, and subtasks
  • Comments with optional visibility
  • Jira metadata and user lookup
  • stdio-based MCP configuration

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 43d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 23h ago via OSV.dev · mcp-jira-stdio@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars14Stargazers on the source repository.
npm downloads4.2kPackage downloads in the last 30 days.
Last commit23d agoMost recent push to the default branch.

How MCP Jira Stdio works

What mcp-jira-stdio does

The mcp-jira-stdio MCP server exposes Jira operations as MCP tools for an agent or MCP client. It can list projects visible to the authenticated user, retrieve project details, fetch individual issues, and search with JQL. Issue management includes creating issues, updating fields such as summaries, descriptions, priorities, assignees, labels, components, and fix versions, and creating subtasks under existing issues.

The server also supports adding comments, including optional visibility restrictions by group or role. Metadata tools help clients inspect issue types, priorities, statuses, custom fields, users, and project-specific create metadata. A separate tool retrieves issues assigned to the current user.

How it works

The package runs as a Node.js MCP process using stdio transport. MCP clients start the process and communicate with it through the configured command, such as mcp-jira-stdio or npx mcp-jira-stdio. Each tool validates its inputs and then uses the configured Jira connection to perform the requested operation.

Jira results and errors are returned to the MCP client. The server does not require a successful Jira connection during startup: it can start and advertise its tools even when credentials are missing. Calls that need Jira access will return an authentication-related error until the environment is configured.

Setup and configuration

mcp-jira-stdio requires Node.js 20 or newer and a Jira instance. Set these environment variables for the process:

  • JIRA_BASE_URL: The Jira instance URL, without a trailing slash.
  • JIRA_EMAIL: The email address for the Jira account.
  • JIRA_API_TOKEN: The Jira API token.

For Jira Cloud, create the token in Atlassian account security settings. The package can be installed globally or locally from npm, or built from the source repository.

Claude Code can register the server with claude mcp add and the three environment variables. Claude Desktop uses an mcpServers entry with either the installed executable or npx mcp-jira-stdio; restart Claude Desktop after changing its configuration.

Tools and capabilities

Available tool groups include:

  • Projects: list visible projects and retrieve project information.
  • Issues: get issues, search with JQL, create and update issues, and create subtasks.
  • Comments: add comments with optional group or role visibility.
  • Metadata: inspect create fields, issue types, users, priorities, statuses, and custom fields.
  • Personal work: list issues assigned to the current user.

Create metadata is useful before creating an issue because it reports available fields, including custom fields, and their permitted values. Search and issue retrieval support pagination or optional field and expansion parameters where exposed by the tool.

The repository includes development commands for building, type checking, linting, formatting, testing, coverage, and running the MCP Inspector. Development and test modes can log connection failures without stopping the server.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Jira Stdio

mcp-jira-stdio is an MCP server that connects MCP clients to Jira through its API. Its main tools retrieve, search, create, and update issues; create subtasks; add comments; list projects; inspect metadata; find users; and retrieve issues assigned to the current user.

Install it with npm globally or locally, then configure an MCP client to run `mcp-jira-stdio` or `npx mcp-jira-stdio`. Provide `JIRA_BASE_URL`, `JIRA_EMAIL`, and `JIRA_API_TOKEN` in the client environment.

It requires `JIRA_BASE_URL`, `JIRA_EMAIL`, and `JIRA_API_TOKEN` for Jira tool calls. The server can start without them, but operations that contact Jira will fail with an authentication error until the values are set.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Jira Stdio AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-jira-stdio?style=directory)](https://allmcps.com/mcp/mcp-jira-stdio)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-jira-stdio"><img src="https://allmcps.com/api/badge/mcp-jira-stdio?style=directory" alt="MCP Jira Stdio on AllMCPs" /></a>