Skip to main content
Glama
Sign In
stealth-agent-browser-mcp

stealth-agent-browser-mcp

by ykshah1309
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to stealth-agent-browser-mcp

No user-submitted related servers found.

    Related Servers

    • Charlotte

      RebeccaLacroix45928
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents token-efficient, structured access to web pages, returning compact page orientations and targeted element queries instead of full accessibility-tree dumps, plus browser interaction, monitoring, and session management tools.
      4 npm
      MIT

    • agbrowser

      neko233-com
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets AI agents drive the locally installed Chrome or Edge, opening pages, taking compact accessibility-tree snapshots with @e references, and clicking, typing, scrolling, or capturing screenshots. It also exposes multi-account and cross-channel tab switching, tab sync rules, and ad-block/perf statistics.
      MIT

    • Web Bridge

      JohnXu22786
      A
      license
      A
      quality
      C
      maintenance
      Browser automation MCP server that uses a real browser to give agents eyes and hands—open pages, click, fill, screenshot, and run scripts via accessibility-tree snapshots.
      22
      17 npm
      MIT

    • browser-mcp

      huaka1
      A
      license
      A
      quality
      D
      maintenance
      Agent-native browser control MCP server that enables AI agents to browse and interact with web pages via accessibility tree snapshots and ref ID-based commands.
      15
      2
      MIT
    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.5/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action: scrolling, waiting, navigation, snapshot, clicking, typing, selecting, tab management, JS evaluation, proxy configuration, and captcha solving. No overlapping purposes.

    Naming Consistency4/5

    Tools consistently use the browser_ prefix with verb or verb+noun patterns (e.g., browser_navigate, browser_set_proxy). The exception is browser_tabs (noun) which deviates slightly but remains clear.

    Tool Count5/5

    13 tools cover the core browser automation tasks without being excessive. Each tool has a clear role, and the count is well-scoped for the server's purpose.

    Completeness4/5

    Covers navigation, interaction, proxy management, and captcha solving comprehensively. Minor gaps exist, such as missing back/forward navigation or visual screenshot (snapshot returns AOM only), but most workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources