-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Admin - Settings - Rovo
-
None
Issue Summary
Currently, the Rovo MCP Server's custom domain allowlist enforces a hard limit of 20 entries. Organizations that need granular control over which external MCP client domains can connect, rather than enabling the blanket "Allow all Atlassian supported domains" toggle are blocked from adding additional tools once this ceiling is reached.
This limit does not account for the growing ecosystem of MCP-compatible AI tools, multi-site organizations, or enterprises with strict information security policies requiring explicit domain-level approval rather than broad allow-all configurations.
Customer Use Case
Customers managing MCP client connections through the Rovo MCP Server Admin console need to:
- Control domain access at a granular level —> infosec policies prohibit enabling "Allow all Atlassian supported domains," requiring each external tool domain to be explicitly approved and auditable
- Support a growing number of AI tool integrations —> as the MCP ecosystem expands (Cursor, VS Code, n8n, AWS QuickSight, internal tools, etc.), 20 entries is quickly exhausted, especially when wildcard consolidation has already been applied
- Manage multi-site organizations —> large enterprises with multiple Atlassian sites, internal hosts, and tool environments require more entries than a single-site customer, yet face the same limit
- Avoid choosing between security and functionality —> today, customers who exceed 20 domains must either relax their security posture (enable all domains) or forgo connecting additional MCP tools, creating a forced trade-off between compliance and productivity
Currently, customers must resort to wildcard pattern consolidation (e.g., http://localhost:*/** instead of multiple localhost entries) to stay under the limit. While wildcards help, they are not always feasible due to distinct vendors, protocols, and internal hostnames often cannot be collapsed without over-permitting access.
Expected Results
The Rovo MCP Server should:
- Increase the custom domain limit significantly → a ceiling of 50-100 entries (or removal of the hard cap entirely) would accommodate enterprise-scale deployments without forcing customers into an all-or-nothing security posture
- Provide clear feedback when approaching the limit → surface a warning in the Admin console as organizations approach the cap, with guidance on wildcard consolidation strategies before they hit the wall
- Document the limit and wildcard syntax → the 20-domain limit is not currently documented in admin-facing materials; customers discover it only upon hitting the error, which erodes trust in the platform's scalability
- Consider domain grouping or tagging → allow admins to organize allowed domains by category (e.g., "IDE tools," "internal hosts," "cloud services") for easier management at scale, without each logical group consuming individual slots
- If the limit cannot be increased, provide official guidance on wildcard best practices and document which MCP client patterns can be safely consolidated, so customers can make informed decisions about their domain configuration strategy