Atlassian Jira MCP Server

Community

Connect AI to Your Jira Projects

How to install ↓ Compare GitHub source repository ↗

Category: Other
Stars: ★ 77 Popular
Transport: stdio (local process)
Runtime: Node.js 18+
Credentials: API key / credential required
Last commit: 7 months ago ⚠
Tools: 5

40FMRS · D

This MCP server provides comprehensive access to Jira Cloud through generic HTTP tools covering all REST API v3 endpoints. Its TOON format and JMESPath filtering enhance AI interaction efficiency. However, it only supports cloud version and requires users to have some API knowledge.

Strongest · Documentation 12/20 Weakest · Reliability 6/20

Reliability

6/20

Security and permissions

6/20

Maintenance

8/20

Documentation

12/20

Setup experience

8/20

Why each score

Reliability 6/20: The server claims to provide five generic tools (jira_get, jira_post, etc.), but the README provides no evidence of tests or CI configuration. It states use of MCP SDK v1.23.0 and Zod v4, but no source code or lockfile to verify. Thus, the happy path is plausible but untested for key paths, error handling and edge cases are thin. Static review caps at 6 - below 10 because no tests or CI evidence.
Security and permissions 6/20: The server uses user-provided API tokens via environment variables, no hardcoded credentials. However, the tool design allows arbitrary Jira API calls, including deletes (`jira_delete`), without confirmation or scoping. While data goes to Atlassian only, the least privilege is not respected. No malicious behavior found in static review, but lack of source and tests leaves security posture weak. Score 6.
Maintenance 8/20: Repository shows recent version (3.2.1), updates dependencies, and has published npm packages. However, no license or security response channel. Open issues exist but response status unknown. Overall active but governance/license gaps, so 8.
Documentation 12/20: README is extensive with install, auth, tool descriptions, examples, troubleshooting, and FAQ. It explains output format and truncation. However, it lacks detailed tool parameters and version compatibility, and no verifiable technical evidence (source/lockfile). Docs are usable but with hidden assumptions, so 12.
Setup experience 8/20: Setup is simple: set environment variables and use npx or npm install. Provides config example for Claude Desktop. Requires Node.js 18+ which is reasonable. No evidence of verification steps or cross-platform testing, and due to missing CI/tests, setup may be fragile. Score 8.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

Developers needing quick access to issue details and development context
Project managers tracking progress, priorities, and team assignments
Scrum masters managing sprints and workflow states
Team leads monitoring project health and issue resolution
QA engineers tracking bugs and testing status
Anyone wanting to interact with Jira using natural language

Not for

Users requiring Jira Server or Data Center (on-premise) support – only Jira Cloud is supported
Legacy workflows expecting predefined dedicated tools (like jira_ls_projects) – v3 migrated to generic HTTP tools
Users who don't have a Jira API token

Required permissions

Requires Atlassian account with appropriate Jira permissions for the projects you want to query
Requires a valid Atlassian API token
The server runs locally, using your own credentials

Risks and side effects

API token leakage could lead to unauthorized access – handle with care
Generic tools may expose more data than intended; use cautiously
API endpoints may change, potentially breaking the tool
Large responses are truncated automatically, with raw data saved locally to /tmp/mcp

Setup

Before you start

Runtime：Node.js 18+

ATLASSIAN_SITE_NAME required Your Jira site name — the part before .atlassian.net in your Jira URL.

ATLASSIAN_USER_EMAIL required The email address of your Atlassian account.

ATLASSIAN_API_TOKEN requiredsecret An API token created at https://id.atlassian.com/manage-profile/security/api-tokens; copy it immediately when generated.

Create an API token at Atlassian API Tokens page and copy it.
Set environment variables: ATLASSIAN_SITE_NAME (e.g., your-company), ATLASSIAN_USER_EMAIL (your email), ATLASSIAN_API_TOKEN (the token).
For Claude Desktop, add the configuration to ~/.claude/claude_desktop_config.json and restart Claude.
Alternatively, install globally via npm and configure any MCP-capable AI assistant.

claude_desktop_config.json

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira"
      ],
      "env": {
        "ATLASSIAN_SITE_NAME": "your-company",
        "ATLASSIAN_USER_EMAIL": "[email protected]",
        "ATLASSIAN_API_TOKEN": "your_api_token"
      }
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "jira": {
      "command": "npx",
      "args": [
        "-y",
        "@aashari/mcp-server-atlassian-jira"
      ],
      "env": {
        "ATLASSIAN_SITE_NAME": "your-company",
        "ATLASSIAN_USER_EMAIL": "[email protected]",
        "ATLASSIAN_API_TOKEN": "your_api_token"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add jira -e ATLASSIAN_SITE_NAME=your-company -e [email protected] -e ATLASSIAN_API_TOKEN=your_api_token -- npx -y @aashari/mcp-server-atlassian-jira

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the config and restarting Claude Desktop, the jira_get, jira_post, jira_put, jira_patch and jira_delete tools should appear in the client's tool list; you can also verify credentials with npx -y @aashari/mcp-server-atlassian-jira get --path "/rest/api/3/myself".

Troubleshooting

Authentication failed or 403: Check if the API token is valid and site name format is correct (e.g., mycompany vs mycompany.atlassian.net)
Resource not found or 404: Check case sensitivity of API paths, use project keys instead of names
No results found: Try broader criteria, or validate JQL in Jira's advanced search first
Claude Desktop integration issues: Restart Claude, verify config file location

Things to try

Once connected, you can ask your AI assistant things like:

List all projects I have access to
Show me details about issue PROJ-123 including comments
Add a comment to PROJ-456: 'Code review completed, ready for testing'
Find all high priority issues in the DEV project that are in progress

Tools 5

jira_get read-only

Send GET requests to any Jira API endpoint to read data.

jira_post writes

Send POST requests to any endpoint to create resources.

jira_put writes

Send PUT requests to any endpoint to replace resources fully.

jira_patch writes

Send PATCH requests to any endpoint to partially update resources.

jira_delete destructive

Send DELETE requests to any endpoint to remove resources.

Use cases

List all accessible projects

Search issues with JQL, e.g., 'high priority issues in DEV project'

Get details of a specific issue including comments

Add comments to an issue

Search across projects for bugs

Create or update issues

Track worklogs and status transitions

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

This MCP server enables AI assistants (such as Claude, Cursor AI) to interact with Atlassian Jira. It exposes any Jira REST API v3 endpoint through five generic tools (jira_get, jira_post, jira_put, jira_patch, jira_delete) for listing projects, searching issues (JQL), managing comments, work logs, and more. By default, it uses TOON output format to reduce token usage by 30-60% and supports JMESPath filtering.

Similar servers

DuckDuckGo Search MCP Server 74 · B

MCP server providing web search and content fetching via DuckDuckGo

★ 1.5k · Tools 2 Compare with this →

Basic Memory 72 · B

Your AI never forgets again.

★ 4.1k · Tools 21 Compare with this →

Telegram MCP Server 70 · B

Telegram MCP server powered by Telethon to let MCP clients read chats, manage groups, and send/modify messages, media, contacts, and settings.

★ 1.8k · Tools 76 Compare with this →

Hostinger API MCP Server 70 · B

Official MCP server for Hostinger API.

★ 160 · Tools 100 Compare with this →

Compare with other MCP servers

Source revision aab8b7f2cc38 Data synced 2026-10-12 Read the FMRS scoring method