mcp-atlassian

Connects to Atlassian JIRA API for issue management and queries. Runs locally as a Podman container subprocess. Requires JIRA URL, username, API token, and optional SSL verify.

Jira

developer-tools

Add to Your Project

Copy this JSON into your .mcp.json to enable this server

Add to your .mcp.json:

{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "podman",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "JIRA_URL",
        "-e",
        "JIRA_USERNAME",
        "-e",
        "JIRA_API_TOKEN",
        "-e",
        "JIRA_SSL_VERIFY",
        "ghcr.io/sooperset/mcp-atlassian@sha256:5cef5042baa79ef1b193d4a6586f3dfd3de251546aa9ee356e4a8a29f7722f7c"
      ],
      "env": {
        "JIRA_URL": "https://redhat.atlassian.net",
        "JIRA_USERNAME": "${JIRA_USERNAME}",
        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
        "JIRA_SSL_VERIFY": "true"
      }
    }
  }
}

Replace placeholder values for: JIRA_API_TOKEN

Security Considerations

Review these signals before enabling this server

Requires secrets

This MCP server needs API keys or credentials. Configure them in your environment before use.

Details

Server configuration and connection parameters

Commandpodman

Access Levelwrite

Arguments

Command-line arguments passed to the server process

run--rm-i-eJIRA_URL-eJIRA_USERNAME-eJIRA_API_TOKEN-eJIRA_SSL_VERIFYghcr.io/sooperset/mcp-atlassian@sha256:5cef5042baa79ef1b193d4a6586f3dfd3de251546aa9ee356e4a8a29f7722f7c

Environment Variables

Environment variables set when the server starts

JIRA_URL=https://redhat.atlassian.net

JIRA_USERNAME=${JIRA_USERNAME}

JIRA_API_TOKEN=${JIRA_API_TOKEN}

JIRA_SSL_VERIFY=true

Required Secrets

Sensitive values you must provide — never committed to source control

JIRA_API_TOKEN

Capabilities

Declared capabilities of this MCP server

issues

Stats

LanguagePython

Parent stars6

Parent forks9

MaintenanceExcellent

Last CommitApr 19, 2026

Actions

Stats

Actions