AgentPhone
Give an AI agent its own US or Canada number to call and text.
Author, run and debug mabl end-to-end tests from Claude.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The mabl MCP server connects Claude to mabl, the end-to-end test automation platform. Anthropic's directory lists 93 tools for authoring and editing tests, running tests and plans in mabl's cloud, triggering deployment runs, analysing failures and reporting on test quality. It acts with your mabl role, or with a workspace API key; a Viewer key is read-only.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
401 with an OAuth challenge, so schemas and annotations are not on this page.Yes, with a Viewer API key. mabl's security article says the MCP server accepts two kinds of workspace-scoped API key: Editor keys, which carry the editor role's permissions, and Viewer keys, which are read-only. Only workspace owners can create keys. mabl recommends an Editor key so every tool works, so a Viewer key trades the authoring and run tools for a read-only connection.
Use OAuth for your own work and an API key for agent-to-agent use. mabl says OAuth connects to your mabl user and reaches every workspace you belong to, with occasional re-authentication. An API key is scoped to the one workspace it was created in and lasts until the key expires or is deleted. API key setup skips the browser consent flow and sends the key in an x-api-key header.
Up to 30 days, or 7 days if you stop using it. mabl documents a one-hour access token and a refresh token that lasts 30 days but expires sooner after 7 days without using the MCP server. After that you sign in again. If your organization sets shorter lifetimes, those apply instead, and with single sign-on your identity provider governs who can authenticate.
Yes, through mabl Link or a local run. mabl says the MCP server never connects to your applications itself, but the test runs it triggers reach them like any mabl cloud run. Private apps need mabl Link, which opens an outbound tunnel from your network, or allowlisted mabl IP addresses. The run_mabl_test_local tool instead returns a link that runs the test in your mabl Desktop App.
POST https://mcp.mabl.com/mcp returned 401 with a WWW-Authenticate challenge naming https://mcp.mabl.com/.well-known/oauth-protected-resource/mcp, which lists https://mcp.mabl.com/ as the authorization server and four identity scopes · retrieved 2026-11-18Connect mabl once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.