Skip to main content
Glama
dijdzv

wsl-chrome-mcp-bridge

by dijdzv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to wsl-chrome-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • winchrome

      ZinChl
      A
      license
      Not graded
      quality
      C
      maintenance
      Runs chrome-devtools-mcp on the Windows side so AI agents inside WSL can drive Windows-side Chrome despite its loopback-only DevTools endpoint, auto-detecting all paths with no configuration. Enables agents to navigate pages, click, fill forms, execute JavaScript, read the accessibility tree, and take screenshots from WSL.
      MIT

    • browser-mcp

      ruggieroromulo
      A
      license
      Not graded
      quality
      C
      maintenance
      Local browser automation MCP server for Claude Code, enabling navigation, clicking, typing, and inspecting real web pages via Google Chrome.
      19 npm
      1
      MIT

    • chrome-local-mcp

      thronapple
      A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight MCP server for controlling a Windows Chrome instance from WSL, designed for AI coding agents with minimal token overhead and human-in-the-loop support.
      154 npm
      MIT

    • deeporax-browser-mcp

      imfaisii
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server to control a real Chrome browser from Claude, enabling navigation, DOM snapshots, clicks, typing, screenshots, and JS execution via a Chrome extension bridge.
      MIT

    • BrowserPilot MCP

      Sept-7-Qi
      A
      license
      B
      quality
      C
      maintenance
      A local browser automation bridge that connects AI agents like Claude to Chromium-based browsers, enabling web navigation, clicking, input, screenshots, and tab management.
      22
      GPL 3.0
    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

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools, chrome_open and chrome_close, are completely distinct actions with no overlap. Each serves a single clear purpose.

    Naming Consistency5/5

    Both tools follow the consistent pattern 'chrome_<verb>', using snake_case and clear verb_noun structure.

    Tool Count5/5

    With exactly two tools for opening and closing the bridge, the count is minimal but perfectly scoped for the server's intended role.

    Completeness5/5

    The tool set fully covers the lifecycle of the Chrome debugging instance (start and stop), with no necessary operations missing for this narrow domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources