# MCP Atlassian > Search, create and update Jira issues and Confluence pages on Cloud or Server/Data Center with an API token or PAT. - Listing: https://mcp.tc/i/mcp-atlassian - Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint. - Type: local (stdio) - Auth: API key - Category: [Productivity & Projects](https://mcp.tc/c/productivity) - Vendor: sooperset - Homepage: - Repository: - Package: pypi `mcp-atlassian` ## 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. ## What it can do - 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 ## Example 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" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport stdio mcp-atlassian --env "JIRA_URL=" --env "JIRA_USERNAME=" --env "JIRA_API_TOKEN=" --env "CONFLUENCE_API_TOKEN=" -- uvx mcp-atlassian ``` 2. 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 1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add: `claude_desktop_config.json`: ```json { "mcpServers": { "mcp-atlassian": { "command": "uvx", "args": [ "mcp-atlassian" ], "env": { "JIRA_URL": "", "JIRA_USERNAME": "", "JIRA_API_TOKEN": "", "CONFLUENCE_API_TOKEN": "" } } } } ``` 2. 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 [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "mcp-atlassian": { "command": "uvx", "args": [ "mcp-atlassian" ], "env": { "JIRA_URL": "", "JIRA_USERNAME": "", "JIRA_API_TOKEN": "", "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: `.vscode/mcp.json`: ```json { "servers": { "mcp-atlassian": { "type": "stdio", "command": "uvx", "args": [ "mcp-atlassian" ], "env": { "JIRA_URL": "", "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 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "mcp-atlassian": { "command": "uvx", "args": [ "mcp-atlassian" ], "env": { "JIRA_URL": "", "JIRA_USERNAME": "", "JIRA_API_TOKEN": "", "CONFLUENCE_API_TOKEN": "" } } } } ``` 2. Refresh the MCP server list in Cascade. Replace the placeholders with your own values. Devin Desktop is the new name for Windsurf. ### Codex ```bash codex mcp add mcp-atlassian --env "JIRA_URL=" --env "JIRA_USERNAME=" --env "JIRA_API_TOKEN=" --env "CONFLUENCE_API_TOKEN=" -- uvx mcp-atlassian ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.mcp-atlassian] command = "uvx" args = ["mcp-atlassian"] env = { JIRA_URL = "", JIRA_USERNAME = "", JIRA_API_TOKEN = "", CONFLUENCE_API_TOKEN = "" } ``` Needs uv (Python) on your computer. Replace the placeholders with your own values. ### Gemini CLI ```bash gemini mcp add -e "JIRA_URL=" -e "JIRA_USERNAME=" -e "JIRA_API_TOKEN=" -e "CONFLUENCE_API_TOKEN=" mcp-atlassian uvx mcp-atlassian ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients that start local servers accept this shape: ```json { "mcpServers": { "mcp-atlassian": { "command": "uvx", "args": [ "mcp-atlassian" ], "env": { "JIRA_URL": "", "JIRA_USERNAME": "", "JIRA_API_TOKEN": "", "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. ## Details - Server version: 0.23.1 - Last checked: 2026-10-03 - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/mcp-atlassian (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report