When a test fails in mabl, you jump to Jira to file a ticket. When a new requirement lands in Confluence, you switch to mabl to create the coverage. Either way, context gets lost in the handoff.
You can now close that gap by connecting the mabl MCP to an Atlassian Rovo agent. With a mabl Rovo agent, your team can query mabl test data and trigger mabl actions from inside the Jira and Confluence tools you already use.
Here are some ways you can use the mabl Rovo agent:
- Turn test failures into actionable Jira tickets, complete with root cause analysis and remediation steps.
- Spot coverage gaps by cross-referencing Jira ticket data against mabl test metadata.
- Translate natural-language requirements from a Jira ticket or Confluence page directly into a new mabl test.
How it works
Setup happens in two stages:
-
Add the mabl MCP server to your Atlassian site. An Atlassian organization admin adds mabl as a custom MCP server under Connected apps, using
https://mcp.mabl.com/mcpas the URL. Once connected, admins can control which mabl tools Rovo has access to. - Create a Rovo agent with mabl skills. Give the agent a name, description, and instructions, then add mabl under MCP servers and choose the tools the agent can use.
From there, open Rovo Chat and select your mabl agent, or mention @agent-name to bring it into a specific Jira or Confluence work item.
Learn more
- Integrate the mabl MCP with Atlassian Rovo: full setup guide with step-by-step walkthrough
- mabl cloud MCP tools: available tools in the mabl cloud MCP