Atlassian Dc MCP Jira

Name: Atlassian Dc MCP Jira
Author: b1ff

by b1ffversion 0.43.1i★ 108iRuns on your computer

Registry nameio.github.b1ff/atlassian-dc-mcp-jira

Overview

Description from the maker (original English)

MCP server for Atlassian Jira Data Center - search, view, and create issues

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiEarly★ 108

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools
You need to fill in: JIRA_API_TOKEN

Install

Pick the AI app you use, then copy the settings.

You need

npmNode.js installed (for the npx command)

Claude DesktopClaude CodeCursorVS Code

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "atlassian-dc-jira": {
      "command": "npx",
      "args": [
        "-y",
        "@atlassian-dc-mcp/jira"
      ],
      "env": {
        "ATLASSIAN_DC_MCP_CONFIG_FILE": "your-value",
        "JIRA_HOST": "your-value",
        "JIRA_API_BASE_PATH": "your-value",
        "JIRA_API_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add atlassian-dc-jira --env ATLASSIAN_DC_MCP_CONFIG_FILE=your-value --env JIRA_HOST=your-value --env JIRA_API_BASE_PATH=your-value --env JIRA_API_TOKEN=your-value -- npx -y @atlassian-dc-mcp/jira

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "atlassian-dc-jira": {
      "command": "npx",
      "args": [
        "-y",
        "@atlassian-dc-mcp/jira"
      ],
      "env": {
        "ATLASSIAN_DC_MCP_CONFIG_FILE": "your-value",
        "JIRA_HOST": "your-value",
        "JIRA_API_BASE_PATH": "your-value",
        "JIRA_API_TOKEN": "your-value"
      }
    }
  }
}

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "atlassian-dc-jira": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@atlassian-dc-mcp/jira"
      ],
      "env": {
        "ATLASSIAN_DC_MCP_CONFIG_FILE": "your-value",
        "JIRA_HOST": "your-value",
        "JIRA_API_BASE_PATH": "your-value",
        "JIRA_API_TOKEN": "your-value"
      }
    }
  }
}

Values you fill in

ATLASSIAN_DC_MCP_CONFIG_FILE env
Absolute path to a shared dotenv-style config file. When set, values are read from this file before direct environment variable overrides are applied.
JIRA_HOST env
Jira host domain (e.g. your-instance.atlassian.net). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or JIRA_API_BASE_PATH.
JIRA_API_BASE_PATH env
Jira API base path (alternative to JIRA_HOST). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or JIRA_HOST.
JIRA_API_TOKEN secret env
Jira Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE.

Values marked secret are keys to your account. Never share them or paste them into a chat.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 5, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account b1ff, which owns the repo
✓ Pass
Still maintained
Code last changed 3 days ago
✓ Pass
Has a licence
Uses MIT
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Needs the server’s tool list first; this check starts in the next step

Compared with others in Developer toolsi

More stars than 0% of the other 13 servers in this category
Published to the registry more recently than 69% of the other 13 servers in this category
Basic checks equal to or better than 100% of the other 13 servers in this category

Compared only with servers in this prototype, not the whole registry.

Common questions

Is Atlassian Dc MCP Jira safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: JIRA_API_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 days ago, and the latest version (0.43.1) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 2 days ago

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 14 days ago

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Atlassian Data Center MCP

Note: This is a community-maintained project and is not affiliated with, endorsed by, or supported by Atlassian.

Use at your own discretion.

This project provides a Model Context Protocol (MCP) integration for Atlassian Data Center products, including Jira, Confluence, and Bitbucket.

Quick Setup

Each package ships an interactive setup subcommand that stores your credentials in the most secure place available on your OS. Run it once per product:

npx @atlassian-dc-mcp/jira setup

npx @atlassian-dc-mcp/confluence setup npx @atlassian-dc-mcp/bitbucket setup

The setup CLI prompts for host, API base path, default page size, and API token. Before saving, it validates obvious input mistakes and performs a timed authenticated request to the selected Atlassian product, so a bad host, base path, or token is caught during setup.

CLI flags and non-interactive mode

Setup accepts flags so you can prefill values or skip prompts entirely (useful for scripted bootstrap, CI, or remote sessions). Run npx @atlassian-dc-mcp/ setup --help for the full list.

Flag	Short	Description
`--host`	`-H`	Host, e.g. `jira.example.com`
`--api-base-path`	`-b`	API base path or full URL
`--token`	`-t`	API token
`--default-page-size`	`-s`	Default page size (positive integer)
`--non-interactive`	`-n`	Skip prompts; fail if a required value cannot be resolved
`--help`	`-h`	Show usage and exit

In interactive mode, any flag you pass prefills its prompt (so e.g. --host skips the host prompt but still asks for the rest). In --non-interactive mode, setup resolves anything missing from existing configuration (process env, ~/.atlassian-dc-mcp/ .env, or macOS Keychain) and exits non-zero if a host (or full-URL --api-base-path) and token cannot be found. An existing token is reused when --token is omitted.

# Scripted, no prompts, write everything from flags

npx @atlassian-dc-mcp/jira setup --non-interactive \ --host jira.example.com \ --token "$JIRA_TOKEN"

Re-validate the existing token without re-entering it

npx @atlassian-dc-mcp/jira setup --non-interactive --host jira.example.com

Credential validation behaves differently between modes: interactive mode offers retry/save-anyway prompts on failure, while --non-interactive exits with code 1 on the first validation failure so it can be used as a CI gate.

Token storage:

macOS — written to the login Keychain via /usr/bin/security (service atlassian-dc-mcp, account -token).
Linux — written to ~/.atlassian-dc-mcp/ .env with POSIX mode 0600 (read/write for your user only; other local user accounts cannot read it).
Windows — written to %USERPROFILE%\.atlassian-dc-mcp\ .env. Node passes the mode bits but Windows ignores them, so the file inherits the ACL of your user profile directory — typically readable only by your user, SYSTEM, and Administrators.

Non-secret fields (host, API base path, default page size) are always written to the home file — ~/.atlassian-dc-mcp/ .env on macOS/Linux, %USERPROFILE%\.atlassian-dc-mcp\ .env on Windows. After a successful Keychain write, the token line is cleared from the home file so there is never a second copy in a less-secure place.

Once setup has run, the MCP servers can boot with no environment variables at all:

"mcpServers": { "atlassian-jira-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/jira"] }, "atlassian-confluence-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/confluence"] }, "atlassian-bitbucket-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/bitbucket"] } } }

You can still pass credentials via environment variables or ATLASSIAN_DC_MCP_CONFIG_FILE as shown in the sections below — they take precedence over values saved by setup.

Configuration Sources & Precedence

At startup, each MCP server resolves each config key by walking sources in this order and taking the first non-empty value:

Priority	Source	Reads	Written by setup
100	`process.env` (`JIRA_`, `CONFLUENCE_`, `BITBUCKET_*`)	all keys	—
80	env file — `ATLASSIAN_DC_MCP_CONFIG_FILE` or `./.env`	all keys	—
60	home file — `~/.atlassian-dc-mcp/ .env` on macOS/Linux, `%USERPROFILE%\.atlassian-dc-mcp\ .env` on Windows (mode `0600` on POSIX; Windows inherits the user-profile ACL)	all keys	host, apiBasePath, defaultPageSize (always); token (non-darwin or keychain fallback)
40	macOS Keychain — service `atlassian-dc-mcp`, account `-token`	token only	token (darwin only)

Notes:

Process env wins over everything, so you can always override a stored credential for one session.
ATLASSIAN_DC_MCP_CONFIG_FILE must be an absolute path; if set and missing, the server fails fast.
Keychain reads are cached at init (one execFileSync per product-token), so tool calls never shell out.
If a higher-priority source shadows the value setup is about to save, setup prints a warning naming the env var so you can unset it.
Atlassian API requests time out after 30 seconds by default. Set ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS to a positive millisecond value to override it.

Claude Desktop Configuration

Official Anthropic quick start guide

To use these MCP connectors with Claude Desktop, add the following to your Claude Desktop configuration.

Set *_HOST variables only to domain + port without protocol (e.g., your-instance.atlassian.net). The https protocol is assumed.

Alternatively, you can use *_API_BASE_PATH variables instead of *_HOST to specify the complete API base URL including protocol (e.g., https://your-instance.atlassian.net/rest). Note that the /api/latest/ part is static and added automatically in the code, so you don't need to include it in the *_API_BASE_PATH values.

You can leave only the services you need in the configuration.

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\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" } }, "atlassian-confluence-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/confluence"], "env": { "CONFLUENCE_HOST": "your-confluence-host", "CONFLUENCE_API_TOKEN": "your-token" } }, "atlassian-bitbucket-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/bitbucket"], "env": { "BITBUCKET_HOST": "your-bitbucket-host", "BITBUCKET_API_TOKEN": "your-token" } } } }

You can also use the alternative API base path configuration:

"mcpServers": { "atlassian-jira-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/jira"], "env": { "JIRA_API_BASE_PATH": "https://your-jira-host/rest", "JIRA_API_TOKEN": "your-token" } }, "atlassian-confluence-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/confluence"], "env": { "CONFLUENCE_API_BASE_PATH": "https://your-confluence-host/rest", "CONFLUENCE_API_TOKEN": "your-token" } }, "atlassian-bitbucket-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/bitbucket"], "env": { "BITBUCKET_API_BASE_PATH": "https://your-bitbucket-host/rest", "BITBUCKET_API_TOKEN": "your-token" } } } }

Shared External Config File

If you want multiple MCP hosts or tools on one machine to reuse the same Atlassian credentials, put the existing JIRA_*, CONFLUENCE_*, and BITBUCKET_* variables into one dotenv-style file and point each MCP server at it with ATLASSIAN_DC_MCP_CONFIG_FILE.

The path must be absolute. Direct environment variables still override values from the shared file.

Example shared file:

JIRA_HOST=your-jira-host

JIRA_API_TOKEN=your-jira-token JIRA_DEFAULT_PAGE_SIZE=50

CONFLUENCE_HOST=your-confluence-host CONFLUENCE_API_TOKEN=your-confluence-token

BITBUCKET_HOST=your-bitbucket-host BITBUCKET_API_TOKEN=your-bitbucket-token BITBUCKET_DEFAULT_PAGE_SIZE=50

Claude Desktop example using one shared file:

"mcpServers": { "atlassian-jira-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/jira"], "env": { "ATLASSIAN_DC_MCP_CONFIG_FILE": "/Users/your-user/.config/atlassian-dc-mcp.env" } }, "atlassian-confluence-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/confluence"], "env": { "ATLASSIAN_DC_MCP_CONFIG_FILE": "/Users/your-user/.config/atlassian-dc-mcp.env" } }, "atlassian-bitbucket-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/bitbucket"], "env": { "ATLASSIAN_DC_MCP_CONFIG_FILE": "/Users/your-user/.config/atlassian-dc-mcp.env" } } } }

Windows example path:

"mcpServers": { "atlassian-jira-dc": { "command": "npx", "args": ["-y", "@atlassian-dc-mcp/jira"], "env": { "ATLASSIAN_DC_MCP_CONFIG_FILE": "C:\\\\Users\\\\your-user\\\\AppData\\\\Roaming\\\\atlassian-dc-mcp.env" } } } }

Claude Code CLI Configuration

To use these MCP connectors with Claude Code, add MCP servers using the claude mcp add command.

You can add servers at the project scope (stored in .mcp.json) or user scope (-s user). Adjust the scope and included services to your needs.

# Jira

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

Confluence

claude mcp add atlassian-confluence-dc \ -e CONFLUENCE_HOST=your-confluence-host \ -e CONFLUENCE_API_TOKEN=your-token \ -- npx -y @atlassian-dc-mcp/confluence

Bitbucket

claude mcp add atlassian-bitbucket-dc \ -e BITBUCKET_HOST=your-bitbucket-host \ -e BITBUCKET_API_TOKEN=your-token \ -- npx -y @atlassian-dc-mcp/bitbucket

You can also use *_API_BASE_PATH instead of *_HOST (same as the Claude Desktop examples above):

claude mcp add atlassian-jira-dc \

-e JIRA_API_BASE_PATH=https://your-jira-host/rest \ -e JIRA_API_TOKEN=your-token \ -- npx -y @atlassian-dc-mcp/jira

To add servers at user scope (available across all projects):

claude mcp add -s user atlassian-jira-dc \

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

To use the shared config file instead of passing credentials inline:

claude mcp add atlassian-jira-dc \

-e ATLASSIAN_DC_MCP_CONFIG_FILE=/Users/your-user/.config/atlassian-dc-mcp.env \ -- npx -y @atlassian-dc-mcp/jira

Windows PowerShell example:

claude mcp add atlassian-jira-dc `

-e ATLASSIAN_DC_MCP_CONFIG_FILE=C:\Users\your-user\AppData\Roaming\atlassian-dc-mcp.env ` -- npx -y @atlassian-dc-mcp/jira

Generating API Tokens

For Data Center installations, you'll need to generate Personal Access Tokens (PAT) for each service:

Jira Data Center

Log in to your Jira instance
Go to Profile > Personal Access Tokens
Click "Create token"
Give it a meaningful name and set appropriate permissions
Copy the generated token immediately (it won't be shown again)

Confluence Data C

Only the beginning is shown; read the rest in the repo