MCP Server Atlassian Jira logo

MCP Server Atlassian Jira

by aashari

Connects AI assistants to Jira Cloud for reading, searching, creating, updating, and deleting Jira resources.

Install MCP Server Atlassian Jira

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": {
    "aashari-mcp-server-atlassian-jira": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira"
      ],
      "env": {
        "ATLASSIAN_SITE_NAME": "YOUR_VALUE_HERE",
        "ATLASSIAN_USER_EMAIL": "YOUR_VALUE_HERE",
        "ATLASSIAN_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.

Automated check passed— started and listed 5 tools correctly (1mo ago).

Overview

aashari/mcp-server-atlassian-jira MCP server exposes Jira Cloud's REST API through five MCP tools for GET, POST, PUT, PATCH, and DELETE requests. It uses Atlassian credentials from environment variables and returns TOON by default, with JSON and JMESPath filtering available. Use it when an AI assistant needs to inspect projects and issues, search with JQL, manage comments or worklogs, or perform other Jira API operations. The server is suitable for Claude Desktop, Cursor, and other MCP-compatible clients that support STDIO configuration.

Use cases

  • Search Jira issues with JQL
  • Inspect project and issue details
  • Create issues and add comments
  • Update fields, worklogs, or transitions
  • Delete Jira resources

Key features

  • Generic GET, POST, PUT, PATCH, and DELETE Jira tools
  • JQL issue search through Jira REST API v3
  • TOON or JSON response output
  • JMESPath filtering with jq
  • Automatic truncation of large responses
  • CLI and STDIO MCP configuration

Tools5

What MCP Server Atlassian Jira lets your agent do. Expand a tool for its parameters.

Verified live~3.1k tokens of context

Security & health

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

ActiveLast checked Today

Recent health check succeeded.

15/15 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @aashari/mcp-server-atlassian-jira (npm)

Adoption & maintenance

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

GitHub stars78Stargazers on the source repository.
npm downloads47kPackage downloads in the last 30 days.
Last commit7mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed5Callable tools this server registers over MCP.
Directory activity11 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server Atlassian Jira works

What aashari/mcp-server-atlassian-jira MCP server does

The aashari/mcp-server-atlassian-jira MCP server connects an MCP client to Jira Cloud's REST API v3. Rather than exposing a separate tool for every Jira resource, it provides five generic operations: jira_get, jira_post, jira_put, jira_patch, and jira_delete. Each operation accepts a Jira API path and the relevant query parameters or request body, allowing an agent to work with endpoints beyond the common examples.

Typical read operations include listing or inspecting projects, retrieving issues, searching with JQL, reading comments and worklogs, checking transitions, and looking up users, statuses, issue types, and priorities. Write operations can create issues, add comments or worklogs, transition issues, update resources, and delete issues or related records when the authenticated Jira account has permission.

How it works

The aashari/mcp-server-atlassian-jira MCP server sends requests to Jira Cloud using the configured site name, user email, and API token. MCP clients invoke the generic tools, while the tool arguments describe the Jira REST path, query parameters, body, output format, and optional jq expression.

Responses use TOON by default. JSON can be selected with outputFormat: "json". Every tool supports optional JMESPath-style filtering through the jq parameter. Filtering is important for large Jira responses because it limits the fields returned to the client. Query parameters such as maxResults can also restrict result counts. A practical workflow is to retrieve one item without a filter to inspect the schema, then request only the needed fields in later calls.

Large responses over approximately 40,000 characters are truncated. The complete raw response is written to a timestamped file under /tmp/mcp/mcp-server-atlassian-jira/, and the response includes guidance for narrowing the request.

Setup and configuration

Install or run the package with npx and provide these environment variables:

  • ATLASSIAN_SITE_NAME: the site portion of the Jira Cloud hostname, such as the value used in company.atlassian.net.
  • ATLASSIAN_USER_EMAIL: the Atlassian account email.
  • ATLASSIAN_API_TOKEN: an Atlassian API token.

For Claude Desktop, configure the MCP server with the npx command and pass the variables in the server's env object. Its environment block can be keyed as jira, atlassian-jira, @aashari/mcp-server-atlassian-jira, or mcp-server-atlassian-jira.

Tools and capabilities

The aashari/mcp-server-atlassian-jira MCP server supports these operations:

  • jira_get reads any Jira API endpoint.
  • jira_post creates resources, including issues, comments, and worklogs.
  • jira_put replaces a resource and should be treated as a full update.
  • jira_patch changes only specified fields for partial updates.
  • jira_delete removes resources such as issues, comments, worklogs, attachments, and watchers where the endpoint and permissions allow it.

Attachment creation requires multipart form data and is described as complex, so the README recommends using the Jira UI for attachments.

Limitations and notes

The server does not bypass Jira permissions or API behavior; the connected account must be authorized for the requested operation. PUT requests replace the full resource, while PATCH is intended for partial changes. Unfiltered responses can contain substantial metadata and increase token usage, so use jq and maxResults for routine requests.

Reviews

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

Frequently Asked Questions about MCP Server Atlassian Jira

Run it with `npx -y @aashari/mcp-server-atlassian-jira`. The package also documents global npm installation and MCP client STDIO configuration.

Set `ATLASSIAN_SITE_NAME`, `ATLASSIAN_USER_EMAIL`, and `ATLASSIAN_API_TOKEN` before running the server.

Yes. The README provides a Claude Desktop configuration using `npx`, STDIO transport, and the three Atlassian environment variables.

Call `jira_get` with the `/rest/api/3/search/jql` path and pass a JQL expression in the `jql` query parameter. Use `maxResults` and `jq` to limit the returned data.

Related MCP servers

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 Server Atlassian Jira AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aashari-mcp-server-atlassian-jira?style=directory)](https://allmcps.com/mcp/aashari-mcp-server-atlassian-jira)
HTML Embed
<a href="https://allmcps.com/mcp/aashari-mcp-server-atlassian-jira"><img src="https://allmcps.com/api/badge/aashari-mcp-server-atlassian-jira?style=directory" alt="MCP Server Atlassian Jira on AllMCPs" /></a>