Skip to main content
Glama
Sign In
mcp-browser-testing-server

mcp-browser-testing-server

by DIMONZ23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-browser-testing-server

No user-submitted related servers found.

    Related Servers

    • qa-pilot

      hoanghadhpt
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to drive Playwright and Midscene browser automation, generate and run heuristic test suites, manage authenticated sessions, monitor UI/console/network failures, and export Playwright tests through MCP tools.
      4
      MIT
    • orchords-web-pilot

      orchords-web-pilotofficial

      ORCHORDS
      F
      license
      A
      quality
      C
      maintenance
      Enables coding agents to drive a real Playwright-backed browser session, navigating, observing, interacting, and capturing proof on web pages via MCP tools across stdio and Streamable HTTP transports.
      15
      2
      -

    • CloakBrowser MCP

      Minhob192
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to automate a real Chromium browser through the unchanged upstream Playwright MCP tool surface, covering navigation, research, testing, and daily web workflows in plain language. It ships via npm or Docker over stdio or Streamable HTTP, and supports persistent login profiles, Chrome extension loading, proxy/GeoIP matching, and humanized mouse, keyboard, and scroll behavior.
      431 npm
      MIT

    • cloakbrowser-mcp

      stavrosgunduz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to run Playwright-compatible browser automation over stdio or Streamable HTTP, covering research, testing, persistent login profiles, Chrome extensions, proxy matching, and humanized interactions. It ships as npm and Docker packages for cross-platform deployments.
      431 npm
      MIT

    • jev-browser

      tontoko
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.
      13
      Apache 2.0

    • weblab

      dittofleet
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive real Chromium, WebKit, or Firefox browsers — opening named sessions, running ordered steps like clicks, typing, and assertions, and reading back text, console/network logs, and screenshots — so web apps can be tested and explored end to end. It starts and shares dev servers, attaches to already-running browsers, and can fake API responses or device settings.
      2 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct browser action: navigation, inspection, interaction, and screenshot capture. There is no meaningful overlap between inspecting elements and interacting with them, since one discovers selectors and the other acts on them.

    Naming Consistency5/5

    All tools use the same browser_ prefix followed by a concise action-oriented name. browser_screenshot uses a noun form, but it is conventionally understood as an action and does not break the overall pattern.

    Tool Count5/5

    Four tools is well within the ideal range and each tool has a clear role in the core browser testing loop. The surface is compact without feeling arbitrarily truncated.

    Completeness3/5

    The core workflow of navigate, inspect, interact, and screenshot is covered, but important browser-testing operations are missing, such as waiting for elements or page load, extracting text, capturing console/network errors, and closing the browser session. These gaps could cause flaky automation or dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources