With the cloud MCP server, you can connect your AI client to mabl without using the mabl CLI. For an overview of server options, see the mabl MCP overview.
Prerequisite
You need an AI client that supports MCP servers, such as Claude Code, Cursor, Windsurf, or Claude Desktop.
Setup
Most AI clients support HTTP connections to remote MCP servers. If your client doesn't support HTTP, the Other tab covers alternative connection methods.
Many AI clients use a JSON configuration file for MCP servers. Use the following config block in a JSON-based MCP configuration:
{
"mcpServers": {
"mabl": {
"url": "https://mcp.mabl.com/mcp",
"type": "http"
}
}
}Type string may vary
Some clients, such as Cursor and Windsurf, use "type": "streamable-http" instead of "type": "http". Check your client’s documentation for the expected type string.
In Claude Code, you can also run the following command in your terminal:
claude mcp add --transport http mabl https://mcp.mabl.com/mcp
Not all clients use JSON configuration. Refer to your AI client’s documentation for specific instructions on adding remote MCP servers.
If your AI client doesn't support HTTP, you can try connecting with SSE or using a stdio bridge.
SSE config
Add the following to your client's MCP configuration:
{
"mcpServers": {
"mabl": {
"type": "sse",
"url" "https://mcp.mabl.com/sse"
}
}
}stdio bridge
If you cannot use HTTP or SSE transport, you can use a package like mcp-remote to bridge between your client's stdio transport and the server's SSE transport. mcp-remote is a third-party open-source package, not maintained by mabl.
Add the following to your client's MCP configuration:
"mabl": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.mabl.com/mcp"
]
}
Authentication
The cloud MCP server uses browser-based OAuth authentication. When you first connect, or when your session expires, your AI client will prompt you to authenticate:
- Open the login URL provided by your client.
- If you aren’t already authenticated, log into mabl using your usual method: username and password, Google auth, or SSO.
Once authenticated, you can start using all of the cloud MCP’s tools. Use the auth_status tool to check your auth session details.
Working in multiple workspaces
By default, the cloud MCP server connects to the primary workspace associated with your mabl user account.
Use the getWorkspaces tool to see all available workspaces. For example:
“What workspaces do I have access to?”
To use the mabl cloud MCP tools in a non-primary workspace, simply provide the name of the workspace or workspace ID when you invoke tools. For example:
“Get my recently created tests from the mabl prod tests workspace.”
Next steps
- mabl MCP tools and prompts — full reference of available tools and sample prompts.
- How to interact with the mabl MCP — best practices for writing effective prompts.