To continue focusing our investments in the cloud MCP server, mabl is retiring the local MCP server on August 25, 2026. After that date, the local mabl MCP will no longer accept connections.
The cloud server covers everything the local server does, plus capabilities that exist only on the cloud side:
- Workspace management for creating applications, credentials, and environments, editing plans, and rerunning deployments without leaving your AI client
- Conversational test planning for working out what a test should cover before you build it
- Failure investigation for understanding why a cloud run failed
- Automatic updates, so new tools reach you without keeping the mabl CLI on its latest version
If you stayed on the local server for Playwright export, the cloud server now supports that too.
Who is affected
Anyone who configured the local mabl MCP server in their AI client needs to migrate before August 25. If your client already points at https://mcp.mabl.com/mcp, you are on the cloud server and nothing changes for you.
Not sure which one you have? Ask your agent:
Look at my mabl MCP server config. Am I running
npx @mablhq/mabl-cli mcp start(local) or pointing at https://mcp.mabl.com/mcp (cloud)?
What to do
Migrating takes about two minutes. 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 Set up the cloud MCP server.
Learn more
If you have questions about migrating, reach out to your CSM.