Testingbot Mcp Server

Created By
testingbot7 months ago
The TestingBot MCP server allows you to take screenshots of your website on multiple browsers and operating systems. Create CDP sessions and interface with the TestingBot service.
Overview

what is TestingBot MCP Server?

The TestingBot MCP Server is a tool that allows developers to take screenshots of their websites across multiple browsers and operating systems, facilitating cross-browser testing and ensuring consistent user experiences.

how to use TestingBot MCP Server?

To use the TestingBot MCP Server, set up your environment with your TestingBot API key and secret, and run the server using the command: TESTINGBOT_KEY={TESTINGBOT_KEY} TESTINGBOT_SECRET={TESTINGBOT_SECRET} npx -y @testingbot/mcp-server. You can then create CDP sessions to interact with the TestingBot service.

key features of TestingBot MCP Server?

  • Cross-browser screenshot capabilities
  • Support for multiple operating systems
  • Integration with the TestingBot service for enhanced testing

use cases of TestingBot MCP Server?

  1. Taking screenshots of web applications to verify UI consistency across different browsers.
  2. Automating visual regression testing for web applications.
  3. Facilitating debugging by capturing screenshots during test runs.

FAQ from TestingBot MCP Server?

  • What browsers does TestingBot MCP Server support?

It supports a wide range of browsers including Chrome, Firefox, Safari, and Edge.

  • Is there a cost associated with using TestingBot MCP Server?

Yes, you need a TestingBot account with an active subscription to use the service.

  • Can I run tests on mobile browsers?

Yes, TestingBot MCP Server supports mobile browser testing as well.

Server Config

{
  "mcpServers": {
    "testingbot": {
      "command": "npx",
      "args": [
        "-y",
        "@testingbot/mcp-server"
      ],
      "env": {
        "TESTINGBOT_KEY": "your-api-key",
        "TESTINGBOT_SECRET": "your-api-secret"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
testingbot
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 hours ago