sooperset/mcp-atlassian
mcp-atlassian is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.
If you are the rightful owner of mcp-atlassian and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). This integration supports both Confluence & Jira Cloud and Server/Data Center deployments.
Try mcp-atlassian with chat:
Server config via mcphub
Traditional api access examples
Path-based authentication
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
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:
{
"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"
}
}
}
}
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"
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 |
|---|---|
| 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 |
See Tools Reference for the complete list.
Security
Never share API tokens. Keep .env files secure. See .
Contributing
See for development setup.
License
MIT - See . Not an official Atlassian product.
