Skip to main content
Back to the Atlassian Rovo MCP server

MCP Gateway · Codex

Atlassian Rovo icon

Connect Atlassian Rovo to Codex

Codex does its best review work when it can see the ticket the change was written for. With Atlassian Rovo behind the Speakeasy MCP Gateway, Codex can read a Jira issue and its remote links, file a correctly typed bug when it finds one, and publish release notes to Confluence. An [otel] block in Codex's config sends telemetry to Speakeasy, and export stays off until you set it.

Category
Project management
Tools
31
Authentication
OAuth
Codex
CLI and ChatGPT desktop app

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 Codex 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 Codex

    Add the gateway as an MCP server, then log in.

    Run the first command with your organization gateway URL.

    Run the second command to sign in.

    codex mcp add 'speakeasy' \
      --url 'https://<organization host>/mcp/gateway/<organization slug>'
    codex mcp login 'speakeasy'
  4. 04

    Sign in and use Atlassian Rovo from Codex

    The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.

Use cases

What Codex users do with Atlassian Rovo

Check the ticket during review

Codex reads the Jira issue behind a pull request and its remote links, then compares the change with the acceptance criteria written there.

getJiraIssuegetJiraIssueRemoteIssueLinks

File a bug with the right fields

Codex looks up the project's issue types and their required fields before creating the bug, so the issue isn't rejected for a missing component or priority.

getJiraProjectIssueTypesMetadatagetJiraIssueTypeMetaWithFieldscreateJiraIssue

Publish release notes to Confluence

After a release is tagged, Codex finds the team's space and writes the notes as a Confluence page or blog post for people who don't read commit logs.

getConfluenceSpacescreateConfluencePage

Tools

31 tools

Each Atlassian Rovo tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex

The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Codex

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

User attribution

Codex

An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.

Budgets

Codex

Spend limits can block Codex traffic once a budget is reached.

Device agent and MDM

Codex

The device agent keeps Codex's configuration in sync on managed laptops.

  • Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
  • The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.

Questions

Frequently asked questions

Who rolls Atlassian out to a Codex team?
A ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
What if our Atlassian organization uses an IP allowlist?
Ask your network owner to allow Speakeasy requests. An Atlassian organization admin may also need to add the Speakeasy callback URL as an allowed domain under Rovo > Rovo MCP server.
How do Codex users get Atlassian Rovo?
An admin adds Atlassian Rovo from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway as an MCP server, then log in. Each person then sees only the Atlassian Rovo tools their access allows.
Are Atlassian Rovo calls from Codex 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.