Atlassian Data Center MCP
About
MCP servers for the Atlassian products (Bitbucket, Confluence, JIRA) of the Data Center version
Details
- Author
- b1ff
- GitHub stars
- 81
- Downloads
- 938
- Categories
- Developer Tools
Jump to
- Interactive setup CLI for each product with credential validation.
- Non-interactive mode for scripted or CI bootstrap.
- Secure token storage: macOS Keychain, Linux home file, Windows user profile.
- Multi-source configuration with clear precedence (env, shared file, home file, keychain).
- Supports both _HOST and _API_BASE_PATH environment variables.
- Configurable request timeout via ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Atlassian Data Center MCPCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Run the interactive setup subcommand for each product (e.g., npx @atlassian-dc-mcp/jira setup) to store credentials securely. Once configured, add the servers to your MCP host (Claude Desktop, Claude Code) using npx commands and environment variables like JIRA_HOST and JIRA_API_TOKEN. You can also use a shared external config file with ATLASSIAN_DC_MCP_CONFIG_FILE.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"atlassian data center mcp": {
"atlassian-dc-mcp": {
"command": "npx",
"args": [
"@atlassian-dc-mcp/jira",
"setup"
]
}
}
}
}McpServers
{
"atlassian-dc-mcp": {
"command": "npx",
"args": [
"@atlassian-dc-mcp/jira",
"setup"
]
}
}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/<product> setup --help for the full list.
| Flag | Short | Description |
|------|-------|-------------|
| --host <value> | -H | Host, e.g. jira.example.com |
| --api-base-path <value> | -b | API base path or full URL |
| --token <value> | -t | API token |
| --default-page-size <n> | -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/<product>.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.
```bash
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
