Skip to main content
Glama
roxybrowserlabs

RoxyBrowser MCP Server

Official
by roxybrowserlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to RoxyBrowser MCP Server

No user-submitted related servers found.

    Related Servers

    • @browserview/mcp by browserview

      @browserview/mcpofficial

      browserview
      A
      license
      A
      quality
      C
      maintenance
      MCP server for browserview.io that lets agents create, inspect, share, and destroy disposable cloud Chromium sessions, and connect via CDP using Playwright or Puppeteer.
      6
      4 npm
      MIT

    • Mithwire MCP

      elendil-tech
      A
      license
      C
      quality
      B
      maintenance
      An MCP server that gives AI clients direct control over driverless Chromium browsers through the Chrome DevTools Protocol, enabling agents to navigate pages, click, type, inspect the DOM, capture console and network traces, and manage tabs, cookies, and storage. It supports persistent profiles, proxy and locale alignment, and a live VNC viewer so users can build, test, and debug web automations interactively.
      70
      MIT

    • CloakBrowser MCP

      ryotali0703
      A
      license
      Not graded
      quality
      A
      maintenance
      This server enables MCP clients and AI agents to perform browser automation with Playwright-compatible tools, persistent profiles, extensions, proxy support, and humanized interactions. It can be run via npm or Docker over stdio or Streamable HTTP for web research, automation, testing, and regional QA.
      826 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation4/5

    Tools have distinct purposes, but batch vs individual create operations could cause confusion if descriptions are not read carefully. Overall, each tool targets a specific resource and action.

    Naming Consistency4/5

    All tools follow 'roxy_verb_noun' pattern with minor inconsistencies like 'health_check' instead of 'check_health' and 'proxy_detail' lacking 'get_' prefix. Mostly consistent.

    Tool Count4/5

    26 tools is slightly above the ideal range but each tool serves a clear purpose in browser, account, and proxy management. The scope justifies the count.

    Completeness4/5

    Covers CRUD for browsers, accounts, proxies, plus cache, health, and fingerprint. Missing a single-close browser tool and an explicit 'list opened browsers' but overall lifecycle is well-covered.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow

    Resources