Set up the cloud MCP server

Config

Many AI clients use a JSON configuration file for MCP servers. Use the following config block:

{
  "mcpServers": {
    "mabl": {
      "url": "https://mcp.mabl.com/mcp",
      "type": "http"
    }
  }
}

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.

After adding the server, complete authentication through a browser consent flow:

• 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. 

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.”

Config

API key setup authenticates your connection directly. Use the following config block, replacing YOUR_API_KEY_HERE with either an "Editor" or "Viewer" type mabl API key:

{
  "mcpServers": {
    "mabl": {
      "url": "https://mcp.mabl.com/mcp",
      "headers": {
        "x-api-key": "YOUR_API_KEY_HERE"
      }
    }
  }
}

In Claude Code, you can also run:

claude mcp add --transport http mabl https://mcp.mabl.com/mcp --header "x-api-key: YOUR_API_KEY_HERE"

If your config file will be checked into version control or shared with others, reference the key from an environment variable instead of pasting it directly. For example, "x-api-key": "${MABL_API_KEY}".

Config

To add the mabl MCP server in Claude Desktop, open Claude Desktop Settings from your system’s menu bar: Claude > Settings…

Accessing settings in Claude

In the Settings window, click on the Developer tab. Click on Edit Config to open the configuration file for Claude Desktop. This action creates or opens the existing claude_desktop_config.json file. Depending on your OS, this file is located in one of the following locations:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%Claudeclaude_desktop_config.json

Claude Desktop currently supports only stdio transport and does not natively connect to remote HTTP endpoints. To use the mabl cloud MCP on Claude Desktop, use a bridge like mcp-remote to translate between Claude's local stdio and our remote HTTP server. mcp-remote is a third-party open-source package, not maintained by mabl. and requires the stdio bridge.

For OAuth config, add the following to your Claude Desktop's MCP configuration:

"mcpServers": {
  "mabl": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://mcp.mabl.com/mcp"
    ]
  }
}

For API key auth config, include your API key as a header. To use the following config block, replace YOUR_API_KEY_HERE with your editor or viewer mabl API key:

"mcpServers": {
  "mabl": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://mcp.mabl.com/mcp",
      "--header",
      "x-api-key:YOUR_API_KEY_HERE"
    ]
  }
}

Start the server

To confirm the mabl cloud MCP is installed, quick and restart Claude Desktop. When you click on the settings icon at the bottom of the conversation input box, you should see available MCP tools.

Viewing mabl MCP tools in Claude Desktop