Atlassian Dc Jira MCP server
MCP server for Atlassian Jira Data Center - search, view, and create issues
99 stars2.1k downloads/wk
Reviews
Write oneNobody has reviewed Atlassian Dc Jira yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Atlassian Dc Jira tools (15, 7 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
jira_createIssuewrite actionCreate a new JIRA issue in the …
jira_downloadAttachmentDownload attachment(s) from a JIRA issue in the …, by issue key (optionally filtered by filename) or by a single attachment id. Returns the file content inline (base64 or text). Useful for inspecting a file or moving it elsewhere (e.g. re-uploading to a Confluence page).…
jira_getIssueGet details of a JIRA issue by its key from the …
jira_getIssueCommentsGet comments of a JIRA issue by its key from the …
jira_getIssueDevelopmentInfoGet linked development information (pull requests, commits, or branches) shown in the Development panel of a JIRA issue in the …. Defaults to pull requests from Bitbucket.
jira_getIssueLinkTypesGet the list of available issue link types (e.g. Blocks, Relates, Duplicate) in the …. Use this to discover valid link type names before calling jira_linkIssues.
jira_getTransitionsGet available status transitions for a JIRA issue in the …. Returns a list of transitions with their IDs, names, and target statuses.
jira_linkIssueswrite actionCreate a link between two JIRA issues in the …. Direction is easy to invert vs the Jira UI: inwardIssueKey is the issue that DISPLAYS the outward phrase (e.g. 'blocks'); outwardIssueKey displays the inward phrase (e.g. 'is blocked by'). After create, GET the first issue — it must have outwardIssue = the second key. Use jira_getIssueLinkTypes for valid type names.
jira_postIssueCommentwrite actionPost a comment on a JIRA issue in the …
jira_searchIssuesSearch for JIRA issues using JQL in the …
jira_transitionIssueTransition a JIRA issue to a new status in the …. Use jira_getTransitions first to get available transition IDs.
jira_unlinkIssueswrite actionDelete an existing link between two JIRA issues in the …. Requires the issue link id (found in the 'issuelinks' field of an issue).
jira_updateIssuewrite actionUpdate an existing JIRA issue in the …
jira_updateIssueCommentwrite actionUpdate the body of an existing comment on a JIRA issue in the …. Use jira_getIssueComments to find the comment id.
jira_uploadAttachmentwrite actionUpload a local file as an attachment to a JIRA issue in the …. The file must live under the server-configured upload directory; the path is given relative to that directory.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
- Code scan1122 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 18 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the Atlassian Dc Jira repository's README, as published. We do not edit it. Read it on GitHub
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 setupThe 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.
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.comCredential 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:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
Runs npx -y @atlassian-dc-mcp/jira on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add atlassian-dc-mcp-jira -- npx -y @atlassian-dc-mcp/jira
Atlassian Dc Jira: common questions
- Is Atlassian Dc Jira MCP server safe?
- Mostly: it is graded B (83/100). Read the Atlassian Dc Jira safety report
- How do I install Atlassian Dc Jira?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Atlassian Dc Jira need an API key?
- Yes. The registry entry asks for
JIRA_API_TOKEN. - Is Atlassian Dc Jira maintained?
- The last commit was 18 days ago (2026-09-02). The latest release is v0.34.0.
- What can I use instead of Atlassian Dc Jira?
- Servers from other publishers that do the same job: Atlassian Rovo MCP Server, Jira Stdio MCP server and Jira Cloud MCP server. Compare all Atlassian Dc Jira alternatives.
Alternatives to Atlassian Dc Jira
Same job from other publishers: the closest match first, then the best rated.
- Atlassian Rovo MCP ServerConnect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.not reviewedEstablishedA
- Jira StdioMCP server for Jira Cloud — issues, search, comments, attachments, transitions.not reviewedGrowingB
- Jira CloudMCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fieldsnot reviewedGrowingB
- Atlassian ExtendedMCP server for Jira and Confluence — sprints, agile boards, attachments, versions, calendars.not reviewedGrowingB
- GitlabGitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.not reviewedWidely usedB