Atlassian (Jira/Confluence) MCP Server
Connect Jira, Confluence, and Jira Service Management to your AI agents via Atlassian's official remote MCP server.
Updated
What is Atlassian (Jira/Confluence) MCP?
The Atlassian MCP server is a Model Context Protocol server that securely connects Jira, Confluence, and Jira Service Management to your LLM, IDE, or agent platform of choice. Officially built and operated by Atlassian (branded the "Rovo MCP Server"), it lets an AI agent search, read, create, and update Atlassian work items and pages using natural language.
It is a remote, Atlassian-hosted service — you connect to it at https://mcp.atlassian.com/v1/mcp rather than running or self-hosting anything yourself. Authentication uses OAuth 2.1: the first time a client connects, you complete a browser-based consent flow that grants the agent access only to the Atlassian Cloud data your account can already see. (Admins can optionally enable scoped API tokens for non-interactive, machine-to-machine use.)
Because access is gated by your existing Atlassian permissions and project/space roles, the agent never sees more than the authorizing user does. Tools are grouped by intent (read, write, search) across Jira, Confluence, and JSM, so an agent can summarize a Confluence space, triage Jira issues, or act on JSM alerts without leaving its host application.
Tools the Atlassian (Jira/Confluence) MCP server exposes
| Tool | What it does |
|---|---|
| searchJiraIssuesUsingJql | Search Jira issues with a JQL query. |
| getJiraIssue | Fetch the full details of a single Jira issue. |
| createJiraIssue | Create a new Jira issue. |
| editJiraIssue | Update fields on an existing Jira issue. |
| transitionJiraIssue | Move a Jira issue through its workflow (e.g. to Done). |
| addCommentToJiraIssue | Add a comment to a Jira issue. |
| searchConfluenceUsingCql | Search Confluence content with a CQL query. |
| getConfluencePage | Retrieve a Confluence page by ID. |
| createConfluencePage | Create a new Confluence page. |
| updateConfluencePage | Update the body or metadata of a Confluence page. |
| getJsmOpsAlerts | List Jira Service Management operations alerts. |
| updateJsmOpsAlert | Update a JSM operations alert. |
Connect the Atlassian (Jira/Confluence) MCP server
Claude Code
- 1
Add the server
Run: claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp
- 2
Authenticate
Run /mcp in a Claude Code session and complete the OAuth browser consent flow with your Atlassian account.
- 3
Use it
Ask Claude to search Jira, summarize a Confluence space, or create an issue — it will call the Atlassian tools automatically.
Requires Atlassian Cloud. The agent only accesses data your account can already see.
Cursor
- 1
Add the MCP server
In Cursor Settings > MCP > Add new MCP server, configure a remote server with URL https://mcp.atlassian.com/v1/mcp (HTTP transport). Clients without native remote support can proxy via npx mcp-remote https://mcp.atlassian.com/v1/mcp.
- 2
Authenticate
On first connection, Cursor opens the OAuth 2.1 browser flow — approve access for your Atlassian Cloud site.
- 3
Verify
Confirm the Atlassian tools appear in Cursor's MCP tool list, then prompt the agent to query Jira or Confluence.
Steps are accurate as of mid-2026; check Atlassian's docs for client-specific quick-install links.
Sample use cases
Automated Jira triage on a schedule
A Gamut agent queries open issues with JQL each morning and posts a prioritized summary, flagging unassigned or stale tickets.
Turn meeting notes into Confluence + Jira
An agent drafts a Confluence page from raw notes and creates linked Jira issues for the action items.
Incident-driven JSM alerting
On an event trigger, an agent reads JSM ops alerts and updates their status as the situation is resolved.
Security & permissions
Authentication is OAuth 2.1: connecting a client triggers an interactive browser consent flow, and the agent is granted access only to the Atlassian Cloud data your account can already view. All actions respect existing project and Confluence space-level roles and permissions — the MCP server does not elevate access. Tools are organized into read / write / search permission groups per product (Jira, Confluence, JSM), so you can reason about what an agent can do. For non-interactive scenarios (CI/CD, bots, backend services), org admins can optionally enable scoped API-token authentication. Because the server is Atlassian-hosted, no Atlassian credentials are stored on your machine beyond the OAuth token your client manages.
Using Atlassian (Jira/Confluence) MCP with Gamut
In a Gamut workflow, the Atlassian MCP server becomes a tool your agent calls on a schedule or in response to an event — Gamut manages the OAuth connection so the agent can act without manual auth each run. For example, a daily-triggered agent can call searchJiraIssuesUsingJql to pull stale or unassigned issues and post a triage summary, or an event-triggered agent can take an incoming spec, createConfluencePage for the design doc, and createJiraIssue for the resulting tasks. All actions stay within the permissions of the connected Atlassian account.
Frequently asked questions
What is the Atlassian MCP server?
It is Atlassian's official remote Model Context Protocol server (the Rovo MCP Server) that connects Jira, Confluence, and Jira Service Management to AI agents and IDEs. It exposes read, write, and search tools so an agent can query and update Atlassian content using natural language, hosted by Atlassian at https://mcp.atlassian.com/v1/mcp.
Is the Atlassian MCP server free?
Yes — the MCP server itself has no separate fee and works with any Atlassian Cloud account, respecting your existing permissions. Some AI/Rovo features consume Rovo credits that are bundled into Jira, Confluence, and JSM plans, with allowances that vary by plan tier.
Is the Atlassian MCP server hosted or self-hosted?
It is hosted by Atlassian. You connect to the remote endpoint at https://mcp.atlassian.com/v1/mcp rather than running or self-hosting a server. (Community-built self-hosted alternatives exist, but the official server is cloud-hosted.)
How do I connect the Atlassian MCP server to Claude Code or Cursor?
For Claude Code, run `claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp`, then `/mcp` to authenticate. For Cursor, add a remote MCP server with the same URL (or proxy via `npx mcp-remote`). Both complete an OAuth 2.1 browser consent flow on first connection.