Atlassian Cli

by putcho01

392 downloads

Not rated

GitHub

About

Single-binary MCP server and CLI for Jira and Confluence. CI/CD-friendly, context-efficient, supports both Cloud and Server/DC.Copy

Details

Author: putcho01
Downloads: 392
Categories: Developer Tools, Project Management, Other, Knowledge Base, Infrastructure

- Single binary — no runtime dependencies required.
- Auth via environment variables — works in headless/CI.
- Supports Atlassian Cloud (API token) and Server/DC (PAT).
- MCP server mode for Claude Code, Cursor, and other AI tools.
- Output in table, JSON, or GitHub-flavored Markdown.
- Interactive TUI mode available.

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 Cli

Command (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

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

From the repository

Atlassian Cli is distributed as a single binary with no runtime dependencies. Authentication is configured via environment variables, supporting both Atlassian Cloud (API token) and Server/Data Center (PAT). It can run in MCP server mode for AI tools like Claude Code and Cursor.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "atlassian cli": {
            "atlassian": {
                "command": "atlassian-cli",
                "args": [
                    "mcp-server"
                ],
                "env": {
                    "JIRA_URL": "https://your-domain.atlassian.net",
                    "JIRA_EMAIL": "you@example.com",
                    "JIRA_API_TOKEN": "your-api-token",
                    "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
                    "CONFLUENCE_EMAIL": "you@example.com",
                    "CONFLUENCE_API_TOKEN": "your-api-token"
                }
            }
        }
    }
}

McpServers

{
    "atlassian": {
        "command": "atlassian-cli",
        "args": [
            "mcp-server"
        ],
        "env": {
            "JIRA_URL": "https://your-domain.atlassian.net",
            "JIRA_EMAIL": "you@example.com",
            "JIRA_API_TOKEN": "your-api-token",
            "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki",
            "CONFLUENCE_EMAIL": "you@example.com",
            "CONFLUENCE_API_TOKEN": "your-api-token"
        }
    }
}

go install github.com/putcho01/atlassian-cli@latest

If$GOPATH/binis not in your$PATH, add the following to your shell config (~/.zshrc, etc.):

export PATH="$PATH:$(go env GOPATH)/bin"

git clone https://github.com/putcho01/atlassian-cli.git cd atlassian-cli go build -o atlassian-cli .

export JIRA_URL=https://your-domain.atlassian.net export JIRA_EMAIL=you@example.com export JIRA_API_TOKEN=your-api-token

To use Confluence as well, set the additional variables:

export CONFLUENCE_URL=https://your-domain.atlassian.net/wiki export CONFLUENCE_EMAIL=you@example.com export CONFLUENCE_API_TOKEN=your-api-token

export JIRA_URL=https://jira.example.com export JIRA_PERSONAL_TOKEN=your-pat

IfJIRA_EMAILis not set, Bearer (PAT) authentication is used automatically.

Two authentication methods are supported:

Used with Atlassian Cloud (*.atlassian.net). Authenticates via Basic auth using your email address and API token.

Server/Data Center - Personal Access Token (Bearer)

Used with self-hosted Jira/Confluence Server/DC. Authenticates via Bearer auth using a PAT.

IfEMAILis set, Basic auth (Cloud) is used; otherwise Bearer auth (Server/DC) is used.

Only the variables for the service you use are required. For example, if you only use Jira, you don't need to set the Confluence variables.

# Authentication atlassian-cli jira myself # Show authenticated user # Issues atlassian-cli jira issue get PROJ-123 # Get issue (includes description) atlassian-cli jira issue open PROJ-123 # Open issue in browser atlassian-cli jira issue search "project = PROJ" # Search issues via JQL atlassian-cli jira issue search "project = PROJ" -i # Interactive TUI picker (↑/↓ navigate, enter detail, o open, q quit) atlassian-cli jira issue create --project PROJ --summary "New task" # or omit --project if JIRA_DEFAULT_PROJECT is set atlassian-cli jira issue update PROJ-123 --field summary="Updated summary" atlassian-cli jira issue delete PROJ-123 atlassian-cli jira issue subtasks PROJ-123 atlassian-cli jira issue transition PROJ-123 "In Progress" # Comments atlassian-cli jira issue comment list PROJ-123 atlassian-cli jira issue comment add PROJ-123 --body "Looks good to me"

# Pages atlassian-cli confluence page get 12345 # Get page content atlassian-cli confluence page create --space PROJ --title "New Page" --body "<p>Hello</p>" atlassian-cli confluence page create --space PROJ --title "Child Page" --parent 12345 --body "<p>Child</p>" atlassian-cli confluence page update 12345 --title "Updated Title" --body "<p>New content</p>" # version auto-detected atlassian-cli confluence page update 12345 --title "Updated Title" --body "<p>New content</p>" --version 3 # explicit version # Labels atlassian-cli confluence label list 12345 atlassian-cli confluence label add 12345 important,reviewed atlassian-cli confluence label remove 12345 outdated # Page Restrictions atlassian-cli confluence restriction list 12345 atlassian-cli confluence restriction add 12345 --operation update --type user --name <account-id> atlassian-cli confluence restriction remove 12345 --operation update --type user --name <account-id>

All commands support three output formats via the--output/-oflag:

# Default: human-readable table atlassian-cli jira issue search "project = PROJ" -o table # Machine-readable JSON atlassian-cli jira issue search "project = PROJ" -o json # GitHub-flavored Markdown (great for Claude Code) atlassian-cli jira issue search "project = PROJ" -o markdown

When using-o markdown, HTML content (Jira descriptions, Confluence page bodies and comments) is automatically converted to clean GitHub-flavored Markdown. Confluence storage format macros are also handled:

- Code blocks (ac:structured-macro name="code") -> fenced code blocks
- Admonitions (note, info, warning, tip) -> blockquotes with labels
- Page links (ac:link) -> emphasized text
- Table of contents macros -> removed

Start as an MCP server for AI assistant integration:

Filter available tools using the--toolsflag:

# Only enable Jira issue and search tools atlassian-cli mcp-server --tools jira_issue,jira_search # Only enable Confluence tools atlassian-cli mcp-server --tools confluence_page,confluence_label

- jira_user- User authentication
- jira_issue- Get issue, subtasks
- jira_search- Search issues via JQL
- jira_create- Create issues
- jira_update- Update issues
- jira_delete- Delete issues
- jira_transition- Transition issues, get available transitions
- confluence_page- Get page content
- confluence_label- Label management
- confluence_restriction- Page restriction management

{ "mcpServers": { "atlassian": { "command": "atlassian-cli", "args": ["mcp-server"], "env": { "JIRA_URL": "https://your-domain.atlassian.net", "JIRA_EMAIL": "you@example.com", "JIRA_API_TOKEN": "your-api-token", "CONFLUENCE_URL": "https://your-domain.atlassian.net/wiki", "CONFLUENCE_EMAIL": "you@example.com", "CONFLUENCE_API_TOKEN": "your-api-token" } } } }

Atlassian provides an official CLI (ACLI) and a remote MCP serverfor AI integration. Here's how this tool differs:

Atlassian's remote MCP server went GA in February 2026, but comes with trade-offs:

- Context-heavy— loads 73 tool schemas upfront, consuming 40–50% of the context window before any real work
- OAuth required— browser-based auth flow; not suitable for headless or CI/CD environments
- Network dependency— requires an outbound connection to Atlassian's remote server

This tool's--toolsflag lets you load only the groups you need, keeping token usage minimal for AI agents.

- Running inCI/CD pipelinesor automation scripts (auth via environment variables only)
- Using bothServer/Data Center and Cloudwith a single interface
- Embedding as anMCP serverin AI agents where context efficiency matters

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Interact with Atlassian tools like Confluence and Jira.

Integrate with Atlassian Cloud to access Jira tickets, issues, projects, and Confluence pages.

An MCP client for integrating with Atlassian tools like Jira and Confluence using OAuth authentication.

Integrate Atlassian products like Confluence and Jira with the Model Context Protocol.

An MCP server with integrations for GitLab, Jira, Confluence, and YouTube, providing AI-powered search and development utility tools.

Atlassian Rovo MCP Server (Streamin HTTP)

Analyzes GitLab merge requests and links them to Confluence documentation.

Official Atlassian MCP server for connecting AI agents to Jira, Confluence, Opsgenie, and other Atlassian products.

A read-only server for accessing Atlassian products like Confluence and Jira.

MCP servers for interacting with Jira and Confluence APIs.

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

Atlassian Cli

About

Details

Jump to

Setting up with Highlight

Setting up with Cursor

JSON

JSON

JSON

Setting up with Claude Desktop

JSON

JSON

JSON

Setting up with Windsurf

JSON

JSON

JSON

Setting up with Cline

JSON

JSON

JSON

Setting up with Goose

JSON

JSON

JSON

From the repository

Claude Desktop / Cursor

McpServers

Server/Data Center - Personal Access Token (Bearer)

Atlassian Rovo MCP Server (Streamin HTTP)

Install

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

Server/Data Center - Personal Access Token (Bearer)

Atlassian Rovo MCP Server (Streamin HTTP)

Install

More like this

Sequential Thinking

Sentry

Github

Filesystem

EverArt

Google Drive