MCP Gateway · Claude
Connect Atlassian Rovo to Claude
Answers to everyday questions are spread across Jira tickets and Confluence pages. With Atlassian Rovo behind the Speakeasy MCP Gateway, Claude can search both at once, sum up the discussion under a page and raise a Jira issue when something needs fixing. People sign in with their own Atlassian account, so Claude reaches only the sites and apps they already can.
- Category
- Project management
- Tools
- 31
- Authentication
- OAuth
- Claude
- 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 Claude 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. 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. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Atlassian Rovo from Claude
The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Atlassian Rovo
Find an answer across Jira and Confluence
Ask a question in plain language and Claude runs a Rovo Search across both products, then opens the most relevant page or issue to answer from it.
Catch up on a page discussion
Claude reads the footer comments on a Confluence page and the replies under each, and tells you which questions are still waiting for an answer.
Report a problem to the right team
Describe what went wrong and Claude finds the Jira project you can see that fits, then creates the issue with a clear summary and description.
Tools
31 tools
Each Atlassian Rovo tool can be allowed or denied per team and role at the MCP Gateway before Claude 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 Claude
The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Does Claude see Jira projects my Atlassian account can't?
Does a Pro or Max user need an admin to add Atlassian?
How do Claude users get Atlassian Rovo?
Are Atlassian Rovo calls from Claude logged?
Connect more