Atlassian Dc MCP Jira

Community

MCP server for Atlassian Jira Data Center

How to install ↓ Compare GitHub source repository ↗

Category: Collaboration #11 of 55
Stars: ★ 103 Popular
Transport: stdio (local process)
Runtime: Node.js 18+
Credentials: API key / credential required
License: MIT
Last commit: 2 days ago

60FMRS · C

A functional MCP server for integrating Jira Data Center with AI assistants. It provides clear configuration guidelines and secure credential storage. However, it is not official, and the tool names are not explicitly documented in the source.

Strongest · Security and permissions 15/20 Weakest · Maintenance 8/20

Reliability

9/20

Security and permissions

15/20

Maintenance

8/20

Documentation

14/20

Setup experience

14/20

Why each score

Reliability 9/20: The manifest is well-formed and describes stdio transport plus JIRA_* env vars; README shows an npm package and config precedence. However, no source, tests, or CI workflows were supplied, so the MCP init handshake, tool-list accuracy, and error paths cannot be verified. Per the 0-20 anchor, the happy path is plausible but tests/edge cases are thin; missing evidence lowers the score to 9.
Security and permissions 15/20: Good design-level practices: macOS Keychain for tokens, 0600 on Linux, token cleared from home file after Keychain write, documented precedence, no real tokens in examples; tools are limited to search/view/create with no destructive defaults. Deductions: source could not verify least privilege or data flow, create has no explicit confirmation mechanism, and shared config-file boundaries are user-controlled; 15 is below 20 due to unverifiable claims.
Maintenance 8/20: Repository is not archived, MIT licensed, version 0.9.0, with a detailed README suggesting community maintenance. However, commit/release dates, dependency-update history, and security-response channel are absent; 3 open issues cannot confirm responsiveness. Evidence is insufficient for a higher score, so 8.
Documentation 14/20: README is well-layered: quick setup, CLI flags, config precedence, platform differences, Claude Desktop/Code examples, and token generation. Missing per-tool parameter documentation, a troubleshooting section, and mostly lacks limits/cost discussion; documentation quality is good but not full, so 14.
Setup experience 14/20: Install path is clear: Node 18+, one `npx @atlassian-dc-mcp/jira setup` command, then boot with no env vars; config examples for Claude Desktop/Code and platform notes are provided. Static calibration caps setup at 15 without real CI and committed tests; those are absent, so 14.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

Organizations using Atlassian Jira Data Center
Teams that want to manage Jira issues via AI assistants
Users needing on-premise or private integration with Jira

Not for

Users of Jira Cloud (non-Data Center)
Those requiring official support or warranty
Users without a Jira Data Center instance or API token

Required permissions

Requires a Jira Personal Access Token (PAT)
Permissions depend on token scopes configured in Jira
Typically needs read permissions for viewing issues and write permissions for creating

Risks and side effects

Token could be leaked if stored in plain text config files
Community-maintained project may lack timely security updates
Overprivileged PATs could pose risks to the Jira instance

Setup

Before you start

Runtime：Node.js 18+

JIRA_API_TOKEN optionalsecret Jira Data Center Personal Access Token, generated under Profile > Personal Access Tokens in your instance; can also be stored interactively via npx @atlassian-dc-mcp/jira setup.

Other optional settings (3)

ATLASSIAN_DC_MCP_CONFIG_FILE optional Optional; absolute path to a shared dotenv-style config file. The server fails fast if set but missing.

JIRA_HOST optional Jira host domain (e.g. your-instance.atlassian.net) without protocol; alternative to JIRA_API_BASE_PATH.

JIRA_API_BASE_PATH optional Full API base URL (e.g. https://your-instance.atlassian.net/rest); can be used instead of JIRA_HOST.

Ensure Node.js 18+ and npm 7+ are installed.
Run the quick setup: npx @atlassian-dc-mcp/jira setup which will prompt for host, API base path, and token, and validate them before saving.
Alternatively, configure environment variables: set JIRA_HOST (or JIRA_API_BASE_PATH) and JIRA_API_TOKEN.
Add the server to your MCP client configuration as shown in the README.
Optionally, use a shared config file via ATLASSIAN_DC_MCP_CONFIG_FILE.

claude_desktop_config.json

{
  "mcpServers": {
    "atlassian-jira-dc": {
      "command": "npx",
      "args": [
        "-y",
        "@atlassian-dc-mcp/jira"
      ],
      "env": {
        "JIRA_HOST": "your-jira-host",
        "JIRA_API_TOKEN": "your-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": {
    "atlassian-jira-dc": {
      "command": "npx",
      "args": [
        "-y",
        "@atlassian-dc-mcp/jira"
      ],
      "env": {
        "JIRA_HOST": "your-jira-host",
        "JIRA_API_TOKEN": "your-token"
      }
    }
  }
}

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

Terminal

claude mcp add atlassian-jira-dc -e JIRA_HOST=your-jira-host -e JIRA_API_TOKEN=your-token -- npx -y @atlassian-dc-mcp/jira

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

Generate and validate client config

Check that it works

Add the server to Claude Desktop and restart the client; the Jira search/view/create issue tools should appear in the tool list, and asking it to search a keyword should prove the connection.

Troubleshooting

Verify that `JIRA_HOST` or `JIRA_API_BASE_PATH` are set correctly without protocol or API path suffixes
Test token validity using `npx @atlassian-dc-mcp/jira setup --non-interactive`
If using a shared config file, ensure the path is absolute and the file exists
Check network connectivity to the Jira instance

Things to try

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

Search our Jira instance for all unresolved issues labeled bug
Show me the details and comments of issue JIRA-123
Create a new issue in project JIRA titled "Fix login timeout" with type Bug
List all open issues assigned to me

Use cases

Search for Jira issues

View issue details

Create new issues

Supported clients

Claude Desktop

Claude Code

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

Overview

This is a community-maintained MCP server for connecting to an Atlassian Jira Data Center instance. It allows search, view, and create issues. Authentication uses Personal Access Tokens (PAT). It is designed for self-hosted Jira Data Center environments. Note: This project is not affiliated with or endorsed by Atlassian.

Similar servers

Atlassian Rovo MCP Server 66 · C

Securely connect Atlassian Cloud to AI tools.

★ 1.1k Compare with this →

Notion MCP Server 64 · C

Official Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.

★ 4.7k · Tools 9 Compare with this →

WhatsApp Channel for Claude Code 64 · C

Drive your Claude Code session straight from WhatsApp

★ 104 · Tools 10 Compare with this →

Anytype MCP Server 64 · C

Official MCP server that lets AI assistants manage your encrypted Anytype wiki in natural language.

★ 532 Compare with this →

Compare with other MCP servers

More servers from this repository

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