Out-of-the-box third-party MCP agents
Nine out-of-the-box Rovo agents powered by third-party Model Context Protocol (MCP) servers are available in Confluence and Jira. These agents connect Rovo to external services like design tools, analytics platforms, CRM systems, and more — letting you work with third-party data directly from your Atlassian products.
Each agent uses a vendor-provided MCP server for tool invocation, with Rovo acting as the LLM layer. An admin must enable each agent's MCP server before end users can access it.
Admin setup required: A site admin must enable each agent's MCP server in Admin Hub before end users can access it. For full setup instructions, see Add an external MCP server from Atlassian administration.
Before enabling any agent, review the Rovo OOTB MCP agents usage guidelines to understand data handling and permissions.
Available OOTB agents
The following agents are available. Most have GA (generally available) MCP servers. Replit and Lovable have Beta MCP servers — you may experience instability or limited functionality with these agents.
Agent | What it does | MCP server status |
|---|---|---|
Figma | Access and work with Figma design files |
|
Canva | Create and manage visual content in Canva |
|
Box | Manage and retrieve documents stored in Box |
|
Amplitude | Query and analyze product analytics data |
|
HubSpot | Access CRM data and manage sales workflows |
|
Intercom | Access customer messaging and support data |
|
Gamma | Generate and work with presentations |
|
Replit | Generate and run code in Replit |
|
Lovable | Prototype and build apps with Lovable |
|
Beta MCP servers: The Replit and Lovable agents use MCP servers that are currently in Beta. Atlassian Support can help with access issues but has limited ability to resolve Beta-specific bugs.
Before you begin
You need a Rovo Premium or Enterprise plan.
A site admin must enable each agent's MCP server in Rovo Admin Hub.
You need a third-party account for the relevant service (for example, a Figma account to use the Figma agent).
Before enabling any agent, review the Rovo OOTB MCP agents usage guidelines to understand data handling and permissions.
Set up and use an agent
To enable an OOTB third-party MCP agent, a site admin adds and configures the agent's MCP server in Admin Hub. Once enabled, end users can access the agent in Rovo from both Confluence and Jira.
For step-by-step setup and usage instructions, see Add an external MCP server from Atlassian administration.
Known limitations
The following agents have known limitations as of April 2026:
Replit, Gamma & Lovable: App Content may not render via Atlassian smart links.
Beta agents
Lovable (beta): The partner is transitioning to a new MCP server. The current server is being deprecated. The new server may not be available to all customers yet.
Troubleshooting
Issue | Solution |
|---|---|
Agent not visible to users | Confirm that a site admin has enabled the MCP server toggle in Rovo Admin Hub. See Add an external MCP server from Atlassian administration. |
Authentication failure | Re-authenticate via the third-party service. If the error is intermittent, retry after a few moments. |
Replit or Lovable errors or instability | These agents use Beta MCP servers. This is a known limitation. Retry the action. If the issue persists, contact Atlassian Support. |
Replit, Lovable OR Gamma content not loading via smart links | Private app’s content is not supported via OAuth smart links. Use the external app directly to view private content. |
MCP server in a bad state or persistent connection issues | Ask your site admin to de-register and then re-register the MCP server from Rovo Admin Hub. This resets the connection and can resolve persistent authentication or connectivity issues. |
Related resources
Was this helpful?