What runtime is required to use TestingBot MCP Server?
Node.js 18 or later is required (22.15.0 or later is recommended).

@testingbot
Basic information
TestingBot's official MCP server
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"testingbot": {
"command": "npx",
"args": [
"-y",
"@testingbot/mcp-server"
],
"env": {
"TESTINGBOT_KEY": "your-api-key",
"TESTINGBOT_SECRET": "your-api-secret"
}
}
}
}Get list of available browsers and platforms for testing. Optionally filter by type (web or mobile).
Get list of available mobile devices for testing (real devices and simulators).
Retrieve a list of recent tests with optional pagination. Returns test details including status, browser, platform, video and duration.
Get detailed information about a specific test by session ID. Includes logs, screenshots, video URLs, and execution metadata.
Update test metadata such as name, status (passed/failed), and other attributes. Useful for marking tests after execution.
Delete a test by session ID. This permanently removes the test and its associated data.
Stop a running test by session ID. This terminates the test execution immediately.
Get a list of builds with optional pagination. Builds group related tests together.
Get all tests associated with a specific build ID.
Delete a build and all its associated tests by build ID.
Upload a local file (APK, IPA, or ZIP) to TestingBot storage for mobile app testing. Returns an app_url for use in tests.
Upload a file from a remote URL to TestingBot storage. The file will be downloaded from the URL and stored.
List all files in TestingBot storage with pagination.
Delete a file from TestingBot storage using its app_url.
Take screenshots of a URL across multiple browsers and platforms. Returns a screenshot ID to retrieve results.
Retrieve screenshot results by screenshot ID. Returns URLs to the generated screenshots.
Get a list of all screenshot jobs with pagination.
Get current user account information including minutes used, plan details, and account status.
Update user account information such as name, email, or other profile details.
Start an interactive live testing session on TestingBot. Opens a real browser or mobile device for manual testing. Supports both desktop browsers (Chrome, Firefox, Safari, Edge, IE) and mobile devices (iOS, Android).
Convenience tool to start a desktop browser live testing session. Automatically sets platformType to 'desktop'.
Convenience tool to start a mobile device live testing session. Automatically sets platformType to 'mobile'.
Retrieve team settings and information including plan details, team size, and configuration.
Get a list of all users in your team with their roles and permissions.
Retrieve detailed information about a specific user in your team by their user ID.
Create a remote browser session on TestingBot and get its CDP (Chrome DevTools Protocol) URL for direct browser control. Use this to automate browsers via CDP clients like Puppeteer or Playwright.
Get a list of all active TestingBot tunnels. Tunnels allow you to test websites behind firewalls or on your local machine.
Delete an active TestingBot tunnel by its ID. This will terminate the tunnel connection.
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.
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.
Node.js 18 or later is required (22.15.0 or later is recommended).
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.
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.
Claude Desktop, VS Code with the Continue extension, Cursor, Cline, and other MCP-compatible clients are supported.
Yes, automation sessions are metered. The bundled automation tools from `@testingbot/automation-mcp` include caveats around session usage and configuration options.

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Free moving quotes for AI agents from Next Generation Movers, a licensed interstate mover (USDOT 3764697). US long-distance nationwide and local DC/MD/VA. Indicative ballpark price and booking options; optional $0.01 x40

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews β all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1β3

Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov
Comments