atlassian-dc-mcp
Three MCP servers for Atlassian Data Center: Jira, Confluence and Bitbucket with interactive setup and protected token storage.
- 109 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Tokens give the agent access to company issues, pages and code, including writes.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/atlassian-dc-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Tokens give the agent access to company issues, pages and code, including writes.
This is third-party code. Review the repository files before installing.
What it does
The repository publishes three npm packages: `@atlassian-dc-mcp/jira`, `@atlassian-dc-mcp/confluence` and `@atlassian-dc-mcp/bitbucket`. Each connects an agent to its own Atlassian Data Center product: in Jira the agent searches, views and creates issues, in Confluence it reads and manages pages, in Bitbucket it works with repositories and code. Every package has a `setup` command: it asks for host, API base path and token, validates access with a request and stores the token in the macOS Keychain or in `~/.atlassian-dc-mcp/<product>.env` with mode 0600. After that the server starts with no environment variables.
Who it is for. Teams that run Jira, Confluence and Bitbucket on their own Data Center servers and want to connect an agent to them.
Good fit when
- An agent works through the Jira queue by JQL and prepares a summary.
- You need to find a policy page in Confluence and quote it.
- An agent inspects a Bitbucket repository and locates a file.
- One credential set has to work in Claude Code, Cursor and Claude Desktop.
Not a fit when
- You want a single Atlassian Rovo server instead of three separate packages.
- A token with broad rights must not be given to an agent.
- You need a project endorsed and supported by Atlassian itself.
Example request
Find my team open Jira issues, sort them by priority and describe the three most urgent.MCP
- Transport
- stdio
- Authentication
- API key
Environment variables
JIRA_HOSTrequired- Jira Data Center host, for example `jira.example.com`.
JIRA_API_TOKENrequired, secret- Jira personal access token.
CONFLUENCE_API_TOKENsecret- Token for the Confluence server.
BITBUCKET_API_TOKENsecret- Token for the Bitbucket server.
Limitations
The project is community-maintained and not endorsed or supported by Atlassian. It needs Node.js 18 or newer, npm 7 and a token for each product, created separately in Jira, Confluence and Bitbucket. Each product runs as its own server. A token with write rights lets the agent create issues and edit pages. On Windows the 0600 file mode does not apply, so protection depends on the user profile permissions.
How to disable. Remove the server entries with `claude mcp remove` or from client configuration. Delete tokens from the Keychain or `~/.atlassian-dc-mcp/` and revoke them in Atlassian.
FAQ
How do I connect Jira Data Center to Claude Code?
Run `claude mcp add atlassian-jira-dc -e JIRA_HOST=your-jira-host -e JIRA_API_TOKEN=your-token -- npx -y @atlassian-dc-mcp/jira`. Or run `npx @atlassian-dc-mcp/jira setup` once and no variables are needed.
Where is the token stored?
On macOS in the Keychain, on Linux in `~/.atlassian-dc-mcp/<product>.env` with mode 0600, on Windows in `%USERPROFILE%\.atlassian-dc-mcp`. Environment variables take precedence over saved values.
Can several clients share one settings file?
Yes: put the `JIRA_*`, `CONFLUENCE_*` and `BITBUCKET_*` variables in one dotenv file and point `ATLASSIAN_DC_MCP_CONFIG_FILE` at it.
Do I have to install all three servers?
No, connect only the products you need. Each package runs on its own with its own token.
Is the project endorsed by Atlassian?
No. It is a community project, not affiliated with or supported by Atlassian.
Discussion
No questions or reviews yet.
Related
MCP serversadd-mcp writes an MCP server into the configs of 25 agents with one command: Claude Code, Codex, Cursor, VS Code, Zed and more
An MCP server that graphs repository dependencies, writes docs from the graph and answers agent questions via codebase-qna
A plugin with skills for building TypeScript MCP servers and MCP apps: the agent scaffolds, edits, debugs and verifies them
SourceCraft MCP and CLI: repos and CI/CD
SourceCraft MCP Server
An MCP server, CLI tool and skill for Yandex's SourceCraft development platform: repositories, issues, pull requests, CI/CD and releases, 48 tools
MCP server that fetches the exact documentation section instead of the whole file: a heading index and byte-precise reads
MCP DevTools replaces a dozen MCP servers with one Go binary: search, page fetch, package documentation and GitHub.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| atlassian-dc-mcp (this card) | no | API key | 109 | |
| MCP Atlassian | no | key is optional | 6,116 | another project for Jira and Confluence; here three separate packages, Bitbucket among them |
| Atlassian Rovo MCP Server | yes | OAuth | 1,160 | Atlassian official cloud server; this is an unofficial set for Data Center |
README in short
A Lerna monorepo with three packages. The README covers setup for Claude Desktop and Claude Code in detail, along with configuration sources and their precedence.