Skip to main content
Glama
conquext

neuron-inspector

by conquext
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to neuron-inspector

No user-submitted related servers found.

    Related Servers

    • izan.io

      ekingunoncu
      F
      license
      Not graded
      quality
      C
      maintenance
      Turns your Chrome browser into an MCP server, allowing AI clients to control browser actions like clicking, typing, navigating, and data extraction through custom JavaScript tools.
      28
      -

    • browser-mcp

      Tuanm
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes your Chrome/Edge browser as MCP tools for AI agents, enabling browser automation through a Chrome extension with 47 tools for navigation, interaction, page reading, and more.
      24 npm
      -

    • Chrome MCP Server

      davincinewton
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An extension-based MCP server that enables AI assistants to control your existing Chrome browser, leveraging your active login states and settings for automation. It provides over 20 tools for tasks like semantic tab search, screen capture, network monitoring, and direct element interaction.
      -

    • Chrome MCP Server

      MNIsRed
      A
      license
      Not graded
      quality
      D
      maintenance
      An extension-based MCP server that enables AI assistants to control your browser, leveraging existing sessions and login states for automation and content analysis. It provides over 20 tools for semantic tab search, interactive element manipulation, and network monitoring directly within your daily Chrome environment.
      MIT

    • a11ydriver-mcp

      idugeni
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control Chrome via DevTools CDP and accessibility trees, providing 21 tools for browser automation including tab management, navigation, interactions, and page capture.
      -

    • chrome-control-mcp

      RandyNorthrup
      A
      license
      Not graded
      quality
      A
      maintenance
      A native MCP server that gives AI assistants full Chrome control via the DevTools Protocol and an unpacked extension, including semantic element refs, real input, screenshots, and browser/tab/window management. It exposes 43 callable tools with a visible control overlay and an optional read-only security profile.
      2
      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.1/5.0

    Scored across 92 tools

    Disambiguation3/5

    Many tools are clearly distinct, but there is meaningful overlap among the extraction/composite tools (research_page, research_profiles, search_and_collect, extract_data, extract_to_json), as well as between get_errors/get_logs, monitor_action/snapshot_state+diff_states, and vision_act/click+screenshot. The detailed descriptions help, but an agent could easily select the wrong tool for a task.

    Naming Consistency4/5

    The neuron_ prefix and snake_case convention are used consistently, and most tools follow a verb_noun pattern like get_requests, create_recipe, and delete_cookie. There are deviations such as profile_save, workflow_status, session_checkpoint, and quickstart, but they are minor and don't create serious confusion.

    Tool Count1/5

    With 92 tools, this server is dramatically over-scoped for any single agent-facing surface. Even if the underlying platform is broad, the sheer count makes tool selection expensive and error-prone, and many tools are one-off composite operations rather than distinct primitives.

    Completeness3/5

    The server covers a huge range of browser automation, network inspection, auditing, recipes, sessions, schedules, and monitoring, so many core workflows are supported. However, there are notable gaps: no individual mock deletion, no workflow delete/edit tool, no monitor update/pause, and no standalone wait/hover/drag/upload operations, which makes lifecycle coverage uneven.

    Resources