Skip to main content
Glama
Sign In
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.
      2,179 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.
      497 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.
      39 PyPI
      MIT

    • Chrome MCP

      hmumu230-ops
      A
      license
      B
      quality
      C
      maintenance
      Exposes a live Chrome browser to any MCP client through a single local endpoint, enabling real-tab control, DOM interaction, cookies and session use, network/console capture, PDF export, and CDP-powered debugging.
      28
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.1/5.0

    Scored across 96 tools

    Disambiguation2/5

    The 96-tool surface contains several near-duplicates that require careful description reading to distinguish: nex_proxy_create vs nex_proxy_batch_create vs nex_proxy_import, nex_account_create vs nex_account_batch_create, nex_ip_buy vs nex_ip_snap_buy, and three separate CAPTCHA paths (nex_captcha_buy, nex_browser_captcha_*). The prose is unusually explicit, which saves it from a 1, but boundaries between vault accounts (nex_browser_accounts) and catalog accounts (nex_account_list) and between snapshot/get_text/evaluate are not self-evident from names.

    Naming Consistency4/5

    A strong nex_<domain>_<verb> convention runs through the server (nex_proxy_list, nex_sms_buy, nex_mail_record_list, nex_browser_tab_new), and domains are clearly grouped by prefix. Minor deviations exist where nouns replace verbs (nex_browser_connection_info, nex_browser_console_messages, nex_browser_page_title), but the pattern remains predictable.

    Tool Count1/5

    96 tools for a browser-automation-plus-reseller product is a severe mismatch; whole subsystems (SMS, mail, IP, CAPTCHA, billing, proxies, accounts, browser control) are bundled into one surface. Multiple redundant variants (batch_create alongside create-with-items, import alongside create) inflate the count without adding capability.

    Completeness4/5

    Coverage is genuinely broad: environment lifecycle, tabs, navigation, input primitives, snapshots, network/console reads, proxies, accounts, SMS verification, mail, IP purchases and CAPTCHA pipelines. Minor gaps remain around cookie/storage management, downloads, and session persistence, but almost no workflow dead-ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources