Skip to main content
Glama
mlnima

browser-use-relay-mcp

by mlnima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to browser-use-relay-mcp

No user-submitted related servers found.

    Related Servers

    • Ghostlight

      sylin-org
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets AI agents drive your real Chromium browser with your existing signed-in sessions, providing visible, local, and inspectable automation for tasks like navigation, clicking, typing, and form filling.
      25
      1
      Apache 2.0
    • browser-relay by Wecko-ai

      browser-relayofficial

      Wecko-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that drives a user's real Chrome browser via a WebSocket-connected MV3 extension, enabling tab management, navigation, page interaction, screenshots, and script evaluation through natural language.
      8 npm
      MIT

    • MCP Browser

      bobmatnyc
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for browser automation and console log capture via a Chrome extension, enabling AI-driven DOM interaction, navigation, and screenshot capabilities.
      2
      MIT

    • BrowserMesh

      scrollDynasty
      A
      license
      A
      quality
      A
      maintenance
      A local, open-source MCP server that enables AI clients to control multiple isolated Chromium browser sessions concurrently, with explicit session and page addressing and independent state.
      35
      82 npm
      3
      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.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of browser interaction: snapshot for state, capabilities for metadata, query for read operations, action for single operations, batch for sequences, events for history, and upload/download for file transfer. No two tools have overlapping purposes.

    Naming Consistency4/5

    All tools share a consistent 'browser_' prefix and use snake_case, but the second part mixes nouns (snapshot, capabilities, action, batch, events) and verbs (query, upload, download). The pattern is predictable enough to be unambiguous, though not as uniform as a strict verb_noun convention.

    Tool Count5/5

    With 8 tools, the set is well-scoped for browser automation. Each tool covers a necessary function without redundancy, and the count is within the ideal range for a domain-specific server.

    Completeness4/5

    The surface covers core browser operations: state observation (snapshot), queries, actions, batch execution, event monitoring, and file transfer. Minor gaps exist such as explicit tab management or waiting, but these are likely handled through browser_action and batch sequences, making the coverage adequate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources