
mcp-atlassian (community Jira/Confluence)
Self-hosted MCP server for Jira and Confluence Cloud and Server/Data Center.
Add to your client
Copy the config for your MCP client and paste it into its config file.
uvx mcp-atlassianPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp-atlassian-community-jira-confluence": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "https://your-company.atlassian.net",
"JIRA_USERNAME": "<your-email@company.com>",
"JIRA_API_TOKEN": "<your-jira-api-token>",
"CONFLUENCE_URL": "https://your-company.atlassian.net/wiki",
"CONFLUENCE_USERNAME": "<your-email@company.com>",
"CONFLUENCE_API_TOKEN": "<your-confluence-api-token>"
}
}
}
}Requires `uv` (the Python package runner). Install it from https://docs.astral.sh/uv/ if `uvx` is not found.
Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Python with `uv`/`uvx` (recommended), or Docker, to run the server; pip and from-source installs are also supported
- For Atlassian Cloud: your site URL plus an Atlassian API token (id.atlassian.com → Security → API tokens) and the account email
- For Jira/Confluence Server or Data Center: a Personal Access Token (PAT) and the base URL (Jira 8.14+, Confluence 6.0+)
- Optional: OAuth 2.0 credentials if you prefer OAuth over tokens
About mcp-atlassian (community Jira/Confluence)
A popular community (non-official) MCP server that connects Jira and Confluence to MCP clients. Unlike Atlassian's hosted Rovo server, this one runs locally over stdio (or as a self-hosted HTTP/SSE service) and — critically — supports both Atlassian Cloud and Server/Data Center deployments, making it the go-to choice for self-managed instances.
It ships ~70+ tools across Jira and Confluence with a clear jira_* / confluence_* naming scheme, covering search, read, create, update, transition, and comment operations. Distribution is flexible: run it with uvx mcp-atlassian, via Docker, pip, or from source.
Authentication adapts to your deployment — API token + email for Cloud, a Personal Access Token (PAT) for Server/Data Center, or OAuth 2.0. It is MIT-licensed and explicitly not an official Atlassian product, so you self-host and self-support it.
Tools & capabilities (11)
jira_searchSearch Jira issues with JQL
jira_get_issueFetch a Jira issue by key
jira_create_issueCreate a new Jira issue
jira_update_issueUpdate fields on a Jira issue
jira_transition_issueMove an issue through its workflow
jira_add_commentAdd a comment to a Jira issue
confluence_searchSearch Confluence content (CQL)
confluence_get_pageFetch a Confluence page
confluence_create_pageCreate a new Confluence page
confluence_update_pageUpdate an existing Confluence page
confluence_add_commentAdd a comment to a Confluence page
What this server can do
mcp-atlassian (community Jira/Confluence) provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Use it when your Jira/Confluence runs on Server or Data Center, which the official Rovo server doesn't support
- Use it when you need a local stdio server you fully control rather than a hosted remote endpoint
- Use it when you want to self-host an Atlassian MCP integration via Docker or uvx in your own environment
- Use it when an agent should search, create, update, and transition Jira issues programmatically
- Use it when reading or writing Confluence pages and comments from an AI assistant
- Use it when you need broad tool coverage (70+ tools) across both Jira and Confluence in one server
Quick setup
- 1Install/run with `uvx mcp-atlassian` (or pull the Docker image / pip install)
- 2Set credentials via environment variables: Cloud uses `JIRA_URL` + `JIRA_USERNAME` + `JIRA_API_TOKEN` and `CONFLUENCE_URL` + `CONFLUENCE_USERNAME` + `CONFLUENCE_API_TOKEN`; Server/DC uses `JIRA_PERSONAL_TOKEN` / PAT
- 3Add the server to your MCP client config (e.g. Claude Desktop or Cursor) pointing at the uvx/Docker command with those env vars
- 4Restart the client so it loads the Jira/Confluence tools
- 5Verify by asking the assistant to run a JQL search or fetch a known Confluence page
Security notes
Supply Jira/Confluence API tokens via env vars (or an --env-file), never in committed config; the server inherits the permissions of the supplied account. For Server/Data Center use JIRA_PERSONAL_TOKEN / CONFLUENCE_PERSONAL_TOKEN instead of username+API-token.
mcp-atlassian (community Jira/Confluence) FAQ
Is this an official Atlassian product?
No. It's an MIT-licensed community project (sooperset/mcp-atlassian) and is not affiliated with or supported by Atlassian. For an official hosted option on Cloud, use the Atlassian Rovo MCP server.
Does it support Jira/Confluence Server and Data Center?
Yes — this is a key reason to choose it. It works with Atlassian Cloud and with Server/Data Center (Jira 8.14+, Confluence 6.0+), using a Personal Access Token for self-hosted instances.
How do I authenticate?
For Cloud, set your email as `JIRA_USERNAME`/`CONFLUENCE_USERNAME` and an Atlassian API token as `JIRA_API_TOKEN`/`CONFLUENCE_API_TOKEN`. For Server/Data Center, use a Personal Access Token (PAT). OAuth 2.0 is also supported.
What's the easiest way to run it?
`uvx mcp-atlassian` (requires Python + uv) is the simplest; a Docker image is provided for containerized or multi-user HTTP/SSE deployments, and pip/from-source installs are also available.
How many tools does it provide?
Around 70+ tools total across Jira and Confluence, named `jira_*` and `confluence_*`, covering search, read, create, update, transition, and commenting.
Alternatives to mcp-atlassian (community Jira/Confluence)
Compare all alternatives →AI-powered task-management system for AI-driven development that drops into Cursor, Windsurf, Claude Code, and more.
Gives AI assistants deep knowledge of 2,000+ n8n nodes, plus optional workflow management on your own n8n instance.
Background computer-use MCP server that drives native macOS, Windows, and Linux desktop apps without stealing focus.
Compare mcp-atlassian (community Jira/Confluence) with: