react-perf-mcp
Related Servers
Alternatives to react-perf-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceA comprehensive MCP server for frontend analysis. It provides Google Lighthouse audits, code quality checks, SEO metadata verification, accessibility analysis, and bundle optimization for React and Next.js projects.83-
- AlicenseAqualityDmaintenanceEnables AI agents to profile React applications, detect performance bottlenecks, and automatically apply fixes like memoization and code hoisting.1337 npm2MIT
- AlicenseBqualityBmaintenanceAn MCP server that gives AI agents hands-on control of a live React Native app, enabling UI taps, screenshots, UI/component trees, native logs, and JS/React profiling to debug, verify fixes, and diagnose performance issues.167 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that decodes V8 CPU profiles into token-efficient bottleneck summaries for AI agents, enabling them to analyze CPU consumption, call trees, GC pressure, and async bottlenecks.628 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that captures and analyzes function-level profiling data from NetEase Minecraft Bedrock Edition mods via the native Tracy profiler, enabling AI to identify performance hotspots and verify optimizations.620MIT
- AlicenseAqualityDmaintenanceMCP server that gives AI coding agents hands, eyes and a mechanic's ear for React Native development.912 npm2MIT
TDQS
Scored across 2 tools
The two tools are clearly differentiated by input: one accepts a code snippet directly, the other reads a file from disk. While they share the same review purpose, the distinct input mechanisms prevent meaningful confusion.
Both tool names follow the consistent verb_noun pattern (review_code, review_file), making the naming predictable and easy to understand.
With only two tools, the server feels minimal for its intended scope. The count is borderline but acceptable for a focused performance-review utility, though it could benefit from additional entry points.
The tool surface covers two common input modes but lacks broader workflow support, such as analyzing a project directory, comparing branches, or generating reports. Agents may need to work around these missing capabilities.