Skip to content
Status

Atlassian Rovo

Connect Atlassian Rovo so users can access their permitted Jira, Confluence, and Compass work through the hosted MCP server.

You need an Atlassian Cloud site with Jira, Confluence, and/or Compass, and the connecting Atlassian account must have access to the intended site and apps. Use a modern browser. Atlassian documents no paid-plan requirement for the MCP Server.

You need no Atlassian-side configuration unless your organization restricts OAuth client domains, IP addresses, third-party apps, or network egress. For OAuth-domain or IP-allowlist restrictions, sign in to Atlassian Administration with an organization-admin account and complete the applicable checks below. If app-management policy blocks authorization, ask the site admin who owns Marketplace and third-party app policy for help. For strict egress filtering, ask your network/security owner to allow the required Atlassian domain.

Allow the Speakeasy OAuth domain

  1. Open admin.atlassian.com.

  2. If more than one organization is shown, select the organization you want to connect.

  3. Select Rovo.

  4. Select Rovo MCP server.

  5. Check whether the allowed domains cover this hosted OAuth callback:

    https://ai.speakeasy.com/mcp/remote_login_callback

  6. If it is not covered, select Add domain.

  7. Enter this exact custom domain pattern:

    https://ai.speakeasy.com/mcp/remote_login_callback

  8. Use the submission control shown in the console.

Keep Allow Atlassian supported domains selected. Deselecting it blocks Atlassian’s supported-domain set.

If your organization uses IP allowlists, ask your network/security owner to confirm that hosted Speakeasy requests are allowed. Exact hosted outbound IP ranges are not established for this guide; do not guess them.

If your organization uses strict egress filtering, ask your network/security owner to allow the following domain in your organization’s network controls so interactive Jira and Confluence widgets can render:

*.atlassian.net

If Atlassian denies the OAuth redirect during connection, return to Rovo > Rovo MCP server and verify that the client origin matches an allowed domain or pattern. If the authorization screen appears but a tool call returns an IP permission error, update the relevant organization IP allowlist.

Add the server in Speakeasy

  1. In the Speakeasy AI Control Plane sidebar, under MCP Gateway, select MCP.
  2. Click Add new to open Add MCP server.

If an Atlassian Rovo result in the catalog clearly identifies the remote URL shown below:

  1. Choose From the catalog.
  2. On the MCP Catalog page, enter Atlassian in Search MCP servers….
  3. Open that result.
  4. Click Add.
  5. In Add to Project, under Identity, select User Identity.
  6. Click Add to Project. If the dialog offers a Guardrails step, click Skip for now.
  7. After Server added successfully, click Configure MCP settings.

If no such result appears, use the custom remote path:

  1. Choose Hosted remotely.

  2. On New remote MCP server, paste this value into MCP server URL:

    https://mcp.atlassian.com/v2/mcp

  3. Click Verify connectivity.

  4. Under Identity, keep User Identity selected.

  5. Click Save.

On save, Speakeasy discovers Atlassian’s identity provider and registers a client automatically. When that works, the server is ready. When it cannot, the server is kept Disabled and the result says to finish setup in Settings > Identity.

Connect your credentials

Open the server’s Settings and find the Identity section. If creation already configured the identity, User Identity is selected with the Atlassian provider and Auto-Configure; skip to step 6.

  1. Select User Identity.

  2. Under Choose an identity provider, confirm the preselected provider uses this issuer. A provider that does not exist yet shows Will be created.

    https://auth.atlassian.com/VCeDsk8ZHncYF1g234fKtc4lNipbBhu3

  3. If the picker preselects a different provider on auth.atlassian.com, open the picker with Search identity providers… and choose the one for the issuer above.

  4. Keep Auto-Configure selected. There is no Client ID or secret to paste.

  5. Click Save.

  6. If the server shows Disabled, open Settings > Danger Zone > Server Availability and turn on Enable MCP server so it shows Enabled.

When a person first uses the server, Atlassian prompts them in the browser:

  1. Sign in with the intended Atlassian account.
  2. Authorize the intended Atlassian Cloud site.
  3. Enable the intended Atlassian apps.

If organization policy rejects the flow, complete Allow the Speakeasy OAuth domain, then retry the connection.

This guide covers setup only. For anything beyond it — billing, tool behavior, limits — see Atlassian’s MCP documentation.