Skip to main content
Glama
Nizarius

mcp-rnw-browser

by Nizarius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-rnw-browser

No user-submitted related servers found.

    Related Servers

    • Enhanced Web Scraper MCP

      JMRMEDEV
      F
      license
      B
      quality
      D
      maintenance
      Enables web scraping, React app testing, and React Native web app inspection using Playwright with multi-browser support. Provides backward compatibility with regular websites while offering enhanced features for React applications including mobile viewport emulation and component analysis.
      10
      -

    • MCP Connect

      plaintest
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control iOS Simulators and automate browsers by combining xcrun simctl, fb-idb, and Puppeteer for screenshot capture, device management, gestures, navigation, and DOM interaction.
      5 npm
      2
      MIT

    • selenium-mcp

      masx200
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides browser automation using Selenium, supporting Chrome and Firefox, with tools for navigation, element interaction, screenshots, and more.
      1
      Mulan Permissive Software , Version 2
    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 15 tools

    Disambiguation5/5

    Each tool maps to a distinct browser action or session/tab operation. Snapshot vs screenshot and evaluate vs click/type are clearly differentiated by their descriptions. No two tools appear to do the same thing.

    Naming Consistency4/5

    All tools share the rnw_ prefix and snake_case, which makes them readable and groupable. However, the internal pattern is not uniformly verb_noun (e.g., rnw_tabs_list, rnw_session_status vs rnw_navigate, rnw_click), so there are minor deviations.

    Tool Count5/5

    15 tools for a browser automation server is well within the useful range. Each tool covers a necessary primitive: navigation, inspection, interaction, tab management, and session lifecycle. No obvious redundancy.

    Completeness4/5

    Core browser automation lifecycle is covered, including navigation, interaction, tab management, and session teardown. Advanced interactions like hover, drag, file upload, iframe handling, or network interception are absent, but agents can work around many via rnw_evaluate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources