# Atlassian Rovo (Jira & Confluence) MCP server
> Search, create and update Jira issues and Confluence pages in Atlassian Cloud from your AI assistant.
- Listing: https://mcp.tc/i/atlassian
- Connect: use the server's own URL `https://mcp.atlassian.com/v2/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Productivity & Projects](https://mcp.tc/c/productivity)
- Vendor: Atlassian
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage:
- Docs:
- Repository:
## About
Connects an AI assistant to an Atlassian Cloud site. You can search and summarize Jira work items and Confluence pages, create or update them from natural language, and turn meeting notes or specs into work items. The README also lists Jira Service Management, Bitbucket, Compass and Loom.
It runs as a hosted streamable HTTP endpoint at https://mcp.atlassian.com/v2/mcp. Users sign in with OAuth 2.1, or with API tokens, and actions follow their existing Atlassian permissions. Nothing is installed locally unless a client needs the mcp-remote proxy.
## What it can do
- Search and summarize Jira work items
- Create and update Jira issues from natural language
- Search and read Confluence pages
- Create and update Confluence pages
- Work with Jira Service Management, Bitbucket and Compass
- Retrieve Loom recordings
- Generate work items from meeting notes or specs
## Example prompts
- "Summarize the open Jira issues assigned to me this sprint"
- "Create a Jira task for fixing the login timeout bug"
- "Find the Confluence page about our release process"
- "Turn these meeting notes into Jira work items"
## Install
### Claude Code
1. Run this in a terminal, in your project folder:
```bash
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
```
2. Start Claude Code, type `/mcp`, pick **atlassian** and choose **Authenticate**. A browser window opens for the Atlassian sign-in.
Add `--scope user` to make it available in every project, not just this one.
### Claude Desktop
1. Open **Settings → Connectors** and click **Add custom connector**.
2. Name it **Atlassian Rovo (Jira & Confluence)** and paste this URL:
```url
https://mcp.atlassian.com/v2/mcp
```
3. Click **Add**, then **Connect**, and sign in when Atlassian asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
### claude.ai
1. Open the connector form on claude.ai. This button fills in the name and URL for you:
[Add to claude.ai]() (opens connector settings)
2. Check that the URL reads `https://mcp.atlassian.com/v2/mcp` and click **Add**.
3. Click **Connect** and sign in when Atlassian asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.
### ChatGPT
1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.
2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.
3. Paste `https://mcp.atlassian.com/v2/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Atlassian to sign in.
Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.
### 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": {
"atlassian": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
```
Cursor shows **Needs login** next to the server. Click it to sign in.
### VS Code
[Install in VS Code]() (opens VS Code)
Or from a terminal:
```bash
code --add-mcp '{"name":"atlassian","type":"http","url":"https://mcp.atlassian.com/v2/mcp"}'
```
Or commit it to the repo in `.vscode/mcp.json`:
`.vscode/mcp.json`:
```json
{
"servers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
```
VS Code asks you to sign in the first time the server starts.
### 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": {
"atlassian": {
"serverUrl": "https://mcp.atlassian.com/v2/mcp"
}
}
}
```
2. Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.
### Codex
```bash
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp
codex mcp login atlassian
```
Or edit `~/.codex/config.toml` directly:
`config.toml`:
```toml
[mcp_servers.atlassian]
url = "https://mcp.atlassian.com/v2/mcp"
```
### Gemini CLI
```bash
gemini mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
```
Then, inside Gemini CLI, run `/mcp auth atlassian` to sign in.
This adds it to the current project. Add `-s user` to use it everywhere.
### Any client
Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.
```json
{
"mcpServers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
```
Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.
Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.atlassian.com/v2/mcp`.
## Details
- Server version: 2.0.0
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03
---
Source: https://mcp.tc/i/atlassian (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report