Skip to main content
Back to the Atlassian Rovo MCP server

MCP Gateway · Claude Cowork

Atlassian Rovo icon

Connect Atlassian Rovo to Claude Cowork

Some Atlassian work takes an afternoon: turning a requirements page into tickets, or writing the sprint review. In Cowork, Claude can carry those multi-step jobs across Jira and Confluence as one task, through the Speakeasy MCP Gateway. Speakeasy checks every prompt before a step runs, and sessions export over OTLP so each run is tied to a named person.

Category
Project management
Tools
31
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork 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 Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Atlassian Rovo from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Atlassian Rovo

Break a requirements page into tickets

Cowork reads a Confluence requirements page, creates a Jira issue for each requirement, and links them to the parent epic or to each other.

getConfluencePagecreateJiraIssuecreateIssueLink

Write the sprint review page

Cowork queries the sprint's finished and carried-over issues with JQL, then writes a Confluence page that groups them by theme for the review meeting.

searchJiraIssuesUsingJqlcreateConfluencePage

Close out stale issues

Cowork finds issues with no activity for months, leaves a comment explaining why each is being closed, and moves it to the done status.

searchJiraIssuesUsingJqladdCommentToJiraIssuetransitionJiraIssue

Tools

31 tools

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

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Does the device agent cover Cowork's Atlassian access?
No. Neither the device agent nor MDM reaches Cowork, so the Claude-side plugin setup always applies. Personal Claude accounts can't be governed in Cowork.
What Atlassian sites can Cowork work with?
Any Atlassian Cloud site with Jira, Confluence or Compass that the connecting Atlassian account can access.
How do Claude Cowork users get Atlassian Rovo?
An admin adds Atlassian Rovo from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Atlassian Rovo tools their access allows.
Are Atlassian Rovo calls from Claude Cowork 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.