mcp-atlassian 0.1.8

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

MCP Atlassian

Model Context Protocol (MCP) server for Atlassian Cloud products (Confluence and Jira). This integration is designed specifically for Atlassian Cloud instances and does not support Atlassian Server or Data Center deployments.

Feature Demo

Demo

Resources

confluence://{space_key}: Access Confluence spaces and pages
confluence://{space_key}/pages/{title}: Access specific Confluence pages
jira://{project_key}: Access Jira project and its issues
jira://{project_key}/issues/{issue_key}: Access specific Jira issues

Tools

Confluence Tools

confluence_search
- Search Confluence content using CQL
- Inputs:
  - query (string): CQL query string
  - limit (number, optional): Results limit (1-50, default: 10)
- Returns: Array of search results with page_id, title, space, url, last_modified, type, and excerpt
confluence_get_page
- Get content of a specific Confluence page
- Inputs:
  - page_id (string): Confluence page ID
  - include_metadata (boolean, optional): Include page metadata (default: true)
- Returns: Page content and optional metadata
confluence_get_comments
- Get comments for a specific Confluence page
- Input:
  - page_id (string): Confluence page ID
- Returns: Array of comments with author, creation date, and content

Jira Tools

jira_get_issue
- Get details of a specific Jira issue
- Inputs:
  - issue_key (string): Jira issue key (e.g., 'PROJ-123')
  - expand (string, optional): Fields to expand
- Returns: Issue details including content and metadata
jira_search
- Search Jira issues using JQL
- Inputs:
  - jql (string): JQL query string
  - fields (string, optional): Comma-separated fields (default: "*all")
  - limit (number, optional): Results limit (1-50, default: 10)
- Returns: Array of matching issues with metadata
jira_get_project_issues
- Get all issues for a specific Jira project
- Inputs:
  - project_key (string): Project key
  - limit (number, optional): Results limit (1-50, default: 10)
- Returns: Array of project issues with metadata

Installation

Using uv (recommended)

When using uv, use uvx to directly run mcp-atlassian.

Using Smithery

To install Atlassian Integration 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.

Usage with Claude Desktop

Get API tokens from: https://id.atlassian.com/manage-profile/security/api-tokens
Add to your claude_desktop_config.json with only the services you need:

Using uvx

For Confluence only:

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

For Jira only:

{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_USERNAME": "your.email@domain.com",
        "JIRA_API_TOKEN": "your_api_token"
      }
    }
  }
}

For both services:

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

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 (recommended):

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

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

Development

For local development testing:

Use the MCP inspector (see Debugging)
Test with Claude Desktop using the configuration above

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

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.8
File	Size	Uploaded
mcp_atlassian-0.1.8.tar.gz	39.1 kB	Feb 16, 2025	Details

Built distribution (wheel)

Table of built distributions (wheels) for mcp-atlassian 0.1.8
File	Interpreter	ABI	Platform	Reset
mcp_atlassian-0.1.8-py3-none-any.whl 14.1 kB Feb 16, 2025	Python 3	none	any	Details

Total release size: 53.3 kB

Release files / mcp_atlassian-0.1.8.tar.gz

Download URL	mcp_atlassian-0.1.8.tar.gz
Size	39.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`0a02382cda14c94b8cc0284ffe02db1cccbd539b8648290c62265b7357fe65e6`
BLAKE2b-256 checksum How to use checksums	`6be931e79a6af1dab4a50d0bc99ffa6dadc808ff17dbb6c946a33cae718cebba`
Upload date	Feb 16, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`uv/0.5.5`

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

Download URL	mcp_atlassian-0.1.8-py3-none-any.whl
Size	14.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`727ff68e7b4f012dbcf7129db31cdecab8de5c6e9fe24e82ff6c1a9764a83ea0`
BLAKE2b-256 checksum How to use checksums	`62cdef6dc6313a021d2da24cf66f920c3abfe8061bcb088bf594d4e139337314`
Upload date	Feb 16, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`uv/0.5.5`