Skip to main content
Back to the Atlassian Rovo MCP server

MCP Gateway · Claude Code

Atlassian Rovo icon

Connect Atlassian Rovo to Claude Code

For teams on Jira, the issue key is often the first thing typed into a branch name. With Atlassian Rovo behind the Speakeasy MCP Gateway, Claude Code can read that issue, move it through the workflow, log time and run JQL searches from the terminal. Agent hooks send each tool call to Speakeasy, which allows or denies it before Claude Code runs it.

Category
Project management
Tools
31
Authentication
OAuth
Claude Code
CLI

Behind the MCP Gateway

Run Atlassian Rovo MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Atlassian Rovo call inspected and logged.

Deploy on MCP Gateway

Before you start

What Atlassian Rovo needs first

An Atlassian organization admin, only if your organization restricts OAuth domains or IP addresses does the Atlassian Rovo side of the setup.

  • You need an Atlassian Cloud site with Jira, Confluence, or Compass.
  • Atlassian documents no paid-plan requirement for the MCP server.
  • No Atlassian-side setup is needed unless your organization restricts OAuth domains, IPs, apps, or egress.

In Atlassian Rovo

  1. In admin.atlassian.com, open Rovo > Rovo MCP server.
  2. If needed, add the Speakeasy callback URL as an allowed domain.
  3. Ask your network owner to allow Speakeasy requests if you use IP allowlists.
  4. Allow *.atlassian.net if you use strict egress filtering.
Full Atlassian Rovo setup guide in the docs

Set up

Add Atlassian Rovo to Claude Code in 4 steps

  1. 01

    Add Atlassian Rovo from the catalog

    An admin finds Atlassian Rovo in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Atlassian Rovo uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Atlassian Rovo

    Give teams the mcp:connect scope on the Atlassian Rovo server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Atlassian Rovo to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Atlassian Rovo from Claude Code

    The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Atlassian Rovo needs its own OAuth grant, so each person connects it once. Until they do, Atlassian Rovo calls fail while the rest of the gateway keeps working.

    From then on, Atlassian Rovo's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Atlassian Rovo

Start work on a Jira issue

Give Claude Code an issue key and it reads the details, checks which transitions the workflow allows, and moves the issue to in progress as you begin.

getJiraIssuegetTransitionsForJiraIssuetransitionJiraIssue

Log time without leaving the shell

When a fix is done, ask Claude Code to add a worklog to the issue for the time spent, or correct an earlier entry instead of creating a duplicate.

addWorklogToJiraIssue

Run a JQL query from the terminal

Ask for every open bug in your component with JQL, then let Claude Code pick the ones that touch the files you're already changing.

searchJiraIssuesUsingJql

Tools

31 tools

Each Atlassian Rovo tool can be allowed or denied per team and role at the MCP Gateway before Claude Code sees it.

atlassianUserInfo

Get current user info

getAccessibleAtlassianResources

Get cloudId to make tool calls. When a link is provided (e.g. https://site.atlassian.net/*), try passing the site hostname (e.g. site.atlassian.net) as cloudId to other tools first; if that fails, use this tool to list accessible resources.

getConfluencePage

Get a Confluence page or blog post by ID, including body content.

searchConfluenceUsingCql

Search content with CQL

getConfluenceSpaces

Get spaces

getPagesInConfluenceSpace

Get pages or blog posts in a space

See all 31 tools

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.

Tool logs

Gateway

Every Atlassian Rovo call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Atlassian Rovo tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Atlassian Rovo can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Does Atlassian need any setup before Claude Code can connect?
Usually not. You need an Atlassian Cloud site with Jira, Confluence or Compass, and no Atlassian-side configuration unless your organization restricts OAuth client domains, IP addresses, third-party apps or network egress.
Can spend on Claude Code be capped while it works in Jira?
Yes. Spend limits can block Claude Code traffic once a budget is reached, whichever server it is calling.
How do Claude Code users get Atlassian Rovo?
An admin adds Atlassian Rovo from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Atlassian Rovo tools their access allows.
Are Atlassian Rovo calls from Claude Code logged?
Yes. Atlassian Rovo calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Atlassian Rovo in other clients

AI everywhere.

Control here.