How react-render-profile-mcp works under the hood - and what it found in a real project

I've been building react-render-profile-mcp for a few months — an MCP server that decodes React DevTools Profiler exports so AI agents can diagnose and now fix render performance. Earlier posts covered v0.1 and v0.3.1. This is v1.0.

I want to do two things in this post: show what it actually found on a real open source project, then explain how the engine works inside — because "it's just an MCP wrapper" is not the right mental model. 🐸

Act 1 — What it found on slash-admin

I ran the full cycle on slash-admin, a real React admin dashboard with Zustand and React Router. Target: UserProfile in src/pages/management/user/profile/index.tsx.

Diagnostics