Skip to main content
Glama
oenius

BrowserTools MCP

by oenius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to BrowserTools MCP

No user-submitted related servers found.

    Related Servers

    • WebAI-MCP

      cpjet64
      F
      license
      Not graded
      quality
      C
      maintenance
      WebAI-MCP is a comprehensive browser automation and monitoring solution that enables AI applications to capture and analyze browser data through a Chrome extension, providing 20+ tools for screenshots, console logs, network monitoring, storage access, audits, and cross-platform auto-paste.
      2
      -

    • Chrome DevTools MCP

      az9713
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control and inspect a live Chrome browser for automated web debugging, performance analysis, and Lighthouse audits. It allows agents to capture screenshots, monitor network requests, and measure Core Web Vitals using plain-English prompts.
      3,138,727 npm
      Apache 2.0

    • browser-tools-mcp

      AgentDeskAI
      A
      license
      Not graded
      quality
      A
      maintenance
      This application is a powerful browser monitoring and interaction tool that enables AI-powered applications via Anthropic's Model Context Protocol (MCP) to capture and analyze browser data through a Chrome extension.
      7,326
      MIT

    • Browser-Debugger

      Selvadinesh-giga
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to automate and debug real Chromium browsers with capabilities like screenshots, video recording, performance analysis, visual regression testing, and OCR text extraction.
      13
      -

    • Web Developer MCP Server

      Artmann
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect web pages, monitor network requests, extract HTML, analyze console output, and examine DOM elements in real-time through a Playwright-powered browser.
      15 npm
      7
      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

    C2.5/5.0

    Scored across 14 tools

    Disambiguation3/5

    There is significant overlap between tools like getConsoleErrors/getConsoleLogs and getNetworkErrors/getNetworkLogs, which could cause confusion about which to use for specific error-checking tasks. Additionally, the various audit tools (runAccessibilityAudit, runBestPracticesAudit, runPerformanceAudit, runSEOAudit) have clear distinctions in purpose but share similar naming patterns that might lead to misselection if the agent doesn't carefully read descriptions. The tool descriptions help differentiate them, but the boundaries between console/network tools and between different audit types aren't perfectly clear.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (getConsoleErrors, getNetworkLogs, runAccessibilityAudit, takeScreenshot), which makes them predictable and readable. The main deviation is runAuditMode and runDebuggerMode, which use 'Mode' suffix instead of a specific noun, but they still fit the overall verb-first convention. All tools use camelCase consistently, with no mixing of naming styles.

    Tool Count4/5

    14 tools is reasonable for a browser testing/auditing server, covering console inspection, network monitoring, element selection, various audits, and screenshot capabilities. While slightly on the higher side, each tool appears to serve a distinct function in the browser testing domain. The count feels comprehensive without being overwhelming for the apparent scope of browser automation and auditing.

    Completeness3/5

    The toolset covers many browser inspection and auditing functions but has notable gaps. There's no navigation or interaction tools (like clickElement, navigateToUrl, fillForm), which are fundamental for browser automation. The audit tools are comprehensive but the lack of basic browser control operations means agents would need to work around significant limitations. The surface feels specialized for auditing and logging rather than complete browser automation.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources