Atlassian Dc MCP Confluence

Atlassian Data Center MCP

Community project — not affiliated with, endorsed by, or supported by Atlassian. Use at your own discretion.

Model Context Protocol (MCP) servers that connect Claude Desktop, Claude Code, Cursor, and any other MCP-compatible AI assistant to self-hosted Atlassian Data Center (formerly *Server*) instances: Jira, Confluence, and Bitbucket.

Search and manage Jira issues, read and edit Confluence pages, review Bitbucket pull requests — from your AI assistant, with credentials stored in your OS keychain instead of pasted into a client config.

Each product is a separate package — install only the ones you need.

Contents

• Capabilities
• Quick start
• Connecting a client — Claude Desktop · Claude Code · Cursor & others
• Authentication & tokens
• Configuration reference
• Features
• Development
• License

Capabilities

Each server exposes MCP tools (actions the assistant can call), resources (readable context endpoints), and prompts (ready-made workflows). Tools are grouped by domain and follow the naming pattern _verb_noun (e.g. jira_search_issues, bitbucket_get_pull_request).

Jira — 288 tools

Confluence — 115 tools

Bitbucket — 120 tools

Every tool carries MCP annotations (read-only vs. destructive hints), and argument completions are provided for common identifiers (project keys, board IDs, repository slugs) so compatible clients can autocomplete them.

Quick start

Each package ships an interactive setup command that stores credentials in the most secure place your OS offers (macOS Keychain, or a 0600 file elsewhere). Run it once per product:

npx jira-datacenter-mcp setup

npx confluence-datacenter-mcp setup npx bitbucket-datacenter-mcp setup

Setup prompts for host, API base path, default page size, and API token, then makes a live authenticated request to verify everything before saving — a wrong host or token is caught immediately. Leave the token blank to configure anonymous (unauthenticated) access on instances that allow it.

After setup, the server boots with zero environment variables — see Connecting a client.

Prefer explicit config? You can skip setup entirely and pass credentials via environment variables or a shared config file instead. See the Configuration reference.

Scripted / non-interactive setup

Setup accepts flags for CI or remote bootstrap (--help for the full list):

# Fully scripted

npx jira-datacenter-mcp setup --non-interactive --host jira.example.com --token "$JIRA_TOKEN"

Re-validate an already-stored token without re-entering it

npx jira-datacenter-mcp setup --non-interactive --host jira.example.com

In --non-interactive mode, missing values are resolved from existing configuration and the command exits 1 on the first validation failure — usable as a CI gate.

Connecting a client

Once setup has stored your credentials, the env block can be empty. The examples below pass credentials inline for clarity; drop the env entries if you ran setup.

Set *_HOST to a domain (+ optional port) without a protocol — https:// is assumed. To point at a non-standard path or force http://, use *_API_BASE_PATH with a full URL instead (the product-specific API suffix is appended automatically — don't include it).

Claude Desktop

Config file: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) · %APPDATA%\Claude\claude_desktop_config.json (Windows). Keep only the servers you need.

{

"mcpServers": { "atlassian-jira-dc": { "command": "npx", "args": ["-y", "jira-datacenter-mcp"], "env": { "JIRA_HOST": "jira.example.com", "JIRA_API_TOKEN": "your-token" } }, "atlassian-confluence-dc": { "command": "npx", "args": ["-y", "confluence-datacenter-mcp"], "env": { "CONFLUENCE_HOST": "confluence.example.com", "CONFLUENCE_API_TOKEN": "your-token" } }, "atlassian-bitbucket-dc": { "command": "npx", "args": ["-y", "bitbucket-datacenter-mcp"], "env": { "BITBUCKET_HOST": "bitbucket.example.com", "BITBUCKET_API_TOKEN": "your-token" } } } }

After running setup, this collapses to:

{

"mcpServers": { "atlassian-jira-dc": { "command": "npx", "args": ["-y", "jira-datacenter-mcp"] } } }

Claude Code

# Project scope (writes .mcp.json); add -s user for all projects

claude mcp add atlassian-jira-dc \ -e JIRA_HOST=jira.example.com \ -e JIRA_API_TOKEN=your-token \ -- npx -y jira-datacenter-mcp

Swap -e JIRA_HOST=… for -e JIRA_API_BASE_PATH=https://jira.example.com/rest, or drop the -e flags entirely if you ran setup.

Cursor & other MCP clients

Any stdio MCP client works. Point it at the command npx -y -datacenter-mcp and supply credentials through its env mechanism (or rely on setup). For remote/multi-client hosting, use the HTTP transport.

Authentication & tokens

Three modes, resolved per request:

• Personal Access Token (recommended) — set *_API_TOKEN. Sent as Authorization: Bearer .
• Basic auth — set *_USERNAME + *_PASSWORD (for older instances without PATs). Takes precedence over a token if both are configured.
• Anonymous — set neither. No Authorization header is sent; works on instances that allow unauthenticated reads.

Generating a Personal Access Token

Give the token the minimum permissions it needs and copy it immediately — it is shown only once.

Configuration reference

Per-product variables

Each product reads its own prefix (JIRA_*, CONFLUENCE_*, BITBUCKET_*):

¹ Provide one of *_HOST or *_API_BASE_PATH. The API suffix is appended for you and must not be included: Jira /rest (+ /api/2), Confluence /rest/api, Bitbucket /rest (+ /api/latest).

Global variables

| ATLASSIAN_DC_MCP_MAX_RESPONSE_CHARS | 100000 | Cap on a tool result's