MCP Atlassian

Install

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

This is third-party code. Review the repository files before installing.

What it does

The server connects the agent to Jira and Confluence. The agent searches issues with JQL and pages with CQL, reads, creates and updates them, transitions statuses and adds comments. It supports Atlassian Cloud and Server/Data Center: Confluence 6.0+ and Jira 8.14+. Auth is via API token, personal access token or OAuth 2.0, and an HTTP mode serves multiple users.

Who it is for. For teams that track work in Jira and document in Confluence.

Example request

Find issues assigned to me in PROJ and move PROJ-123 to Done

Limitations

Requires an Atlassian API token or a personal access token for Server/Data Center. Atlassian Cloud restricted service for users in Russia, so cloud instances may be unreachable; a self-hosted Jira or Confluence in your network works. Not an official Atlassian product.

How to disable. Remove the mcp-atlassian block from the MCP config and revoke the API token in Atlassian settings.

MCP

Transport

stdio, sse, http

Authentication

API key

Security check

• Creates and edits issues and pages in an external system
• Holds API tokens with user-level rights

README in short

The README is a quick start: get a token, add a config with uvx and environment variables, start asking. Details live on the docs site: install via uvx, Docker and pip, auth options, HTTP transport and the tool reference. It includes a compatibility table and the key Jira and Confluence tools. MIT licensed.

Related