Testable MCP Server

• Introduction
• Server URL
• Authentication
• What MCP Provides
• Choosing a Client

Introduction

Testable exposes the testing web app’s capabilities through a hosted Model Context Protocol (MCP) server. Connect an MCP-compatible client to let external agents inspect and manage your Testable account with the permissions granted during authentication.

The MCP server is not limited to a few special workflows. It is designed as an external agent interface for the same kinds of actions you can perform in the Testable web app, including creating and updating test cases, scenarios, configurations, executions, schedules, success criteria, notifications, integrations, runners, organization settings, and related testing resources.

Server URL

Use the Testable MCP endpoint:

https://mcp.testable.io

If your organization uses SAML login, use the MCP endpoint that matches your team’s Testable login subdomain:

The MCP configuration is also available from AI Conversations by opening the settings icon in the upper right. The modal includes a copyable config block and authentication selector.

Authentication

OAuth is the recommended authentication method. When your MCP client supports OAuth for remote MCP servers, connect to the server URL and complete the Testable authorization flow in the browser. OAuth avoids copying long-lived API keys into local config files and makes access easier to revoke.

For SAML organizations, replace mcp.testable.io in the examples below with [subdomain].mcp.testable.io, using the same subdomain you use to sign in to Testable.

{
  "mcpServers": {
    "testable": {
      "url": "https://mcp.testable.io"
    }
  }
}

API Key Alternatives

The MCP server also supports API key authentication through an authorization header or a key query parameter. Use these methods only when your MCP client does not support OAuth.

Bearer Header

{
  "mcpServers": {
    "testable": {
      "url": "https://mcp.testable.io",
      "headers": {
        "Authorization": "Bearer [api-key]"
      }
    }
  }
}

Query Parameter

{
  "mcpServers": {
    "testable": {
      "url": "https://mcp.testable.io?key=[api-key]"
    }
  }
}

Prefer OAuth whenever your client supports it. If you use API keys, treat them like passwords: store them in your MCP client’s secret storage when available, rotate them when access changes, and avoid committing MCP config files with real keys.

What MCP Provides

MCP provides agent access to the same testing resources and actions available through the web app. If your authenticated Testable user can perform an action in the testing app, an MCP-connected agent can generally perform that action through the server, subject to the client’s approval flow and the tools exposed for your account.

Available actions still depend on your plan, organization permissions, feature flags, and rollout status. MCP clients may also present tool calls differently, so review and approve changes using the controls provided by your client.

Choosing a Client

Use any MCP-compatible client that supports remote HTTP MCP servers. Paste the copied configuration into that client, complete OAuth when prompted, then verify that the client can list Testable tools before asking it to make changes.