Setting up the mabl MCP server just got easier! With the new cloud MCP server, you can connect your AI client to mabl without going through mabl CLI. The mabl cloud MCP is a more lightweight, centrally managed option for teams looking to manage their testing workflows directly from their IDE or AI workspace.
With the mabl cloud MCP, you can access over 15 tools to query your mabl workspace, run and review test results, and analyze failures. Use natural language prompts to:
- Kick off cloud-based test authoring session
- Run tests ad hoc in the mabl cloud
- Get the latest plan and test run results
- Analyze test failures with GenAI-powered insights
- Check deployment results for your most recent commit
- Map mabl tests to Xray test cases for compliance reporting
Cloud vs. local
The cloud MCP server complements the existing local MCP server. Here’s how they compare:
| Option | Cloud MCP | Local MCP |
|---|---|---|
| Requirements | AI client that supports HTTP type MCP servers | AI client that supports MCP servers, Node.js, and the mabl CLI |
| Capabilities | Cloud-based test authoring and execution, querying workspace data, analyzing test failures | All capabilities of the cloud server, plus local test authoring, execution, and Playwright export |
| Best for | Users who want a more lightweight, centrally managed way to trigger cloud runs and analyze results | Users who want to create, run, and debug tests locally |
Try it out
The cloud MCP server supports two transport methods: HTTP (recommended) and SSE (server-sent events). Add the mabl cloud MCP to your AI client’s configuration to get started:
"mabl": {
"url": "https://mcp.mabl.com/mcp",
"type": "http"
}In Claude Code, the best way to add the mabl cloud MCP is to run this command in your terminal or command prompt:
claude mcp add --transport http mabl https://mcp.mabl.com/mcp
Detailed setup instructions
Configuration may vary across different AI clients. For more detailed configuration and setup suggestions, see the cloud MCP setup docs.
Before you can use the mabl cloud MCP, you'll need to authenticate. The authentication process varies depending on what AI client you're using:
- Client-initiated: Your client may recognize that you aren't logged in and provide a button or prompt to initiate the process.
- User-initiated: If your agent doesn't automatically prompt you to authenticate, use a prompt like "Help me authenticate the mabl MCP" to initiate the process.
The cloud MCP will open a browser window to a consent page. Review the details and click Accept. At this point, if you aren't already logged into the mabl web app, you'll also need to sign in to mabl.
Once logged in, you can start querying test results, triggering ad hoc runs, and investigating failures. For example:
"Create a browser test for the checkout flow on the Shopbricks app." → "What's the status of that test?" → "Run it against the staging environment."
“What applications do I have in mabl?” → “Show me the tests for the Admin Dashboard.” → “Get me the latest results for the login test.”
“What happened with my previous mabl deployment?” → “Show me the test runs from that deployment.” → “Which tests failed?”