Community-built MCP server for Jira and Confluence with 72 tools. Dual implementation alongside official Atlassian Rovo MCP (now GA).
Where it wins
Deepest tool set: 72 tools across Jira and Confluence
Highest stars of any business MCP server (4.6K+)
Dual path: community MIT server + official Atlassian Rovo GA
Supports Cloud, Server, and Data Center deployments
Most active dev cadence: 69 releases, ~28.5 commits/week
Where to be skeptical
72 tools approaching context-flooding threshold
165 open issues suggests growing pains at scale
Official Rovo server may eventually supersede community version
Editorial verdict
#2 overall, #1 enterprise operating surface for teams on the Atlassian stack. 4,666 stars, deepest tool set (72 tools), 139K PyPI weekly downloads, 140K PulseMCP/wk (#14 global). On-prem/Data Center support is the key moat vs official Rovo MCP.
Videos
Reviews, tutorials, and comparisons from the community.
Why I Never Open JIRA Anymore: MCP (Model Context Protocol) Beyond Coding
Install Atlassian MCP Server in VS Code | GitHub Copilot Integration Tutorial (Marketplace Setup)
JIRA MCP Integration Tutorial: Complete Guide with Python Client, FastAPI & Streamlit
Related
Exa MCP Server
87Official Exa MCP for fast web search and crawling when the workflow is search-first rather than page-ops-first.
Notion MCP Server
86Official Notion MCP server with hosted OAuth, token-optimized Markdown responses, and 22 tools for page/database/search operations.
PostHog MCP
84Official PostHog MCP — product analytics, feature flags, experiments, error tracking, and usage insights via MCP. Integrated into PostHog monorepo Jan 2026. #5 all-time globally on PulseMCP (5.7M visits).
Google Workspace MCP
80The most complete public Google Workspace MCP surface right now across Gmail, Docs, Sheets, Calendar, Drive, and more.
Public evidence
Snyk rated mcp-atlassian the most comprehensive project management MCP server. Tool count has since grown from 31 to 72.
4,621 stars, 1,008 forks, 118 contributors, 69 releases. Latest v0.21.0 (2026-03-02). Most active business MCP server by all community metrics.
Clear segmentation: sooperset for flexibility/on-prem/DC, Rovo for enterprise/zero-setup/Cloud. Both paths active and complementary.
Independent validation of Atlassian's MCP positioning as strategic enterprise infrastructure, not just a developer tool.
HN discussion validates core user need: making Jira bearable through AI agent integration. 23 points, 19 comments shows engaged niche interest.
~800K monthly PyPI downloads is the primary distribution channel. npm (2.8K/week) is a secondary wrapper. Discover stage under-reported this by focusing on npm.
Highest PulseMCP interest signal in the product-business-development category by far. 140K estimated weekly visitors, 2.3M all-time.
Raw GitHub source
Constrained peek so you can sanity-check the source material without leaving the site.
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>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.
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_TOKENinstead ofJIRA_USERNAME+JIRA_API_TOKEN. See Authentication for details.
Ask your AI assistant to:
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 sitemapllms-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 |
| 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+) |
| 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 |
72 tools total — See Tools Reference for the complete list.
Never share API tokens. Keep .env files secure. See SECURITY.md.
See CONTRIBUTING.md for development setup.
MIT - See LICENSE. Not an official Atlassian product.