Skip to main content
Back to the Atlassian Rovo MCP server

MCP Gateway · OpenCode

Atlassian Rovo icon

Connect Atlassian Rovo to OpenCode

Scripted Jira and Confluence work starts with IDs: the site's cloudId, account IDs and page IDs. From OpenCode, through the Speakeasy MCP Gateway, you can resolve those, assign issues by name and walk a Confluence page tree to build an index. Tool output is blocked at the gateway, and the OpenCode plugin reports token and cost totals per turn.

Category
Project management
Tools
31
Authentication
OAuth
OpenCode
Terminal

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 OpenCode 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. OpenCode connects to the Atlassian Rovo server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect OpenCode

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Atlassian Rovo from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Atlassian Rovo

Resolve the site's cloudId

Before any other call, OpenCode confirms who you are signed in as and gets the cloudId for your Atlassian site, which every Jira and Confluence tool needs.

atlassianUserInfogetAccessibleAtlassianResources

Assign issues to a teammate

Look up a colleague's Jira account ID from their name or email, then edit a batch of issues to make them the assignee.

lookupJiraAccountIdeditJiraIssue

Index a Confluence page tree

OpenCode lists the pages in a space and the child pages under a parent, which is useful when you generate a table of contents or check a docs migration.

getPagesInConfluenceSpacegetConfluencePageDescendants

Tools

31 tools

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

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

Can OpenCode create Jira issues but not edit Confluence?
Yes. You decide which of the 31 Atlassian Rovo tools each team can call at the gateway, so a role can have createJiraIssue without updateConfluencePage.
Does strict egress filtering affect Atlassian Rovo MCP?
It can. If your organization uses strict egress filtering, allow *.atlassian.net. If it uses IP allowlists, ask your network owner to allow Speakeasy requests.
How do OpenCode users get Atlassian Rovo?
An admin adds Atlassian Rovo from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Atlassian Rovo tools their access allows.
Are Atlassian Rovo calls from OpenCode 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.