neuron-inspector
Related Servers
Alternatives to neuron-inspector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceTurns 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.28AGPL 3.0
- FlicenseNot gradedqualityBmaintenanceExposes 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.20 npm-
- AlicenseNot gradedqualityNot gradedmaintenanceAn 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.-
- AlicenseNot gradedqualityDmaintenanceAn 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
- AlicenseNot gradedqualityAmaintenanceA local MCP server that enables AI coding assistants to drive the real, already-logged-in Chrome browser — navigating pages, clicking, typing, reading content, taking screenshots, and inspecting tabs, cookies, and network traffic through natural language. It works as a Chrome extension, so no remote-debugging port needs to be opened and pages the user is already signed into are fully usable.1 npmISC
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI coding tools drive your own already-logged-in Chrome through a browser extension, rather than a headless or cookie-copied instance. It exposes 25 tools for snapshotting pages, clicking, typing, reading content, taking screenshots, recording network traffic, and reading cookies or storage, so agents can act on authenticated sites without triggering bot detection.1 npmISC
TDQS
Scored across 92 tools
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.
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.
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.
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.