mcp-atlassian 0.1.16

The Model Context Protocol (MCP) Atlassian integration is an open-source implementation that bridges Atlassian products (Jira and Confluence) with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Atlassian tools while maintaining data privacy and security. Key features include:

pip install mcp-atlassian==0.1.16

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

Demo

Compatibility

Product	Deployment Type	Support Status
Confluence	Cloud	✅ Fully supported
Confluence	Server/Data Center	❌ Not yet supported
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

Installing via Smithery

To install Atlassian Integration for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install mcp-atlassian --client claude

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)

Get API tokens from: https://id.atlassian.com/manage-profile/security/api-tokens

For Jira Server/Data Center

Generate a Personal Access Token in your Jira Server/Data Center (version 8.14 or later):
- Navigate to your profile by clicking on your avatar in the top right corner
- Select Profile → Personal Access Tokens (Alternative path in some versions: Account Settings → Security → Personal Access Tokens)
- Click Create token
- Give your token a meaningful name (e.g., "MCP Integration")
- Set an expiry date (or choose "Never" if permitted by your organization)
- Copy the generated token immediately (you won't be able to see it 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 Jira Server/Data Center:

{
  "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://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:

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"
      }
    }
  }
}

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_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

Cursor IDE Configuration

To integrate the MCP server with Cursor IDE:

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

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_comments`	Get comments for a specific Confluence page
`confluence_create_page`	Create a new Confluence page
`confluence_update_page`	Update 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

Build

Docker build:

docker build -t mcp/atlassian .

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.1.16

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.1.16
File	Size	Uploaded
mcp_atlassian-0.1.16.tar.gz	188.3 kB	Mar 8, 2025	Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-atlassian 0.1.16
File	Interpreter	ABI	Platform	Reset
mcp_atlassian-0.1.16-py3-none-any.whl 34.5 kB Mar 8, 2025	Python 3	none	any	Details

Total release size: 222.8 kB

Release files / mcp_atlassian-0.1.16.tar.gz

Download URL	mcp_atlassian-0.1.16.tar.gz
Size	188.3 kB
Tags	Source
SHA-256 checksum How to use checksums	`bc4027e79ca0474605a3815ff50c501d743041deb025a89a7ffc195cb58ac738`
BLAKE2b-256 checksum How to use checksums	`87e5ac26cb03addb6d13e0e40d1f80004c0c4d3b008930200241052e5c07a2bc`
Upload date	Mar 8, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`uv/0.6.0`

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

Download URL	mcp_atlassian-0.1.16-py3-none-any.whl
Size	34.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`a04a4be7e5c66416b692dc4b7bc1bc0e2f118797c9c5048998d962602de738d9`
BLAKE2b-256 checksum How to use checksums	`def0157595ea24d48c553c1d8b5c24abb69b1eb55de41b20306779345d9a6938`
Upload date	Mar 8, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`uv/0.6.0`