# Jira MCP server: Atlassian's MCP for Jira and Confluence

> Atlassian's official MCP server for Jira and Confluence: the v2 address, setup in Claude Code, Cursor and Codex, tools, admin settings, Data Center, and Upsy.

Updated 2026-11-02 · https://upsy.ai/guides/jira-mcp-server

## Short answer

Atlassian runs an official MCP server (a connector that lets an AI agent use your Atlassian apps) for Jira, Confluence and more of its Cloud apps. It's called the Atlassian MCP server, formerly the Atlassian Rovo MCP server, and the current address is `https://mcp.atlassian.com/v2/mcp`. Add it to your client, sign in to Atlassian and pick a site. In Claude Code:

```
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
```

Then run `/mcp` to sign in. It works with Atlassian Cloud only; for Jira Data Center or Server, use a community server such as [sooperset/mcp-atlassian](https://github.com/sooperset/mcp-atlassian). Your Atlassian admin decides which tools may connect and whether they may write. Add Atlassian through Upsy if you want limits for each agent, several sites in one connection, or a history of what every agent did.

## Atlassian's MCP server

| | |
|---|---|
| Address | `https://mcp.atlassian.com/v2/mcp` (Streamable HTTP) |
| Older address | `https://mcp.atlassian.com/v1/mcp`, still supported. Atlassian said the old SSE address would stop being supported after June 30, 2026 |
| Sign-in | OAuth 2.1 with dynamic client registration. If an admin allows it, a personal API token or a service account key instead |
| Sites | One per OAuth sign-in, picked on Atlassian's consent screen |
| Plans | Any Atlassian Cloud site. Not Data Center or Server |
| Cost | Lookups and changes in one app are free. Cross-app searches and Teamwork Graph context cost 1 to 10 Rovo credits a call ([Rovo usage](https://support.atlassian.com/rovo/docs/rovo-usage-limits/)) |
| Record | Every tool call is in your organization's audit log |

Atlassian's [getting-started page](https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/) has the details. The server left beta on February 4, 2026.

### v1 and v2

Atlassian released v2 by September 2026 and presented it at Team '26 Europe in October with "220+ tools" ([Atlassian](https://www.atlassian.com/blog/company-news/team26-europe-atlassian-mcp)). What changed:

- **More apps:** besides Jira and Confluence, Jira Service Management, Bitbucket Cloud, Loom, Assets, Goals, Projects, Teams, Focus, Talent, Capacity Planning, Jira Align, Rovo search and code search. Compass isn't in v2.
- **Tools on demand.** v2 loads a few main tools and finds the rest with `discover`, then runs them with `executeRead`, `executeWrite` or `executeDestructive`. v1 loaded 32 tool definitions up front; v2 loads 6 for Jira, and Atlassian says it saves up to 25% of tokens ([Atlassian](https://www.atlassian.com/blog/how-we-build/jira-depth-on-demand)).
- **Renamed tools,** such as `getConfluencePage` to `getConfluenceContent` and `addCommentToJiraIssue` to `addOrEditJiraIssueComment`.
- **A new sign-in.** v2 is a separate OAuth resource, so v1 sign-ins don't carry over ([upgrade guide](https://support.atlassian.com/atlassian-ai-gateway/docs/how-to-upgrade-from-atlassian-mcp-v1-to-atlassian-mcp-v2/)).

"On March 1, 2027 any existing utilization of v1 will automatically start to expose and utilize v2 tools." Some clients will then have to clear their saved sign-in.

### Connect it to your client

**Claude Code.** Run the command above, then `/mcp`. Atlassian also publishes a Claude Code plugin in its [repository](https://github.com/atlassian/atlassian-mcp-server).

**Claude.** Add **Atlassian MCP** from the connector directory; it's made by Atlassian. A connector added before v2 shows as a custom web connector and needs adding again.

**Cursor.** Install Atlassian from [Cursor's marketplace](https://cursor.com/marketplace/atlassian), or add `{"mcpServers":{"atlassian":{"url":"https://mcp.atlassian.com/v2/mcp"}}}` to `mcp.json`.

**VS Code and GitHub Copilot.** In the Extensions view, search `@mcp Atlassian` and click **Install**.

**Codex.** Run `codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp`. In the Codex desktop app, find Atlassian under **Plugins** or **Connectors**.

**ChatGPT.** Use the Atlassian Rovo app, which Atlassian launched in December 2025.

**Windsurf.** Under **Cascade › MCP servers**, add a custom server with `"serverUrl": "https://mcp.atlassian.com/v2/mcp/"`.

**Scripts and headless agents.** Once an admin turns on API tokens, send `Authorization: Basic` with your email and API token, Base64-encoded, or `Authorization: Bearer` with a service account key ([API token setup](https://support.atlassian.com/atlassian-ai-gateway/docs/configure-authentication-via-api-token/)).

### Its tools

Atlassian lists every tool on its [supported tools page](https://support.atlassian.com/atlassian-ai-gateway/docs/supported-tools/). Jira alone has 52 in v2. The ones agents use most:

| App | Main tools |
|---|---|
| Jira | `getJiraIssue`, `searchJiraIssuesUsingJql`, `createJiraIssue`, `editJiraIssue`, `transitionJiraIssue`, `addOrEditJiraIssueComment`, `listJiraIssueComments` |
| Confluence | `getConfluenceContent`, `searchConfluence` (CQL), `createConfluenceContent`, `updateConfluenceContent` |
| Across apps | `search` (Rovo search), `atlassianUserInfo`, `getAccessibleAtlassianResources`, Teamwork Graph context |
| Finding the rest | `discover`, `executeRead`, `executeWrite`, `executeDestructive` |

- **Deletes are off by default.** Jira's delete tools (issues, comments, attachments) and its project and workflow tools stay off until an admin enables them. Confluence has no delete tool; pages can only be archived.
- **Search languages:** JQL for Jira and Jira Service Management, CQL for Confluence, AQL for Assets, and plain language for Rovo search.
- **Some tools need more:** Bitbucket needs the workspace linked to your organization, Loom needs it linked to a site, and code search, Teams and Jira Align work only with OAuth.

### What your admin controls

An organization admin manages the server under **Atlassian Administration › Connectors › Atlassian MCP server** ([admin settings](https://support.atlassian.com/security-and-access-policies/docs/control-atlassian-mcp-server-settings/)):

- **Domains.** **Allow Atlassian supported domains** lets in Atlassian's list of clients, such as Claude, ChatGPT, Cursor, VS Code and local apps on `localhost`. You can't block one of them on its own, but you can add custom domains.
- **Permissions.** Read, Write and Search, on or off for each app, effective right away.
- **Authentication.** Whether API tokens and enterprise-managed sign-in through Okta or Claude are allowed.
- **IP allowlists** apply to OAuth and tokens alike. A hosted client like Claude connects from its provider's servers, so your VPN doesn't help.
- **Audit log.** Under **Insights › Audit log**, filter for "Atlassian MCP User Actions" to see every tool call.

There's no single off switch. To block MCP, admins combine these settings ([how to](https://support.atlassian.com/security-and-access-policies/docs/prevent-atlassian-mcp-server-access/)).

### Where Atlassian's server stops

- **Cloud only.** Data Center and Server need a community server.
- **One site per sign-in.** For a second site, sign in again under a second server entry.
- **Limits are for the whole organization.** The admin's Read, Write and Search settings apply to every client. Anything narrower, like comments but no edits, depends on each client's own settings.
- **Rate limits aren't published.** The server sends `X-RateLimit` headers, and users report 429 errors at about 20 parallel calls ([issue #171](https://github.com/atlassian/atlassian-mcp-server/issues/171)).
- **Rovo credits.** Cross-app searches draw from your organization's Rovo credits, and extra usage is billed from December 3, 2026.

For one site and clients on Atlassian's list, Atlassian's server is enough.

## Jira MCP servers compared

| | Atlassian MCP server | Upsy | sooperset/mcp-atlassian |
|---|---|---|---|
| Who runs it | Atlassian | Upsy, on top of Atlassian's server | You, on your machine or server |
| Jira editions | Cloud | Cloud | Cloud, Server and Data Center |
| Sign-in | OAuth, or an API token | OAuth to Upsy; Upsy signs in to Atlassian | API token, personal access token or OAuth |
| Limits | Read, Write and Search for the whole organization | Read-only, picked tools, or everything, per agent | `READ_ONLY_MODE` and `ENABLED_TOOLS` |
| Sites | One per sign-in | Up to 5 in one server | One per configuration |
| Record | The organization's audit log | History and alerts | Your own logs |

### Community servers and Data Center

- **[sooperset/mcp-atlassian](https://github.com/sooperset/mcp-atlassian)** is the popular one, with about 6,000 stars and 98 tools. It covers Jira 8.14+ and Confluence 6.0+ on Server and Data Center as well as Cloud. It runs with `uvx mcp-atlassian` or the Docker image `ghcr.io/sooperset/mcp-atlassian`. Docker's `mcp/atlassian` image is built from it. `READ_ONLY_MODE=true` turns off every change.
- **[b1ff/atlassian-dc-mcp](https://github.com/b1ff/atlassian-dc-mcp)** is for Data Center only, covering Jira, Confluence and Bitbucket.
- **aashari/mcp-server-atlassian-jira** works with Jira Cloud through five generic tools that call the API directly, delete included.

### Rovo as an MCP client

Since February 2026, Rovo, Atlassian's own AI, can use other MCP servers ([Atlassian's docs](https://support.atlassian.com/organization-administration/docs/add-an-external-mcp-server-from-atlassian-administration/)). An admin adds one under **Apps › Sites › Connected apps › Add external MCP server**. It needs Streamable HTTP and OAuth 2.1 with dynamic client registration.

## Upsy's Jira MCP server

Upsy connects to Atlassian's MCP server with your Atlassian sign-in. It's the same address as Upsy's other apps, `https://upsy.ai/connect`, so one server also holds your Gmail, Slack, Linear and more.

Upsy uses Atlassian's v1 address today, so agents get v1's tools: Jira issues, JQL search, transitions and comments, Confluence pages, CQL search and comments, and Rovo search. Atlassian moves v1 connections to v2's tools on March 1, 2027.

What it adds:

- **Limits per agent.** **Read-only**, **Pick actions** (the tools you tick) or **Full access**, set for each agent, on top of your admin's settings. Upsy refuses the rest on its side.
- **Up to five Atlassian sites** in one server, each with its own access.
- **History and alerts:** every Jira and Confluence tool an agent runs, refused attempts included, listed under that agent.
- **Any client:** Claude, Claude Code, Cursor, Codex, ChatGPT, Grok, Muse, or anything with remote MCP and OAuth.

Upsy isn't on Atlassian's list of supported domains. If your organization limits domains, an admin adds `https://upsy.ai/**` as a custom domain. With an IP allowlist, they allow Upsy's servers, since requests come from Upsy.

### Connect Atlassian to Upsy

1. Go to [upsy.ai](https://upsy.ai) and click **Set up Upsy**.
2. Open **Apps**, click **Connect an app** and pick **Atlassian**. Sign in and choose the site on Atlassian's consent screen. For another site, click **Add account** next to Atlassian.
3. On the **Assistants** page, click **Add assistant** and choose your client under **Which assistant?** for its exact steps.

### Add the server to your client

Signing in opens an Upsy page: tick Atlassian, keep full access or pick **Read-only**, and click **Allow**. To allow only some actions, use **Pick actions** on the agent's page afterwards.

- **Claude Code:** `claude mcp add --transport http --scope user upsy https://upsy.ai/connect`, then `/mcp` to sign in.
- **Cursor:** add `{"mcpServers":{"upsy":{"url":"https://upsy.ai/connect"}}}` to `~/.cursor/mcp.json`, then click **Connect** next to upsy.
- **Codex:** `codex mcp add upsy --url https://upsy.ai/connect`, then `codex mcp login upsy`.
- **Claude and ChatGPT:** add `https://upsy.ai/connect` as a custom connector ([Claude](/guides/claude/custom-connector), [ChatGPT](/guides/chatgpt/custom-connector)).
- **Grok and Muse:** paste the setup prompt Upsy shows into a chat and approve the sign-in ([Grok](/guides/grok/jira), [Muse](/guides/muse/jira)).

Server details, such as OAuth endpoints and token lifetimes, are in the [Gmail MCP server guide](/guides/gmail-mcp-server#server-details); they're the same for Atlassian.

### Check that it works

> Using Upsy, list my open Jira issues, highest priority first, then find the Confluence page about our release process.

The agent should list issues with keys such as PROJ-142, then name the page. Both calls show in Upsy's **History** under that agent.

### Picking Atlassian tools

With **Pick actions**, a sensible start is the search and read tools plus `addCommentToJiraIssue` and `transitionJiraIssue`, so an agent can report on work, comment and move issues along, but not create or edit them. Tick `createJiraIssue` and `editJiraIssue` when it should file and change issues. A tool Atlassian adds later, including v2's, stays off until you tick it.

## Troubleshooting

### "Access denied: Your organization admin has not authorized the write permission"

Write is off for your organization or this app. An admin turns it on under **Connectors › Atlassian MCP server › Permissions**. Changes apply right away.

### "Access denied: Your organization admin must authorize access from [redirect URI]"

Your client isn't on the allowed domains. An admin adds its address as a custom domain under **Connectors › Atlassian MCP server › Domains**, or turns on **Allow Atlassian supported domains** for clients on Atlassian's list.

### "You don't have permission to connect from this IP address"

Your site uses an IP allowlist. Requests come from the client's servers, such as Claude's or Upsy's, not your laptop. An admin has to allow those addresses.

### "You don't have permission to connect via API token"

API tokens are off. An admin turns them on under **Connectors › Atlassian MCP server › Authentication**, or you sign in with OAuth instead.

### "The app is not installed on this instance"

The saved sign-in no longer matches the site. Disconnect the server in your client and connect again.

### Tools stopped working after moving to v2

v2 needs its own sign-in, and some tool names changed. Remove the v1 entry, add `https://mcp.atlassian.com/v2/mcp`, and sign in again.

### 429 errors during a big report

You hit Atlassian's rate limit. Narrow the request to one project or sprint, and ask the agent for fewer calls at once.

### "The user hasn't allowed you to use Atlassian's …"

That's Upsy refusing a tool outside the agent's level, such as `createJiraIssue` on Read-only. Change Atlassian's level on the agent's page in Upsy.

## Security and privacy

- **Every option acts as you,** with your Jira and Confluence permissions, on top of your admin's settings.
- **Atlassian logs every call** in the organization's audit log, whichever client made it.
- **API tokens** aren't tied to one site and skip the domain allowlist; only the IP allowlist applies. Treat them like passwords, and prefer service account keys for scripts.
- **Through Upsy,** agents never get your Atlassian token: they call Upsy, and Upsy calls Atlassian. Upsy emails you when one agent reads 100 or more items in 10 minutes or deletes 50 or more, and when a new agent or app connects.
- **Prompt injection.** An issue, comment or page can carry instructions aimed at your agent. Keep changes confirmed in your client, or give agents that read public tickets Read-only.

## FAQ

### Is there an official Jira MCP server?

Yes. Atlassian runs the Atlassian MCP server for Jira, Confluence and its other Cloud apps, at `https://mcp.atlassian.com/v2/mcp`.

### What's the difference between v1 and v2?

v2 covers more Atlassian apps, loads tools on demand instead of all at once, and renames some tools. It needs a new sign-in. v1 still works, and moves to v2's tools on March 1, 2027.

### Is the Jira MCP server free?

The server itself is. Looking up and changing things in one app is free; cross-app searches and Teamwork Graph context cost 1 to 10 Rovo credits a call, from your organization's allowance.

### Does it work with Jira Data Center?

No, Atlassian's server is for Cloud only. Use sooperset/mcp-atlassian, or b1ff/atlassian-dc-mcp, on your own machine or server.

### Can the Jira MCP server delete issues?

Only if an admin enables Jira's delete tools, which are off by default. Confluence pages can be archived, not deleted.

### Does it cover Confluence?

Yes. The same server reads, searches, creates and updates Confluence pages and comments, within your permissions.

### How do I use the Jira MCP server with Codex?

Run `codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp` and sign in, or install Atlassian from Plugins in the Codex desktop app.

### Can I connect two Atlassian sites?

Yes, with a separate sign-in for each: two server entries in your client, or two accounts in one Upsy server.

---

Upsy connects personal AI assistants (Muse, Grok, ChatGPT, Claude, Cursor, Claude Code, Codex, Devin) to your Gmail, Google Calendar, Google Drive, Slack, Notion and other apps through one MCP server, with a shared memory, files and a cloud browser signed in to your sites. You choose what each assistant may do in each app, see everything it did, and turn it off in one click. Upsy is free. To add Upsy to an assistant, add a remote MCP server (Streamable HTTP) named Upsy at https://upsy.ai/connect. It signs in with OAuth; there is no API key.