Skip to main content

MCP Atlassian

Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). This integration supports both Atlassian Cloud and Jira Server/Data Center deployments.

Feature Demo

Jira Demo

Confluence Demo

Confluence Demo

Compatibility

Product Deployment Type Support Status
Confluence Cloud ✅ Fully supported
Confluence Server/Data Center ✅ Supported (version 7.9+)
Jira Cloud ✅ Fully supported
Jira Server/Data Center ✅ Supported (version 8.14+)

Installation

Using uv (recommended)

On macOS:

brew install uv

When using uv, no specific installation is needed. We will use uvx to directly run mcp-atlassian.

uvx mcp-atlassian

Using PIP

Alternatively you can install mcp-atlassian via pip:

pip install mcp-atlassian

Using Docker

Clone this repository and build the Docker image:

git clone https://github.com/sooperset/mcp-atlassian.git
cd mcp-atlassian
docker build -t mcp/atlassian .

Configuration

The MCP Atlassian integration supports using either Confluence, Jira, or both services. You only need to provide the environment variables for the service(s) you want to use.

Authentication

For Atlassian Cloud (Confluence and Jira Cloud)

Generate an API token for Atlassian Cloud:

For Confluence and Jira Server/Data Center

Generate a Personal Access Token in Jira Server/Data Center (v8.14+):

  • Go to your profile (avatar) → Profile → Personal Access Tokens
  • Click Create token, name it, set expiry
  • Copy the token immediately after generation (it won't be shown again)

Usage with Claude Desktop

Note: For all configuration methods, include only the environment variables needed for your services:

  • For Confluence only (Cloud): Include CONFLUENCE_URL, CONFLUENCE_USERNAME, and CONFLUENCE_API_TOKEN
  • For Jira Cloud: Include JIRA_URL, JIRA_USERNAME, and JIRA_API_TOKEN
  • For Jira Server/Data Center: Include JIRA_URL and JIRA_PERSONAL_TOKEN
  • For multiple services: Include the variables for each service you want to use
Using uvx
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "your.email@domain.com",
        "CONFLUENCE_API_TOKEN": "your_api_token",
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your.email@domain.com",
        "JIRA_API_TOKEN": "your_api_token"
      }
    }
  }
}

For Confluence/Jira Server/Data Center:

{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "CONFLUENCE_URL": "https://confluence.your-company.com",
        "CONFLUENCE_PERSONAL_TOKEN": "your_personal_access_token",
        "JIRA_URL": "https://jira.your-company.com",
        "JIRA_PERSONAL_TOKEN": "your_personal_access_token"
      }
    }
  }
}
Using pip
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "python",
      "args": ["-m", "mcp-atlassian"],
      "env": {
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "your.email@domain.com",
        "CONFLUENCE_API_TOKEN": "your_api_token",
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your.email@domain.com",
        "JIRA_API_TOKEN": "your_api_token"
      }
    }
  }
}
Using docker

There are two ways to configure the Docker environment:

  1. Using environment variables directly in the config:
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "mcp/atlassian"],
      "env": {
        "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
        "CONFLUENCE_USERNAME": "your.email@domain.com",
        "CONFLUENCE_API_TOKEN": "your_api_token",
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your.email@domain.com",
        "JIRA_API_TOKEN": "your_api_token"
      }
    }
  }
}
  1. Using an environment file:
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "--env-file",
        "/path/to/your/.env",
        "mcp/atlassian"
      ]
    }
  }
}

The .env file should contain:

# Confluence Cloud
CONFLUENCE_URL=https://your-domain.atlassian.net/wiki  # Your Confluence cloud URL
CONFLUENCE_USERNAME=your.email@domain.com              # Your Atlassian account email
CONFLUENCE_API_TOKEN=your_api_token                    # API token for Confluence

# Confluence Server/Data Center (alternative to CONFLUENCE_USERNAME and CONFLUENCE_API_TOKEN)
# CONFLUENCE_URL=https://confluence.your-company.com        # Your Confluence Server/Data Center URL
# CONFLUENCE_PERSONAL_TOKEN=your_personal_access_token      # Personal Access Token for Confluence Server/Data Center
# CONFLUENCE_SSL_VERIFY=true                                # Set to 'false' for self-signed certificates

#
# Jira Cloud
JIRA_URL=https://your-domain.atlassian.net            # Your Jira cloud URL
JIRA_USERNAME=your.email@domain.com                   # Your Atlassian account email
JIRA_API_TOKEN=your_api_token                         # API token for Jira Cloud

# Jira Server/Data Center (alternative to JIRA_USERNAME and JIRA_API_TOKEN)
# JIRA_URL=https://jira.your-company.com              # Your Jira Server/Data Center URL
# JIRA_PERSONAL_TOKEN=your_personal_access_token      # Personal Access Token for Jira Server/Data Center
# JIRA_SSL_VERIFY=true                                # Set to 'false' for self-signed certificates

Cursor IDE Configuration

To integrate the MCP server with Cursor IDE:

image

Configure the server:

  • Open Cursor Settings
  • Navigate to Features > MCP Servers
  • Click Add new MCP server
  • Enter this configuration:
    name: mcp-atlassian
    type: command
    command: uvx mcp-atlassian --confluence-url=https://your-domain.atlassian.net/wiki --confluence-username=your.email@domain.com --confluence-token=your_api_token --jira-url=https://your-domain.atlassian.net --jira-username=your.email@domain.com --jira-token=your_api_token
    
  • After configuring, ensure you're in Agent mode in the Composer to use MCP tools

image

Using a Local Development Version

If you've cloned the repository and want to run a local version of mcp-atlassian:

Configure in Claude Desktop:

{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uv",
      "args": [
        "--directory", "/path/to/your/mcp-atlassian",
        "run", "mcp-atlassian",
        "--confluence-url=https://your-domain.atlassian.net/wiki",
        "--confluence-username=your.email@domain.com",
        "--confluence-token=your_api_token",
        "--jira-url=https://your-domain.atlassian.net",
        "--jira-username=your.email@domain.com",
        "--jira-token=your_api_token"
      ]
    }
  }
}

Resources

Note: The MCP server filters resources to only show Confluence spaces and Jira projects that the user is actively interacting with, based on their contributions and assignments.

  • confluence://{space_key}: Access Confluence spaces
  • jira://{project_key}: Access Jira projects

Available Tools

Tool Description
confluence_search Search Confluence content using CQL
confluence_get_page Get content of a specific Confluence page
confluence_get_page_children Get child pages of a specific Confluence page
confluence_get_comments Get comments for a specific Confluence page
confluence_create_page Create a new Confluence page
confluence_update_page Update an existing Confluence page
confluence_delete_page Delete an existing Confluence page
jira_get_issue Get details of a specific Jira issue
jira_search Search Jira issues using JQL
jira_get_project_issues Get all issues for a specific Jira project
jira_create_issue Create a new issue in Jira
jira_update_issue Update an existing Jira issue
jira_delete_issue Delete an existing Jira issue
jira_get_transitions Get available status transitions for a Jira issue
jira_transition_issue Transition a Jira issue to a new status
jira_add_worklog Add a worklog entry to a Jira issue
jira_get_worklog Get worklog entries for a Jira issue
jira_link_to_epic Link an issue to an Epic
jira_get_epic_issues Get all issues linked to a specific Epic

Debugging

You can use the MCP inspector to debug the server:

npx @modelcontextprotocol/inspector uvx mcp-atlassian

For development installations:

cd path/to/mcp-atlassian
npx @modelcontextprotocol/inspector uv run mcp-atlassian

View logs with:

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

Security

  • Never share API tokens
  • Keep .env files secure and private
  • See SECURITY.md for best practices

License

Licensed under MIT - see LICENSE file. This is not an official Atlassian product.

Metadata

Release files for mcp-atlassian 0.2.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-atlassian 0.2.2
File Size Uploaded
mcp_atlassian-0.2.2.tar.gz 404.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-atlassian 0.2.2
File Interpreter ABI Platform
mcp_atlassian-0.2.2-py3-none-any.whl Python 3 none any Details

Total release size: 488.6 kB

Release files / mcp_atlassian-0.2.2.tar.gz

Download URL mcp_atlassian-0.2.2.tar.gz
Size 404.6 kB
Tags Source
SHA-256 checksum
How to use checksums
2dc2fae60b7e7b865167de9bc633d2d4101a1af799e62892caceb434aad87696
BLAKE2b-256 checksum
How to use checksums
10ee92dd22e2431ed2f44c1acbef9cd4befec9cb197e64981d10d851946d4266
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.6.0

Release files / mcp_atlassian-0.2.2-py3-none-any.whl

Download URL mcp_atlassian-0.2.2-py3-none-any.whl
Size 84.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
193ea5a229781f4449d2cc24e956ed903cf8890c20b3097d33b5bfe38b8aa4ae
BLAKE2b-256 checksum
How to use checksums
c120b704569138ca3e54831e0f959b75eb6b1ec87a47350b7f35df180768a904
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.6.0

Release history Release notifications | RSS feed

0.23.1

2 release files

0.23.0

2 release files

0.22.1

2 release files

0.22.0

2 release files

0.21.1

2 release files

0.20.1

2 release files

0.20.0

2 release files

0.19.0

2 release files

0.18.1

2 release files

0.18.0

2 release files

0.17.0

2 release files

0.16.1

2 release files

0.16.0

2 release files

0.15.0

2 release files

0.14.3

2 release files

0.14.2

2 release files

0.14.1

2 release files

0.14.0

2 release files

0.13.1

2 release files

0.12.0

2 release files

0.11.9

2 release files

0.11.8

2 release files

0.11.7

2 release files

0.11.6

2 release files

0.11.5

2 release files

0.11.4

2 release files

0.11.3

2 release files

0.11.2

2 release files

0.11.1

2 release files

0.11.0

2 release files

0.10.6

2 release files

0.10.5

2 release files

0.9.0

2 release files

0.8.4

2 release files

0.8.3

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.5

2 release files

0.6.4

2 release files

0.6.3

2 release files

0.6.2

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

This release

0.2.2 This release

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page