Back to MCP Servers
🔌

sooperset/mcp-atlassian

MITAPI key required

🐍 ☁️ - MCP server for Atlassian products (Confluence and Jira). Supports Confluence Cloud, Jira Cloud, and Jira Server/Data Center. Provides comprehensive tools for searching, reading, creating, and

PythonDev Tools

Install

npx -y sooperset-mcp-atlassian

Required environment variables

JIRA_API_TOKENSet in your MCP config
CONFLUENCE_API_TOKENSet in your MCP config
JIRA_PERSONAL_TOKENSet in your MCP config

claude_desktop_config.json

claude_desktop_config.json
{
  "mcpServers": {
    "sooperset-mcp-atlassian": {
      "command": "npx",
      "args": [
        "-y",
        "sooperset-mcp-atlassian"
      ],
      "env": {
        "JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
        "CONFLUENCE_API_TOKEN": "<YOUR_CONFLUENCE_API_TOKEN>",
        "JIRA_PERSONAL_TOKEN": "<YOUR_JIRA_PERSONAL_TOKEN>"
      }
    }
  }
}

Add this to your Claude Desktop config file. Find it at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS.

What this does

sooperset/mcp-atlassian exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation. That makes it useful when you want Claude to reach into your developer tooling without copy-pasting context every turn.

Requirements

This server needs the following environment variables to be set before it can run:

JIRA_API_TOKEN
CONFLUENCE_API_TOKEN
JIRA_PERSONAL_TOKEN

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

Common use cases

  • Drive your build, test, lint, or deploy commands from a chat session
  • Pull CI status, commit metadata, or PR review state into context
  • Inspect or scaffold project boilerplate without leaving Claude