The mabl cloud MCP server has new tools for environments, workspace members, and test run artifacts, so your AI client can handle more setup and investigation without a trip to the mabl app.
- Environments: look up an environment and the names of its variables, set or remove variables, and update the environment's name or description. Variable values are never returned, and variables you don't change keep their values.
- Workspace members: list workspace members with their name, email, and workspace role.
- Test run artifacts: list the screenshots, DOM snapshots, HAR files, console logs, and traces for each step of a test run, whether the run passed or failed.
- Plans with multiple deployments: when an application and environment are linked by more than one deployment, you can tell your AI client which deployment a new plan should use. If you don't specify one, it lists the deployments to choose from.
To change an environment through the cloud MCP server, you need the editor or owner role in the workspace.
Try it out
Connect your AI client to the mabl cloud MCP server, then try a prompt like:
"Set BASE_PATH to /v2 on my staging environment and remove the OLD_TOKEN variable."
"Who are the owners in this workspace?"
"Show me the DOM snapshot and console log from the failed step in my last checkout run."