react-devtools-mcp
Related Servers
Alternatives to react-devtools-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes the React DevTools and TanStack Query/Router state of a Chrome tab to coding agents as MCP tools, enabling inspection, profiling, and mutation of components, queries, and routes from any MCP client.1MIT
- AlicenseBqualityBmaintenanceEnables AI-assisted debugging of React applications by providing browser control, DOM inspection, network monitoring, React DevTools, and error analysis through natural language conversation.396 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to inspect React component trees, props, state, and source locations in Chrome, facilitating UI debugging and analysis.11 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to debug frontend applications by providing direct access to browser DevTools, React state, DOM inspection, and runtime debugging capabilities. Bridges the gap between AI and complex web applications for autonomous debugging and issue resolution.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to profile React applications, detect performance bottlenecks, and automatically apply fixes like memoization and code hoisting.1334 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to deeply analyze and visualize React and React Native codebases locally through 36 free MCP tools for component trees, complexity scoring, navigation, data flow, health audits, and interactive tracing.-
TDQS
Scored across 45 tools
The tools cover distinct operations like connection management, inspection, and overrides, but there is some overlap in purpose. For example, 'get_element_by_id' and 'inspect_element' both retrieve element info, and 'get_profiling_data' vs 'stop_profiling' could cause confusion. Descriptions help differentiate, but the high count increases ambiguity.
Most tools follow a clear verb_noun pattern (e.g., 'capture_screenshot', 'clear_errors_and_warnings'), with consistent snake_case throughout. Minor deviations exist, such as 'log_to_console' using 'to' instead of a direct verb, but overall naming is predictable and readable.
With 45 tools, the count is excessive for a React DevTools server, making it heavy and potentially overwhelming. While the domain is broad, many tools could be consolidated or omitted without losing functionality, indicating poor scoping.
The tool set provides comprehensive coverage for React DevTools operations, including connection management, component inspection, profiling, overrides, and debugging features. There are no obvious gaps; it supports full CRUD-like actions and lifecycle management for the domain.