Skip to main content
Glama
nex-browser

NexBrowser MCP Server

Official
by nex-browser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to NexBrowser MCP Server

No user-submitted related servers found.

    Related Servers

    • local-bridge

      tianshu-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects local tools (browser, shell) to a remote MCP server via reverse-MCP, enabling the server agent to control your local browser and execute shell commands.
      815 npm
      Apache 2.0

    • Real Browser MCP

      ton-to-ton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
      72 npm
      MIT

    • roblox_studio

      Cpleasance
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI IDEs and agents to connect to and control Roblox Studio through the Model Context Protocol, bridging to Studio's native StudioMCP daemon to interact with the active place and DataModel.
      92 PyPI
      MIT

    • browserpilot-mcp

      Fire162
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.
      1
      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

    B3/5.0

    Scored across 64 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (e.g., nex_browser_click vs nex_browser_type vs nex_browser_fill_form). Some potential overlap exists between nex_browser_run_code and nex_browser_evaluate, and between nex_proxy_create and nex_proxy_batch_create, but descriptions clarify the differences (permissions, batch vs single).

    Naming Consistency4/5

    Tools follow a consistent nex_<domain>_<verb> pattern (e.g., nex_browser_list, nex_proxy_create, nex_account_delete). Minor deviations like nex_browser_connection_info and nex_browser_network_requests use noun phrases instead of verb_noun, but the pattern is largely predictable.

    Tool Count2/5

    64 tools is excessive for a browser automation server, even with proxy and account management. Many tools are granular (e.g., key_down, key_up, check, uncheck, select_option) and could be consolidated. This exceeds the typical well-scoped range and risks agent confusion.

    Completeness5/5

    The tool surface covers the full lifecycle: window creation, opening, connecting, navigation, interaction, form filling, screenshots, network/console inspection, proxy management, account management, and group management. No obvious dead ends; workflows like create window -> bind proxy -> open -> connect -> interact -> close are fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources