Skip to main content
Glama
scrollDynasty

BrowserMesh

by scrollDynasty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BrowserMesh

No user-submitted related servers found.

    Related Servers

    • browser-store

      bysking
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.
      3 npm
      MIT

    • 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

    • BrowserGenie MCP Server

      BrowserGenie
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that provides AI models with full browser automation capabilities through Chrome. It enables navigation, interaction, screenshots, and complete DevTools access by bridging AI clients with a companion Chrome extension.
      99
      4 npm
      3
      Apache 2.0
    • agentify-desktop by agentify-sh

      agentify-desktopofficial

      agentify-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI tools to control local browser sessions for ChatGPT, Claude, and other AI services, supporting querying, navigation, file uploads, and artifact management.
      35 npm
      564
      Mozilla Public 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.8/5.0

    Scored across 35 tools

    Disambiguation5/5

    Every tool maps to a distinct resource or action: session lifecycle, page lifecycle, navigation, history, interaction, observation, waiting, and state persistence. Even adjacent tools like wait vs action_and_wait and scroll vs scroll_into_view are clearly separated by trigger semantics and intended use.

    Naming Consistency4/5

    All names share the browser_ prefix and snake_case style, and most follow a predictable action-plus-target pattern such as session_create, page_list, get_url, and select_option. Minor deviations like browser_snapshot, browser_visible_text, and browser_forward/back break the strict verb_noun pattern but remain readable and recognizable.

    Tool Count2/5

    35 tools is well above the 25+ threshold and will feel heavy for agents to scan, even though browser automation is a broad domain. Many interaction tools are individually justified, but several could be consolidated or grouped without losing clarity.

    Completeness4/5

    The surface covers full session and page lifecycles, navigation, history, state persistence, observation, waiting, and a rich set of interaction actions, so most workflows have no dead ends. Minor gaps remain, such as file upload/download handling, post-creation viewport or context updates, and direct cookie or storage inspection, but agents can usually work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources