LABSCO SUMMARY
No API key anywhere means there is no long-lived credential to leak or rotate.
For a system that can run and create tests against your applications, removing the static-credential option entirely is a defensible choice — every connection traces to a person who signed in. The AI tools being entitlement-gated is worth checking against your plan before designing a workflow around them; the rest works on any account that can log in.
What it is
Mabl's endpoint for their low-code test automation platform, operated by mabl with nothing to self-host. An SSE endpoint exists alongside the main one.
What you get
- Running tests and analysing why they failed
- Creating tests in the cloud
- Querying results across workspaces
- AI tools, subject to the corresponding entitlement on your plan
Requirements
OAuth in the browser with your mabl account. There is no API key at all — the token is cached by the client for reconnection.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Understanding a failing test
Run it and read the analysis rather than reading a report afterwards.
02
Creating coverage from a conversation
Build the test in the cloud without opening the editor.
03
Comparing across workspaces
Query results in one place rather than switching workspace by workspace.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- Standard MCP OAuth — sign in with your mabl account on first connect; the token is cached by the client and there is no API key
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.mabl.com/mcpRequirements
- Standard MCP OAuth — sign in with your mabl account on first connect; the token is cached by the client and there is no API key