MCP Atlassian
listing.by
Search, create and update Jira issues and Confluence pages on Cloud or Server/Data Center with an API token or PAT.
listing.install
listing.local.explain
listing.local.needs listing.local.note
JIRA_URLJira site URL (omit to use Confluence only).JIRA_USERNAMEJira account email (Cloud).JIRA_API_TOKENlisting.env.secret Jira API token (Cloud) or use JIRA_PERSONAL_TOKEN (Server/Data Center).CONFLUENCE_URLlisting.env.optional Confluence site URL (omit to use Jira only).CONFLUENCE_USERNAMElisting.env.optional Confluence account email (Cloud).CONFLUENCE_API_TOKENlisting.env.secret listing.env.optional Confluence API token.
listing.share.h
listing.share.p_local
mcp.tc/i/mcp-atlassianlisting.about
A community server that connects an assistant to Jira and Confluence. You can search issues with JQL, read and create issues, change their status, and search, read, create and update Confluence pages and comments. The README lists 93 tools in total.
It runs locally over stdio with uvx mcp-atlassian. Cloud needs your site URL, email and an API token. Server/Data Center uses a Personal Access Token. It is not an official Atlassian product and is separate from Atlassian's hosted server.
listing.can
- Search Jira issues with JQL
- Get issue details
- Create and update Jira issues
- Transition issues to a new status
- Search Confluence with CQL
- Read, create and update Confluence pages
- Add comments to Confluence pages
- Works with Cloud and Server/Data Center
listing.tools
listing.notools.key
listing.prompts
Find issues assigned to me in the PROJ project
Search Confluence for onboarding docs
Create a bug ticket for the login issue
Update the status of PROJ-123 to Done
listing.setup.h
listing.setup.local
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio mcp-atlassian --env "JIRA_URL=<YOUR_JIRA_URL>" --env "JIRA_USERNAME=<YOUR_JIRA_USERNAME>" --env "JIRA_API_TOKEN=<YOUR_JIRA_API_TOKEN>" --env "CONFLUENCE_API_TOKEN=<YOUR_CONFLUENCE_API_TOKEN>" -- uvx mcp-atlassian- Start Claude Code and type
/mcp. mcp-atlassian should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "<YOUR_JIRA_URL>",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"CONFLUENCE_API_TOKEN": "<YOUR_CONFLUENCE_API_TOKEN>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "<YOUR_JIRA_URL>",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"CONFLUENCE_API_TOKEN": "<YOUR_CONFLUENCE_API_TOKEN>"
}
}
}
}Needs uv (Python) on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"mcp-atlassian": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "<YOUR_JIRA_URL>",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "${input:jira-api-token}",
"CONFLUENCE_API_TOKEN": "${input:confluence-api-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "jira-api-token",
"description": "JIRA_API_TOKEN",
"password": true
},
{
"type": "promptString",
"id": "confluence-api-token",
"description": "CONFLUENCE_API_TOKEN",
"password": true
}
]
}Needs uv (Python) on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "<YOUR_JIRA_URL>",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"CONFLUENCE_API_TOKEN": "<YOUR_CONFLUENCE_API_TOKEN>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add mcp-atlassian --env "JIRA_URL=<YOUR_JIRA_URL>" --env "JIRA_USERNAME=<YOUR_JIRA_USERNAME>" --env "JIRA_API_TOKEN=<YOUR_JIRA_API_TOKEN>" --env "CONFLUENCE_API_TOKEN=<YOUR_CONFLUENCE_API_TOKEN>" -- uvx mcp-atlassianOr edit ~/.codex/config.toml directly:
[mcp_servers.mcp-atlassian]
command = "uvx"
args = ["mcp-atlassian"]
env = { JIRA_URL = "<YOUR_JIRA_URL>", JIRA_USERNAME = "<YOUR_JIRA_USERNAME>", JIRA_API_TOKEN = "<YOUR_JIRA_API_TOKEN>", CONFLUENCE_API_TOKEN = "<YOUR_CONFLUENCE_API_TOKEN>" }Needs uv (Python) on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "JIRA_URL=<YOUR_JIRA_URL>" -e "JIRA_USERNAME=<YOUR_JIRA_USERNAME>" -e "JIRA_API_TOKEN=<YOUR_JIRA_API_TOKEN>" -e "CONFLUENCE_API_TOKEN=<YOUR_CONFLUENCE_API_TOKEN>" mcp-atlassian uvx mcp-atlassianThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"mcp-atlassian": {
"command": "uvx",
"args": [
"mcp-atlassian"
],
"env": {
"JIRA_URL": "<YOUR_JIRA_URL>",
"JIRA_USERNAME": "<YOUR_JIRA_USERNAME>",
"JIRA_API_TOKEN": "<YOUR_JIRA_API_TOKEN>",
"CONFLUENCE_API_TOKEN": "<YOUR_CONFLUENCE_API_TOKEN>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs uv (Python) on your computer. Replace the placeholders with your own values.
listing.faq
Can I paste mcp.tc/i/mcp-atlassian into my MCP client?
No. MCP Atlassian runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx mcp-atlassian.
Does MCP Atlassian need an API key?
Yes. It reads JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN and CONFLUENCE_API_TOKEN from its environment, and JIRA_API_TOKEN and CONFLUENCE_API_TOKEN are secrets. Put the value in your client's config on your own machine, never in a shared file.
Is MCP Atlassian a remote or a local server?
Local. Your client starts it as a process on your computer with uvx mcp-atlassian, which needs uv (Python).
What can MCP Atlassian do?
You can search Jira issues with JQL, get issue details and create and update Jira issues.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Who wrote this page?
mcp.tc's robot read MCP Atlassian's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
listing.em.h
listing.em.lead_local listing.em.how
listing.em.badge
[](https://mcp.tc/i/mcp-atlassian)<a href="https://mcp.tc/i/mcp-atlassian"><img src="https://mcp.tc/i/mcp-atlassian/badge.svg" alt="MCP Atlassian on mcp.tc" height="20"></a>listing.em.badge_note
listing.em.widget
<script src="https://mcp.tc/w/mcp-atlassian.js" async></script>listing.em.widget_note
iframe
<iframe src="https://mcp.tc/embed/mcp-atlassian" title="MCP Atlassian on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>listing.em.iframe_note
listing.disclaimer_checked