MCP Gateway · ChatGPT
Connect Atlassian Rovo to ChatGPT
Support, HR and operations teams keep policies in Confluence and track escalations in Jira. Through the Speakeasy MCP Gateway, ChatGPT can keep a policy page current, find every page a team published in a period with CQL, and add updates to an escalation ticket. A workspace admin decides which roles get the plugin.
- Category
- Project management
- Tools
- 31
- Authentication
- OAuth
- ChatGPT
- Web, desktop and mobile
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.
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
- In admin.atlassian.com, open Rovo > Rovo MCP server.
- If needed, add the Speakeasy callback URL as an allowed domain.
- Ask your network owner to allow Speakeasy requests if you use IP allowlists.
- Allow *.atlassian.net if you use strict egress filtering.
Set up
Add Atlassian Rovo to ChatGPT in 4 steps
- 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.
- 02
Choose who can use Atlassian Rovo
Give teams the
mcp:connectscope on the Atlassian Rovo server through team access or a role. ChatGPT connects to the Atlassian Rovo server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect ChatGPT
Import the organization's plugin marketplace into the ChatGPT workspace and set who gets each plugin.
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.
Give the importing workspace admin collaborator access to the marketplace repository, and connect their GitHub account in ChatGPT under Plugins > GitHub > Manage.
In ChatGPT, open Admin > Plugins > Add > Import marketplace.
Set each plugin's installation policy, Installed or Available, per role.
Enable the MCP servers the plugin connects to.
- 04
Sign in and use Atlassian Rovo from ChatGPT
The first time ChatGPT 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 ChatGPT, limited to what the person's access allows, and every call lands in the gateway's tool logs.
The marketplace syncs from GitHub once a day. Use Sync now to pick up a change straight away.
Use cases
What ChatGPT users do with Atlassian Rovo
Keep a policy page current
When a policy changes, ChatGPT reads the current Confluence page and updates the affected section, so staff keep working from one source.
List a team's recent pages
Use a CQL search to find every page a team published in a space last month, and get a short digest for the monthly newsletter.
Update a customer escalation
Read the Jira escalation for a customer, then add a comment with what you heard on the call, so engineering has the context without a meeting.
Tools
31 tools
Each Atlassian Rovo tool can be allowed or denied per team and role at the MCP Gateway before ChatGPT 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
Control
What Speakeasy can see and stop in ChatGPT
The gateway covers every client the same way. The rest depends on what ChatGPT 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 ChatGPT. MCP-scoped policies are enabled per organization.
Conversation import
ChatGPT
ChatGPT activity can be imported through OpenAI's Compliance API for review after the fact. It can't block in real time.
- The workspace import needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
Can a support team comment on Jira without editing issues?
How long until a change to the Atlassian plugin shows up in ChatGPT?
How do ChatGPT users get Atlassian Rovo?
Are Atlassian Rovo calls from ChatGPT logged?
Connect more