Skip to main content

Set up the cloud MCP server

Molly Exten
  • Updated

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

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. 

Working in multiple workspaces

By default, the cloud MCP server connects to the primary workspace associated with your mabl user account. If you aren't sure what your default workspace is, ask your client:

“What is my default workspace?”

To list all available workspaces, use the get_workspaces tool. For example:

“What workspaces do I have access to?”

To use the mabl cloud MCP tools in a non-primary workspace, 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

Related articles