To focus continued investment on the cloud MCP server, mabl is deprecating the local MCP server as of May 18, 2026. The local server will continue to function, but it will no longer receive new tools, feature updates, or support.
We recommend migrating to the cloud MCP server. With the cloud server, you get nearly everything that exists on the local MCP plus:
- A larger and still-growing set of tools, including agentic capabilities such as identifying coverage gaps and conversational results analysis
- Built-in workspace management, so you can create applications, credentials, and environments, edit plans, and rerun deployments without leaving your AI client
- Automatic updates, with no need to keep the mabl CLI on the latest version to access new tools
Who is affected
This deprecation applies to anyone who configured the local mabl MCP server in their AI client. If you've already configured the cloud MCP server at https://mcp.mabl.com/mcp, no action is required.
If you aren't sure if you're using the local or cloud MCP, try prompting your agent for the information. For example:
"Look at my mabl MCP server config. Am I running
npx @mablhq/mabl-cli mcp start(local) or pointing athttps://mcp.mabl.com/mcp(cloud)?"
The only capability unique to the local server is Playwright export, which remains available through the mabl CLI. See exporting tests for more details.
How to migrate
To switch, replace your local MCP configuration with the cloud configuration in your AI client. In Claude Code, run:
claude mcp add --transport http mabl https://mcp.mabl.com/mcp
For other clients, use the following JSON configuration:
{
"mcpServers": {
"mabl": {
"url": "https://mcp.mabl.com/mcp",
"type": "http"
}
}
}
For complete instructions, see the article on setting up the mabl cloud MCP.
Learn more
If you have any questions about migrating to the cloud MCP server, please reach out to your CSM.