Mind the Product take

Love it or not, Jira is where many enterprise product teams track their work. This MCP server (which also covers Confluence) lets your AI agent create issues, update sprints, query backlogs, and search across your Atlassian workspace. The real value is in reducing the Jira tax - instead of spending 20 minutes creating well-formatted tickets with proper labels and links, your agent can do it from a quick description in seconds.

How product builders use Jira

1Create well-structured Jira tickets from product requirements in seconds
2Query sprint progress and velocity metrics for standups
3Bulk-update issue priorities and labels based on strategic shifts
4Search across Jira and Confluence for related work and decisions
5Generate sprint reports and burndown summaries automatically

Getting started

From the official Jira README

MCP Atlassian

Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Supports both Cloud and Server/Data Center deployments.

https://github.com/user-attachments/assets/35303504-14c6-4ae4-913b-7c25ea511c3e

<details> <summary>Confluence Demo</summary>

https://github.com/user-attachments/assets/7fe9c488-ad0c-4876-9b54-120b666bb785

</details>

1. Get Your API Token

Go to https://id.atlassian.com/manage-profile/security/api-tokens and create a token.

For Server/Data Center, use a Personal Access Token instead. See Authentication.

2. Configure Your IDE

Add to your Claude Desktop or Cursor MCP configuration:

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

Server/Data Center users: Use JIRA_PERSONAL_TOKEN instead of JIRA_USERNAME + JIRA_API_TOKEN. See Authentication for details.

3. Start Using

Ask your AI assistant to:

"Find issues assigned to me in PROJ project"
"Search Confluence for onboarding docs"
"Create a bug ticket for the login issue"
"Update the status of PROJ-123 to Done"

Documentation

Full documentation is available at mcp-atlassian.soomiles.com.

Documentation is also available in llms.txt format, which LLMs can consume easily:

llms.txt — documentation sitemap
llms-full.txt — complete documentation

| Topic | Description | |-------|-------------| | Installation | uvx, Docker, pip, from source | | Authentication | API tokens, PAT, OAuth 2.0 | | Configuration | IDE setup, environment variables | | HTTP Transport | SSE, streamable-http, multi-user | | Tools Reference | All Jira & Confluence tools | | Troubleshooting | Common issues & debugging |

Compatibility

| Product | Deployment | Support | |---------|------------|---------| | Confluence | Cloud | Fully supported | | Confluence | Server/Data Center | Supported (v6.0+) | | Jira | Cloud | Fully supported | | Jira | Server/Data Center | Supported (v8.14+) |

Key Tools

| Jira | Confluence | |------|------------| | jira_search - Search with JQL | confluence_search - Search with CQL | | jira_get_issue - Get issue details | confluence_get_page - Get page content | | jira_create_issue - Create issues | confluence_create_page - Create pages | | jira_update_issue - Update issues | confluence_update_page - Update pages | | jira_transition_issue - Change status | confluence_add_comment - Add comments |

93 tools total — See Tools Reference for the complete list.