1. Home
  2. Servers
  3. Productivity
  4. MCP Atlassian

Server profile

MCP Atlassian

MCP Atlassian connects assistants to Jira and Confluence for issue tracking and team documentation. It supports Atlassian Cloud and compatible Server or Data Center installations, with tools for searching, reading, creating, and updating content.

View repositoryInstall & configure

Server facts

MCP Atlassian

Tech

Runtime / language
pythonPython
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
6,008
Last commit
Data as of

Tags

  • Atlassian
  • Confluence
  • Issue Tracking
  • Jira
  • Team Documentation

Overview

MCP Atlassian puts Jira issue workflows and Confluence knowledge into the same assistant connection. The README shows requests for assigned issues, onboarding documentation, bug creation, and issue status changes. Its named Jira tools cover JQL search, issue retrieval, creation, updates, and transitions. Confluence tools provide CQL search, page retrieval and editing, new pages, and comments. The project describes a larger catalog of 77 tools, but only the explicitly listed identifiers are included here. This combination is useful for teams whose delivery work and supporting documentation are split across the two Atlassian products.

The quickstart launches the Python package through uvx and configures each product's URL, username, and API token in the MCP client. For Server or Data Center, the README instead points to personal access tokens and specifically documents a Jira personal-token setting. Cloud editions of both products are listed as fully supported; self-managed compatibility begins at Confluence 6.0 and Jira 8.14. Claude Desktop and Cursor appear in the setup example, and separate documentation covers additional installation methods, OAuth, HTTP transports, and multi-user operation. The project is MIT-licensed and is not an official Atlassian product. Credentials remain part of setup, and the README explicitly warns against sharing tokens or leaving environment files unsecured.

Install & configure

Requirements

  • uvx
  • An MCP-compatible client
  • Access to Jira or Confluence with appropriate credentials
  • Confluence 6.0+ or Jira 8.14+ for self-managed deployments
Documented launch / install command
uvx mcp-atlassian

This is the Cloud quickstart configuration. Server/Data Center uses PAT authentication; the README specifies JIRA_PERSONAL_TOKEN in place of the Jira username and API-token pair. Keep credentials private.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Desktop configuration
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "<your Jira instance URL>",
        "JIRA_USERNAME": "<your Jira account email>",
        "JIRA_API_TOKEN": "<your Jira Cloud API token>",
        "CONFLUENCE_URL": "<your Confluence instance URL>",
        "CONFLUENCE_USERNAME": "<your Confluence account email>",
        "CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
      }
    }
  }
}

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

Cursor configuration
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "<your Jira instance URL>",
        "JIRA_USERNAME": "<your Jira account email>",
        "JIRA_API_TOKEN": "<your Jira Cloud API token>",
        "CONFLUENCE_URL": "<your Confluence instance URL>",
        "CONFLUENCE_USERNAME": "<your Confluence account email>",
        "CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
      }
    }
  }
}

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

VS Code configuration
{
  "servers": {
    "mcp-atlassian": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "<your Jira instance URL>",
        "JIRA_USERNAME": "<your Jira account email>",
        "JIRA_API_TOKEN": "<your Jira Cloud API token>",
        "CONFLUENCE_URL": "<your Confluence instance URL>",
        "CONFLUENCE_USERNAME": "<your Confluence account email>",
        "CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
      }
    }
  }
}

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

Windsurf configuration
{
  "mcpServers": {
    "mcp-atlassian": {
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "<your Jira instance URL>",
        "JIRA_USERNAME": "<your Jira account email>",
        "JIRA_API_TOKEN": "<your Jira Cloud API token>",
        "CONFLUENCE_URL": "<your Confluence instance URL>",
        "CONFLUENCE_USERNAME": "<your Confluence account email>",
        "CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
      }
    }
  }
}

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Code configuration
{
  "mcpServers": {
    "mcp-atlassian": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "<your Jira instance URL>",
        "JIRA_USERNAME": "<your Jira account email>",
        "JIRA_API_TOKEN": "<your Jira Cloud API token>",
        "CONFLUENCE_URL": "<your Confluence instance URL>",
        "CONFLUENCE_USERNAME": "<your Confluence account email>",
        "CONFLUENCE_API_TOKEN": "<your Confluence Cloud API token>"
      }
    }
  }
}

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

Source: repository README. Tool descriptions are a documented snapshot, not a live capability check.

ToolWhat it does
jira_searchFind Jira issues using a JQL query.
jira_get_issueRetrieve a Jira issue's details.
jira_create_issueCreate a new Jira issue.
jira_update_issueModify an existing Jira issue.
jira_transition_issueMove an issue to another workflow status.
confluence_searchFind Confluence content with CQL.
confluence_get_pageRead a Confluence page's content.
confluence_create_pageAdd a new Confluence page.
confluence_update_pageRevise an existing Confluence page.
confluence_add_commentPost a comment to Confluence content.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

  • Find assigned Jira issues using JQL-backed search.
  • Create bug reports and move issues through workflow statuses.
  • Search Confluence for onboarding or project documentation.
  • Create or update team pages and add comments.

Strengths

  • Connects issue tracking and knowledge pages through one integration.
  • Supports both Atlassian Cloud and compatible self-managed deployments.
  • Documents query-language searches and write operations.

Limitations

  • Requires product URLs and appropriate authentication credentials.
  • Self-managed support has minimum Confluence and Jira version requirements.
  • Only a subset of the full tool catalog is named in the README.

Frequently asked questions

Yes. The compatibility table lists Confluence Server/Data Center 6.0+ and Jira Server/Data Center 8.14+.

The named search tools use JQL for Jira and CQL for Confluence.

Yes. jira_transition_issue handles workflow status changes.

No. The README explicitly identifies it as unofficial and lists the MIT license.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

n8n MCP Server

Productivity

n8n MCP Server lets AI assistants manage workflows and inspect or control executions in an n8n instance. It supports workflow CRUD, activation controls, API execution, and authenticated webhook triggers.

nodestdio1,631 GitHub stars

MCP Shrimp Task Manager

Productivity

Shrimp organizes AI-assisted development into planned, dependent tasks with persistent progress. It helps coding assistants retain project context, research decisions, and work through implementation and verification.

nodestdio2,146 GitHub stars

HowToCook-MCP Server

Productivity

HowToCook-MCP brings the HowToCook recipe collection to AI assistants. It can retrieve recipes, suggest dishes for a group, and build weekly meal plans around ingredient exclusions and allergies.

nodestdio782 GitHub stars

ATLAS Task Management System

Productivity

ATLAS lets LLM agents manage linked projects, tasks, and knowledge through MCP. It uses Neo4j for relationships, dependencies, and cross-entity search, with stdio and streamable HTTP options.

nodestdio477 GitHub stars