A unified server for Atlassian Jira and Confluence that supports issue management and documentation collaboration across Cloud and On-Prem/Data Center deployments.
Provides tools for interacting with Confluence, including searching with CQL, retrieving page content, creating and updating pages, and adding comments.
Enables programmatic management of Jira issues, allowing users to search with JQL, retrieve issue details, create and update tickets, and transition issue statuses.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP AtlassianFind all open bugs assigned to me in the PROJ project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Atlassian (On-Prem/Data Center Ready)
Model Context Protocol (MCP) server for Atlassian Jira and Confluence. Supports Cloud and Server/Data Center deployments, with on-prem friendly auth and SSL options.
Fork note: this repository is based on https://github.com/sooperset/mcp-atlassian and focuses on on-prem/Data Center deployment clarity and repo hygiene for production use.
https://github.com/user-attachments/assets/35303504-14c6-4ae4-913b-7c25ea511c3e
https://github.com/user-attachments/assets/7fe9c488-ad0c-4876-9b54-120b666bb785
Why use this
Unified Jira + Confluence MCP server with typed models and robust tooling
Works with Cloud and Server/Data Center (PAT, OAuth, basic auth)
Read-only mode for safer production usage
Streamable HTTP and SSE transports for multi-user setups
Quick Start
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:
Python 3.14 not yet supported. Use
["--python=3.12", "mcp-atlassian"]as args if needed.
Server/Data Center users: Use
JIRA_PERSONAL_TOKENinstead ofJIRA_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"
On-Prem/Data Center notes
PAT auth: set
JIRA_PERSONAL_TOKENandCONFLUENCE_PERSONAL_TOKENSSL: set
JIRA_SSL_VERIFY=falseorCONFLUENCE_SSL_VERIFY=falseonly when requiredClient certs:
JIRA_CLIENT_CERT/JIRA_CLIENT_KEYandCONFLUENCE_CLIENT_CERT/CONFLUENCE_CLIENT_KEY
Documentation
Full documentation is available at personal-1d37018d.mintlify.app.
Documentation is also available in llms.txt format, which LLMs can consume easily:
llms.txt— documentation sitemapllms-full.txt— complete documentation
Topic | Description |
uvx, Docker, pip, from source | |
API tokens, PAT, OAuth 2.0 | |
IDE setup, environment variables | |
SSE, streamable-http, multi-user | |
All Jira & Confluence tools | |
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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See Tools Reference for the complete list.
Security
Never share API tokens. Keep .env files secure. See SECURITY.md.
Contributing
See CONTRIBUTING.md for development setup.
License
MIT - See LICENSE. Not an official Atlassian product.