SSyncDev

Testingbot MCP Server

TestingBot's official MCP server

Local serverstdioTypeScript

What is the Testingbot MCP Server?

TestingBot's official MCP server

What you get

TestingBot's official Model Context Protocol (MCP) server implementation. This server enables AI assistants to interact with TestingBot's testing infrastructure, allowing you to manage tests, browsers, devices, and more through conversational interfaces.

  • 🖥️ Live Testing - Start interactive manual testing sessions on real browsers and devices
  • 🌐 Browser & Device Management - Query available browsers and real devices
  • 🧪 Test Management - Create, retrieve, update, and delete tests with comprehensive details
  • 📦 Storage Management - Upload and manage mobile app files (APK, IPA, ZIP)
  • 📸 Screenshot Testing - Take cross-browser screenshots
  • 🏗️ Build Management - Organize tests into builds

Configuration and credentials

  • Node.js >= 18 (recommended: 22.15.0 or later) - TestingBot Account with API credentials - An MCP-compatible client (Claude Desktop, VS Code with Continue, Cursor, etc.)

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
startLiveSessionStart an interactive live testing session on TestingBot. Opens a real browser or mobile device for manual testing.
startDesktopLiveSessionConvenience tool to start a desktop browser live testing session.
startMobileLiveSessionConvenience tool to start a mobile device live testing session.
getBrowsers
getDevicesGet list of available mobile devices (real devices and simulators).
getTests
getTestDetailsGet comprehensive details about a specific test including: - Test status, browser, platform, and timing information - Video recording URL and screenshot URLs - Selenium, browser, and Appium logs - Test execution steps wi
updateTest
deleteTest
stopTest
getBuilds
getTestsForBuild

Configuration

  • Node.js >= 18 (recommended: 22.15.0 or later) - TestingBot Account with API credentials - An MCP-compatible client (Claude Desktop, VS Code with Continue, Cursor, etc.)
VariableDescriptionRequired
TESTINGBOT_KEYCredential the server authenticates with.Yes
TESTINGBOT_SECRETCredential the server authenticates with.Yes
TESTINGBOT_ACCESS_KEYCredential the server authenticates with.Yes

Example prompts to try

  • “Use Testingbot to Configuration.”
  • “Use Testingbot to Cursor.”
  • “Use Testingbot to startLiveSession.”

Frequently asked questions

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

Alternatives to the Testingbot MCP Server

Playwright

Official

Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.

Browser AutomationTypeScript★ 21.0k

Puppeteer

Official

The original Chromium automation reference server — simple, screenshot-driven browser control.

Browser AutomationTypeScript★ 63.0k

Chrome DevTools

Official

Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.

Browser AutomationTypeScript★ 48.4k

Browser MCP

Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.

Browser AutomationRemoteTypeScript★ 38.4k

BrowserTools

Enables AI-powered applications to monitor and interact with browser data via a Chrome extension and MCP.

Browser Automation★ 7.3k

Playwright

Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript

Browser Automation★ 5.6k