Skip to main content
Glama
LowOrbitLab

chromiumfish_mcp

by LowOrbitLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to chromiumfish_mcp

No user-submitted related servers found.

    Related Servers

    • chrome-mcp

      xiyiyiru
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.
      7
      129 PyPI
      GPL 3.0

    • Browser MCP

      CypherPotato
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.
      7 npm
      -

    • BrowserUse

      YisRime
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to control Chrome/Edge browsers via CDP, including page navigation, element interaction, snapshots, network debugging, script execution, and performance tracing.
      AGPL 3.0

    • monkeysee

      juliocesar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.
      0
      1
      MIT
    • tether-browser-harness by Orellius

      tether-browser-harnessofficial

      Orellius
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable clients to launch and control one visible, isolated Chromium session, creating and managing Tether-owned tabs, navigating to HTTP(S) URLs, reading bounded page text on request, and ending the session without touching the user's personal browser profile.
      Apache 2.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

    A3.6/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, from basic interactions like click and hover to specialized actions like solve_challenge and drag. The slight overlap between click and click_at is well-documented and justified by use cases.

    Naming Consistency4/5

    Tool names mostly follow a consistent verb_noun pattern (e.g., open_page, type_text), though a few single-word verbs (click, hover, scroll) deviate slightly. The pattern is predictable and readable.

    Tool Count4/5

    24 tools is a comprehensive set for browser automation, covering navigation, input, waiting, frames, screenshots, and challenge handling. It is slightly above the ideal range but each tool serves a distinct purpose.

    Completeness4/5

    The toolset covers most common browser interactions including all major navigation and input actions, frame handling, and even challenge detection/solving. Minor gaps like file upload or clipboard operations exist but are not essential for core automation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources