
MCP server for Atlassian tools (Confluence, Jira)
MCP server for Atlassian tools (Confluence, Jira)
·
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
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": "[email protected]",
"JIRA_API_TOKEN": "your_api_token",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "[email protected]",
"CONFLUENCE_API_TOKEN": "your_api_token"
}
}
}
}Server/Data Center users: Use
JIRA_PERSONAL_TOKENinstead ofJIRA_USERNAME+JIRA_API_TOKEN. See Authentication for details.
Use the same uvx server with your Atlassian credentials:
autohand mcp add mcp-atlassian env \
JIRA_URL=https://your-company.atlassian.net \
[email protected] \
JIRA_API_TOKEN=your_api_token \
CONFLUENCE_URL=https://your-company.atlassian.net/wiki \
[email protected] \
CONFLUENCE_API_TOKEN=your_api_token \
uvx mcp-atlassianAdd --scope project after add to keep the configuration in the current
project. See Autohand Code for current
installation and CLI 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 |
98 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.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add mcp-atlassian -- uvx mcp-atlassian{
"mcpServers": {
"mcp-atlassian": {
"env": {
"JIRA_URL": "",
"JIRA_USERNAME": "",
"CONFLUENCE_URL": "",
"JIRA_API_TOKEN": "",
"CONFLUENCE_USERNAME": "",
"CONFLUENCE_API_TOKEN": ""
},
"args": [
"mcp-atlassian"
],
"command": "uvx"
}
}
}code --add-mcp '{"name":"mcp-atlassian","env":{"JIRA_URL":"","JIRA_USERNAME":"","CONFLUENCE_URL":"","JIRA_API_TOKEN":"","CONFLUENCE_USERNAME":"","CONFLUENCE_API_TOKEN":""},"args":["mcp-atlassian"],"command":"uvx"}'[mcp_servers.mcp-atlassian]
command = "uvx"
args = ["mcp-atlassian"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/atlassian-mcp-jira-and-confluence to learn what the "Atlassian MCP (Jira & Confluence)" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
uvx mcp-atlassianThis server runs locally, so we can't read its tool list over the web yet.
It is a thin connector. It discovers running Next.js 16+ dev servers and proxies their built-in MCP
Postman MCP Server — connect AI agents (Claude Code, Cursor, VS Code Copilot, Gemini CLI) to your Po
The Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced a
v0.23.1Release notesv0.23.0Release notesv0.22.1Release notesv0.22.0Release notesv0.21.1Release notesv0.21.0Release notesv0.20.1Release notesv0.20.0Release notesv0.19.0Release notesv0.18.1Release notesv0.18.0Release notesv0.17.0Release notesv0.16.1Release notesv0.16.0Release notesv0.15.0Release notesv0.14.3Release notesv0.14.2Release notesv0.14.1Release notesv0.14.0Release notesv0.13.1Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "atlassian-mcp-jira-and-confluence" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
It is a thin connector. It discovers running Next.js 16+ dev servers and proxies their built-in MCP
Developer Tools
Postman MCP Server — connect AI agents (Claude Code, Cursor, VS Code Copilot, Gemini CLI) to your Po
Developer Tools
The Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced a
Developer Tools
One email a week. New agents, MCP servers and skills, and what is actually getting traction.