Skip to main content
Glama
CodeInKlingon

@codeinklingon/browser-mcp

Related Servers

Alternatives to @codeinklingon/browser-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      MCP server for Puppeteer-based browser automation with a unified observe (a11y snapshot + pixel overlay), diff engine, event layer, and action primitives.
      26
      46 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for headless browser automation using Puppeteer, enabling AI to navigate, click, fill forms, take screenshots, and execute JavaScript on web pages.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Self-hosted MCP server for browser automation using Puppeteer, with tools for navigation, screenshots, mouse interactions, cookie management, and multiple transport protocols.
      1,833 npm
      20
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for stealth browser automation that uses human-like interaction patterns to bypass bot detection via the Chrome DevTools Protocol. It enables users to navigate, interact with elements, and capture data from websites using undetectable behaviors like Bezier mouse movements and Gaussian typing delays.
      82 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.
      8
      1,833 npm
      MIT
    • A
      license
      B
      quality
      Not graded
      maintenance
      A MCP server that provides browser automation tools, allowing users to navigate websites, take screenshots, click elements, fill forms, and execute JavaScript through Playwright.
      8
      2
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct action: open, run, close. No overlap; an agent can easily select the correct tool for each step of the browser lifecycle.

    Naming Consistency5/5

    All names follow the exact pattern `browser_tab_<verb>`, with verbs being clear actions. Perfectly consistent.

    Tool Count5/5

    Three tools cover the essential browser tab lifecycle: open, execute code, close. This is a well-scoped set for the server's purpose.

    Completeness4/5

    The tools cover the primary workflow (open, run, close). While additional tools for specialized actions (e.g., tab navigation) could be added, the API methods described in the critical rules provide sufficient interactivity, so no dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues