Jira MCP Server

tl;dr: there is no official Anthropic Jira MCP server. @modelcontextprotocol/server-jira was never published. The dominant community option is sooperset/mcp-atlassian (5.9k stars, MIT, Python, uvx mcp-atlassian), which covers both Confluence and Jira Cloud and Jira Server/Data Center.

What it does

mcp-atlassian wraps the Atlassian REST APIs (Jira + Confluence) and exposes 98 MCP tools. For Jira you get: JQL search, get/create/update issues, transitions, comments, attachments, sprint management, board inspection, and user lookups. Reads are read-only by default; writes require an API token with the right scopes.

Install

uvx mcp-atlassian

The CLI is hosted on PyPI and pulls from the awslabs/mcp-style Python ecosystem (uv/uvx from Astral).

Claude Desktop config

{
  "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"
      }
    }
  }
}

For Jira Server/Data Center, swap JIRA_USERNAME + JIRA_API_TOKEN for JIRA_PERSONAL_TOKEN. For Confluence, set the matching CONFLUENCE_* env vars. Get a Cloud API token at id.atlassian.com/manage-profile/security/api-tokens.

Streaming HTTP / multi-user

The same server also runs over HTTP/SSE for shared deployments — see HTTP transport. Useful if you want one server for a team rather than per-laptop.

Key tools (Jira subset)

• jira_search — JQL queries
• jira_get_issue / jira_create_issue / jira_update_issue
• jira_transition_issue — change workflow status
• jira_add_comment / jira_get_comments
• jira_list_sprints / jira_get_sprint

Full list: Tools Reference.

Gotchas

• The token is a real Atlassian API token — anyone holding it can read/modify your Jira. Use a scoped token, rotate it, don’t commit it.
• Server/DC URLs do not use the atlassian.net host; the README assumes Cloud by default.
• It’s not an official Atlassian product; support is via the repo’s issues, not Atlassian.

Related

• Notion MCP — workspace docs
• Playwright MCP — for browsing Jira from the agent
• MCP Servers Explained