Testingbot Mcp Server

What is TestingBot MCP Server?

TestingBot MCP Server is the official Model Context Protocol (MCP) implementation from TestingBot. It enables AI assistants to interact with TestingBot’s testing infrastructure, allowing users to manage tests, browsers, devices, and more through conversational interfaces, directly from MCP-compatible clients.

How to use TestingBot MCP Server?

Install the server globally with npm install -g @testingbot/mcp-server or add it to a project. Authenticate by either running the tb_login tool (OAuth-style browser or device code flow) or by setting TESTINGBOT_KEY and TESTINGBOT_SECRET environment variables. Configure the server in your MCP client (e.g., Claude Desktop, VS Code with Continue, Cursor) using the npx -y @testingbot/mcp-server command and your credentials.

Key features of TestingBot MCP Server

• Live Testing on real browsers and mobile devices
• Query and manage available browsers and devices
• Create, retrieve, update, delete tests with detailed logs
• Upload and manage mobile app files (APK, IPA, ZIP)
• Take cross-browser screenshots
• Organize tests into builds and manage builds
• View and update account and team information
• Drive remote browsers/devices via automation tools (bundled)
• Manage TestingBot tunnels for local testing

Use cases of TestingBot MCP Server

• Start an interactive live testing session on a specific browser and OS via a chat prompt
• Query recent test results, view video recordings, logs, and execution steps
• Upload an APK or IPA file to TestingBot storage for later testing
• Mark a test as passed or failed and update its metadata
• Drive a remote browser or real mobile device from an agent to perform actions and take screenshots

FAQ from TestingBot MCP Server

What runtime is required to use TestingBot MCP Server?

Node.js 18 or later is required (22.15.0 or later is recommended).

How do I authenticate with TestingBot?

You can either use the tb_login tool, which supports OAuth-style browser or device code authentication, or set the TESTINGBOT_KEY and TESTINGBOT_SECRET environment variables. Credentials are resolved with environment variables taking highest priority.

Where are credentials stored after using tb_login?

Credentials are written to ~/.testingbot/credentials with mode 0600. You can set TESTINGBOT_PROFILE to use a different account or TESTINGBOT_CONFIG_DIR to change the directory.

Which MCP clients are supported?

Claude Desktop, VS Code with the Continue extension, Cursor, Cline, and other MCP-compatible clients are supported.

Are there any limitations on automation sessions?

Yes, automation sessions are metered. The bundled automation tools from @testingbot/automation-mcp include caveats around session usage and configuration options.