Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

TestingBot

✓ service owner · testingbot.com

by testingbotversion 1.4.0i★ 2iRuns on your computerOfficial site ↗
Registry namecom.testingbot/mcp-server

How to install

What it does

Run browser, mobile and app tests on TestingBot's cloud, including localhost via tunnels

  • Connects Runs on your computer
  • Account or key Needs TESTINGBOT_KEY, TESTINGBOT_SECRET
  • Category Web & browsers

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6381 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6051 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2361 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity6/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score18/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install TestingBot. Follow https://mcp.popnx.com/i/testingbot-mcp-server.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 19, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server TestingBot for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "testingbot": { "command": "npx", "args": [ "-y", "@testingbot/mcp-server" ], "env": { "TESTINGBOT_KEY": "your-value", "TESTINGBOT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TESTINGBOT_KEY, TESTINGBOT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the TestingBot tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a TestingBot key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the TestingBot site ↗

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "testingbot": {
          "command": "npx",
          "args": [
            "-y",
            "@testingbot/mcp-server"
          ],
          "env": {
            "TESTINGBOT_KEY": "your-value",
            "TESTINGBOT_SECRET": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use TestingBot and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using TestingBot or shows a TestingBot tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect TestingBot yet

TestingBot runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect TestingBot

  • You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time)
  • You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time)

B · Others in Web & browsers that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server TestingBot for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user testingbot --env TESTINGBOT_KEY=your-value --env TESTINGBOT_SECRET=your-value -- npx -y @testingbot/mcp-server 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TESTINGBOT_KEY, TESTINGBOT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the TestingBot tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a TestingBot key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the TestingBot site ↗

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user testingbot --env TESTINGBOT_KEY=your-value --env TESTINGBOT_SECRET=your-value -- npx -y @testingbot/mcp-server

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see TestingBot listed as connected

  6. Try it

    Use TestingBot and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using TestingBot or shows a TestingBot tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server TestingBot for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "testingbot": { "command": "npx", "args": [ "-y", "@testingbot/mcp-server" ], "env": { "TESTINGBOT_KEY": "your-value", "TESTINGBOT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TESTINGBOT_KEY, TESTINGBOT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the TestingBot tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a TestingBot key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the TestingBot site ↗

  3. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  4. Fill in your key

    In the TestingBot settings, TESTINGBOT_KEY, TESTINGBOT_SECRET is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use TestingBot and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using TestingBot or shows a TestingBot tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a TestingBot key (create it on the maker’s site) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server TestingBot for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "testingbot": { "type": "stdio", "command": "npx", "args": [ "-y", "@testingbot/mcp-server" ], "env": { "TESTINGBOT_KEY": "your-value", "TESTINGBOT_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For TESTINGBOT_KEY, TESTINGBOT_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the TestingBot tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a TestingBot key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the TestingBot site ↗

  3. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  4. Fill in your key

    In the TestingBot settings, TESTINGBOT_KEY, TESTINGBOT_SECRET is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use TestingBot and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using TestingBot or shows a TestingBot tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use TestingBot💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user testingbot --env TESTINGBOT_KEY=your-value --env TESTINGBOT_SECRET=your-value -- npx -y @testingbot/mcp-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "testingbot": {
      "command": "npx",
      "args": [
        "-y",
        "@testingbot/mcp-server"
      ],
      "env": {
        "TESTINGBOT_KEY": "your-value",
        "TESTINGBOT_SECRET": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "testingbot": {
      "command": "npx",
      "args": [
        "-y",
        "@testingbot/mcp-server"
      ],
      "env": {
        "TESTINGBOT_KEY": "your-value",
        "TESTINGBOT_SECRET": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "testingbot": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@testingbot/mcp-server"
      ],
      "env": {
        "TESTINGBOT_KEY": "your-value",
        "TESTINGBOT_SECRET": "your-value"
      }
    }
  }
}

Values you fill in

  • TESTINGBOT_KEY secret required env
    TestingBot API key (also accepts TB_KEY or TESTINGBOT_USERNAME)
  • TESTINGBOT_SECRET secret required env
    TestingBot API secret (also accepts TB_SECRET or TESTINGBOT_ACCESS_KEY)

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
204/wk
Verified domain
✓ testingbot.com
Connection
Runs on your computer
Latest versioni
1.4.0
Published to registryi
Nov 19, 2026
Code last changedi
Nov 19, 2026
Maker
testingbot
Packages
npm: @testingbot/mcp-server
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain testingbot.com (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/testingbot-mcp-server.svg)](https://mcp.popnx.com/en/servers/testingbot-mcp-server)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Web & browsersi

  • More stars than 84% of the other 1645 servers in this category
  • Published to the registry more recently than 99% of the other 1645 servers in this category
  • Basic checks equal to or better than 99% of the other 1645 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is TestingBot safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TESTINGBOT_KEY, TESTINGBOT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (1.4.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Browser Use, changedetection.io (official), Apify MCP Server, Pomerado, Actionbook

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

by browser-useWidely used↓ 1.7M/wk★ 121.5KUpdated 30 days ago

Computer or cloud✓ service owner · browser-use.com

Apify MCP Server

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

by apifyWidely used★ 17KUpdated 3 days ago

Runs in the cloud✓ service owner · apify.com

Pomerado

Connect your agents to any website. The cheaper, faster and more reliable alternative to browser use

by PomeradoGrowing★ 1.8KUpdated 2 days ago

Runs in the cloud✓ service owner · pomerado.ai

Actionbook

Let your AI agent operate any website through a real, logged-in browser session.

by actionbookGrowing★ 1.6KUpdated 32 days ago

Runs in the cloud✓ service owner · actionbook.app
Compared with similar ones
This one
TestingBot
Browser Usechangedetection.io (official)Apify MCP ServerPomeradoActionbook
Runs whereInstalls on your computerCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesYesNoYesNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks3/35/53/34/44/44/4
LicenseMITMITApache-2.0MITMITApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

TestingBot MCP Server

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.

⚡ One-Click Install

Claude Desktop: download testingbot-mcp-server- .mcpb from the latest release and double-click it. Claude will set up the TestingBot MCP server automatically.

After install, set your credentials from TestingBot account settings.

Features

  • 📱 App Automate - Run Maestro, Espresso, and XCUITest suites on real devices and emulators, straight from the agent
  • 🖥️ 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
  • 👤 User Account - View and update account information
  • 👥 Team Management - Manage team settings and team members
  • 🔌 Chrome DevTools Protocol - Create CDP sessions for advanced browser automation
  • 🚇 Tunnel Management - Start, stop and manage TestingBot tunnels to test localhost and private sites

Prerequisites

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

Installation

Quick Setup

Install the MCP server globally:

npm install -g @testingbot/mcp-server

Or add to your project:

npm install @testingbot/mcp-server
Configuration
Recommended: log in with tb_login (no key/secret to copy)

You don't have to find and paste API credentials. Install the server, leave the credentials blank, and just ask the agent:

Log me in to TestingBot.

The agent calls the `tb_login` tool. It uses OAuth-style browser authentication — no secret ever leaves the browser — and picks the right mechanism for your environment automatically:

  • Browser (loopback, the default on a desktop): your browser opens to a TestingBot authorization page. Sign in if needed and click Authorize; the credentials are captured on a local callback and the agent finishes the sign-in. Nothing to type. (RFC 8252.)
  • Device code (automatic fallback on SSH / remote / dev containers / web): the tool prints a short URL and code instead:
  1. Open the URL in your browser (e.g. https://testingbot.com/device).
  2. Enter the code, sign in if needed, and click Authorize.
  3. Tell the agent you've authorized — it calls tb_login again to finish.

(RFC 8628.)

You can force a mechanism by passing mode: "loopback" or mode: "device" to tb_login (the default is "auto").

Your credentials are written to ~/.testingbot/credentials (mode 0600) and used by every subsequent tool call — no restart and no JSON editing. This works in any MCP client (VS Code, Cursor, Cline, Claude Desktop, …). To use a different account, set TESTINGBOT_PROFILE; to relocate the file, set TESTINGBOT_CONFIG_DIR.

Environment Variables

Alternatively (or for CI, where env vars take precedence over the file), set your TestingBot credentials as environment variables:

export TESTINGBOT_KEY="your-api-key"

export TESTINGBOT_SECRET="your-api-secret"

Or create a .env file in your project:

TESTINGBOT_KEY=your-api-key

TESTINGBOT_SECRET=your-api-secret

The key also accepts the aliases TB_KEY / TESTINGBOT_USERNAME, and the secret accepts TB_SECRET / TESTINGBOT_ACCESS_KEY.

How credentials are resolved

Credentials are resolved in this order, highest priority first:

  1. Environment variables (above) — both a key and a secret must be set. This lets CI and per-client config override everything else.
  2. The `~/.testingbot/credentials` file written by tb_login, for the active profile (default, or TESTINGBOT_PROFILE).
  3. Neither set: the server starts in a degraded mode where every tool except tb_login reports "Run tb_login to authenticate" — so first run is self-healing rather than a hard error.
Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows):

{

"mcpServers": { "testingbot": { "command": "npx", "args": ["-y", "@testingbot/mcp-server"], "env": { "TESTINGBOT_KEY": "your-api-key", "TESTINGBOT_SECRET": "your-api-secret" } } } }

VS Code (with Continue extension)

Add to .continue/config.json:

{

"mcpServers": [ { "name": "testingbot", "command": "npx", "args": ["-y", "@testingbot/mcp-server"], "env": { "TESTINGBOT_KEY": "your-api-key", "TESTINGBOT_SECRET": "your-api-secret" } } ] }

Cursor

Add to .cursor/mcp.json:

{

"mcpServers": { "testingbot": { "command": "npx", "args": ["-y", "@testingbot/mcp-server"], "env": { "TESTINGBOT_KEY": "your-api-key", "TESTINGBOT_SECRET": "your-api-secret" } } } }

🤖 Let an AI Agent Drive a Remote Browser or Device

This server already includes the automation tools from @testingbot/automation-mcp — installing this package gives the agent the ability to actually drive a remote browser or real mobile device on TestingBot's grid, not just manage resources.

Just ask:

Open Safari 17 on macOS on TestingBot. Navigate to example.com and click the "More information" link.

The agent will call tb_openBrowser, tb_navigate, tb_snapshot, tb_click — and surface a live-view URL so you can watch it in real time. For real iOS / Android devices, the bundled appium-mcp child gives the agent the full appium_* toolbelt (appium_session_management, appium_gesture, appium_set_value, appium_screenshot, ~30 more) — no separate install or config required. Just ask: _"Open an iPhone 15 Pro on iOS 17 on TestingBot, tap the login button, take a screenshot."_ See the @testingbot/automation-mcp README for the full tool list, caveats (sessions are metered), and configuration options.

🚇 Testing localhost and private sites

TestingBot's browsers and devices run in the cloud, so they can't open localhost, private IPs (10.x, 192.168.x, …) or intranet hosts directly. To reach them, they need a TestingBot Tunnel running on your machine. Just ask:

Start a tunnel and open http://localhost:3000 in Chrome on Windows 11.

The agent calls startTunnel, which needs Java 17+. The tool returns the tunnel's identifier and ID, and the agent passes them on:

RunHow it uses the tunnel
tb_openBrowser (agent-driven browser)tunnelIdentifier (required: sessions without it go direct). Or set TESTINGBOT_TUNNEL_IDENTIFIER
appium_session_management (native apps)"tb:options": {"tunnel-identifier": "…"} in the capabilities
startLiveSession / startDesktopLiveSession / startMobileLiveSessiontunnelId (the numeric ID)
runMaestroTesttunnelIdentifier. Without it, the account's newest running tunnel is used
takeScreenshot, runAppAutomateTest (Espresso / XCUITest)The account's newest running tunnel is used automatically

Android apps and flows: Android never sends localhost / 127.0.0.1 through a proxy, so on an Android device or emulator those URLs reach the device itself, not your machine. Use a hostname that resolves to 127.0.0.1 on your side instead, such as http://myapp.localtest.me:3000. The tunnel resolves it on your machine.

stopTunnel stops the tunnel. Tunnels started by the server are also stopped when the server exits. If you'd rather run the tunnel yourself, start it with --tunnel-identifier and give the agent that name.

Available Tools

Live Testing
startLiveSession

Start an interactive live testing session on TestingBot. Returns a link that opens the session in your TestingBot dashboard, where you confirm it with Start. Mobile sessions run on emulators/simulators; real-device live sessions are started from the dashboard.

Parameters:

  • platformType: "desktop" or "mobile"
  • desiredURL: The URL to open
  • desiredOS: Operating system (Windows, Mac, Linux for desktop; android, ios for mobile)
  • desiredOSVersion: OS version: Windows 11/10/8.1/8; macOS by name (Sonoma) or number (14); or a platform code like WIN11
  • desiredBrowser (desktop only): Browser name (chrome, firefox, safari, edge, ie)
  • desiredBrowserVersion (desktop only): Browser version or "latest"
  • desiredDevice (mobile only): Device name (e.g., "iPhone 14", "Galaxy S23")
  • tunnelId (optional): Numeric ID of a running tunnel, needed for localhost / private URLs (see Testing localhost and private sites)

Example prompts:

"Start a live testing session on Chrome latest with Windows 11 for https://example.com"

"Open https://myapp.com on iPhone 14 with iOS 16 for manual testing"

startDesktopLiveSession

Convenience tool to start a desktop browser live testing session.

Parameters:

  • desiredURL: The URL to open
  • desiredOS: Windows, Mac, or Linux
  • desiredOSVersion: OS version
  • desiredBrowser: chrome, firefox, safari, edge, or ie
  • desiredBrowserVersion (optional): Browser version or "latest" (default: latest)
  • tunnelId (optional): Numeric ID of a running tunnel, for localhost / private URLs

Example prompt:

"Start desktop live session on Firefox 120 with Mac Monterey for https://example.com"

startMobileLiveSession

Convenience tool to start a mobile device live testing session.

Parameters:

  • desiredURL: The URL to open
  • desiredOS: android or ios
  • desiredOSVersion: OS version
  • desiredDevice: Device name
  • tunnelId (optional): Numeric ID of a running tunnel, for localhost / private URLs

Example prompt:

"Start mobile live session on Galaxy S23 with Android 13 for https://example.com"

Browser & Device Management
getBrowsers

Get list of available browsers and platforms for testing.

Parameters:

  • type (optional): Filter by "web" or "mobile"

Example prompt:

"Show me all available browsers for testing"

"What mobile browsers are available?"

getDevices

Get list of available mobile devices (real devices and simulators).

Example prompt:

"List all available iOS devices"

"Show me Android devices for testing"

Test Management
getTests

Retrieve a list of recent tests with pagination.

Parameters:

  • offset (optional): Paginat

Only the beginning is shown; read the rest in the repo