Skip to main content
Glama
zeshuochen

nekoro-browser-mcp

by zeshuochen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nekoro-browser-mcp

No user-submitted related servers found.

    Related Servers

    • Browser MCP by BrowserMCP

      Browser MCPofficial

      BrowserMCP
      A
      license
      Not graded
      quality
      F
      maintenance
      Automate your browser with AI using a Chrome extension and MCP server, enabling logged-in sessions and stealth automation.
      7,578 npm
      7,062
      Apache 2.0

    • chrome-bridge-mcp

      ShalomObongo
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets coding tools drive an already-running, logged-in Chrome using its real profile and cookies, providing tools for tabs, navigation, clicks, typing, and more via CDP.
      345 npm
      MIT

    • BrowserMCP

      Smotree
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that provides AI assistants with full control over a real browser session via a Chrome extension, supporting 36 tools for navigation, data extraction, and DOM manipulation. It bypasses bot detection by utilizing the user's active browser session, including cookies, authentication tokens, and installed extensions.
      18 npm
      3
      MIT

    • browseros-mcp

      dreamsxin
      F
      license
      Not graded
      quality
      B
      maintenance
      Standalone browser automation MCP server supporting both BrowserOS and standard Chrome. Enables 16 MCP tools for browser control including navigation, interaction, and content extraction.
      8 npm
      -
    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

    C2.6/5.0

    Scored across 53 tools

    Disambiguation2/5

    The older locator-specific click tools (`click_selector`, `click_text`, `click_index`) are largely redundant with the unified `click` tool, which explicitly says callers should not need to choose between them. Additional overlap exists among `state`/`refs`/`box_of`, the different scroll tools, and the universal escape hatches `cdp` and `exec_python`, making automatic tool selection fuzzy.

    Naming Consistency4/5

    Most tools follow a clear snake_case verb_noun pattern (`close_tab`, `wait_for_load`, `scroll_into_view`, `switch_tab`, `upload_file`), and the specialized interaction variants are named predictably. The main deviations are bare nouns like `state`, `refs`, `cdp`, and `box_of`, plus the generic `click` tool sitting beside its named variants, but these are minor relative to the overall set.

    Tool Count1/5

    With 53 tools, the server is well past the 50+ extreme threshold, and much of that size comes from redundant click variants, low-level CDP plumbing, and maintenance/debug helpers (`reload_extension`, `reload_agent_helpers`, `exec_python`, `drain_events`). A coherent public-facing browser MCP could provide the same capability in roughly 15–20 well-chosen tools by having `click` absorb the outdated variants and exposing CDP/`exec_python` through a single escape hatch.

    Completeness4/5

    The tool set covers the full lifecycle of browser automation: navigation, tab management, page interpretation, DOM interaction, wait conditions, screenshots, iframes, cookies, network interception, uploads/downloads, scrolling/reads, and even frame details. Minor gaps like explicit browser history back/forward and full cookie deletion are workaround-able via `navigate` and `cdp`, but they are noticeable in an otherwise richly featured set.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources