Atlassian
Connect your company's Atlassian org so agents work with Jira, Confluence and more through Cakewalk's gateway. One admin step: add Cakewalk's domain to the Rovo MCP server.
Last updated
Was this helpful?
Connect your company's Atlassian org so agents work with Jira, Confluence and more through Cakewalk's gateway. One admin step: add Cakewalk's domain to the Rovo MCP server.
Connect your company's Atlassian organization to Cakewalk's MCP Gateway. Every agent tool call against Jira, Confluence and other Atlassian products passes through the gateway and is evaluated against your Policies.
Atlassian exposes its products through the Rovo MCP server. That server only accepts connections from domains your company trusts. Before employees can connect, an Atlassian admin adds Cakewalk's gateway domain to the trusted list. There are no credentials to create or paste: once the domain is trusted, each employee signs in and approves access, and Atlassian registers Cakewalk automatically.
An Atlassian organization admin who can open Atlassian Administration.
The Rovo MCP server available in your Atlassian org.
Go to Atlassian Administration and select your organization if you have more than one.
In the left sidebar, expand Rovo.
Select Rovo MCP server.
Open the Domains tab.
Leave Allow Atlassian supported domains on. It governs Atlassian's own partner tools and does not cover Cakewalk, so you still add the gateway domain in the next step.
Under Your domains, select Add domain.
In the Domain field, enter this pattern:
Select Add.
The domain now appears under Your domains. Cakewalk's gateway is allowed to connect to your Rovo MCP server.
No credentials change hands. Once the domain is trusted, employees connect themselves:
The Admin enables the Atlassian Connection in Cakewalk.
From an agent platform connected to Cakewalk, an employee signs in to Atlassian and approves access.
Atlassian registers Cakewalk on first connect and issues the access token.
The Atlassian Connection card flips to Active on All Connections. From an agent platform connected to Cakewalk, ask the agent to find a recent Jira issue or a Confluence page. If Atlassian returns results, the Connection is live.
Connection is refused or the sign in is blocked: open the Domains tab on the Rovo MCP server and confirm https://mcp-gateway.getcakewalk.io/** is listed under Your domains.
Domain saved but still blocked: the pattern must end with /**. A bare https://mcp-gateway.getcakewalk.io does not match the gateway paths.
Domain rules apply only to tools connecting through OAuth 2.1. If your Atlassian org is set to API token authentication for the Rovo MCP server, switch the connecting method to OAuth 2.1.
Last updated
Was this helpful?
Was this helpful?
https://mcp-gateway.getcakewalk.io/**