Testingbot Mcp Server

Name: Testingbot Mcp Server
Author: testingbot

@testingbot

代码仓库主页

关于 Testingbot Mcp Server

TestingBot's official MCP server

#testing #ai-testing #developer-tools

基本信息

分类

其他

许可证

MIT

运行时

node

传输方式

stdio

发布者

testingbot

提交者

Jochen

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "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.

概览

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.