Available Atlassian Rovo MCP server domains

Atlassian MCP server domains includes Atlassian-supported domains and pattern information for the domains you want to add. By default, we automatically allow  Atlassian-supported domains to access apps in your organization. You can add the domains you trust or block Atlassian-supported domains. More about Atlassian Rovo MCP server

Atlassian-supported domains

Patterns for domains you want to add

When you authorize access to Rovo MCP server, you can add a single domain or a flexible pattern.

• Add a single domain — To allow access from that exact location. For example, https://aiagent.mydomain.com or http://localhost:5678.

• Add a pattern — To cover multiple domains, subdomains, ports, or paths. You can define a pattern using wildcards or braces to allow access from a broader set of URLs.

How to add your domains

Domain pattern requirements

To ensure your domain patterns are accepted and secure, follow these rules when creating a pattern:

Always include a protocol

• Every pattern must start with a protocol such as https://, http://, or a custom protocol like cursor://.

• http:// is only valid for localhost or 127.0.0.1 entries.

• Patterns without a protocol will be rejected.

Invalid examples:

• ❌ *.example.com/** (missing protocol)

• ❌ ://example.com/** (empty protocol)

Specify a valid domain or host

• The pattern must include a valid domain, IP address, or host after the protocol.

• Wildcards (*) are allowed in the domain part, but you can't omit the top-level domain entirely.

• For local development, use localhost or 127.0.0.1 as the domain.

Invalid example:

• ❌ https://** (missing domain)

Use a port wildcard (optional)

• You can specify a port in your pattern using a colon followed by a number (for example, :8080) or a wildcard (:** or :*) to match any port.

• This is especially useful for local development or environments where the port may vary.

Valid examples:

• ✅ https://localhost:**

• ✅ http://localhost:*/**

Use a path wildcard (optional)

• You can use a path wildcard (/**) at the end of your pattern to match any path under the domain.

• This allows the pattern to cover all URLs at or below the specified domain.

Valid examples:

• ✅ https://*.example.com/**

• ✅ https://specific.domain.com/**

Use wildcards and braces for flexibility

• You can use * as a wildcard for subdomains or paths.

• Use {} braces to specify multiple allowed subdomains or environments.

• Only the specified environments, dev,staging,prod, can be used as subdomains.

Valid examples:

• ✅ https://{dev,staging,prod}.platform-demo.com/**

• ✅ https://agent-*.saas-demo.com/**

Pattern must be a valid URL structure

• The pattern must be a valid URL format, including protocol and domain.

• Patterns are checked by replacing wildcards with test values to ensure they form a valid URL.