Skip to content
Agentmart
Submit a tool

Perfonext Render MCP

MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components.

Connector by souvikdu · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/souvikdu-perfonext-render-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

MCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
6 read · 2 write · 0 delete · 2 not yet classified
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 10

Read from the source code; the running server may list different tools.

Read 6 · Look things up without changing anything.

  • compare_renders
  • get_captured_renders
  • get_hot_commits
  • get_render_summary
  • get_rerender_causes
  • get_slow_components

Write 2 · Create, change, send or run things.

  • run_render_capture
  • stop_render_capture

Not yet classified 2 · We could not tell from the name and description.

  • begin_render_analysis
  • load_render_profile

Files it touches

  • Any path the agent passes to its tools

Tools (10)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • begin_render_analysisBegin Render Analysis

    Entry point for render profiling. Choose an approach: live — react-scan/lite streams events in real time; exact rerender causes, source locations, changeDescription. manual — no install needed; user exports a JSON from the React DevTools Profiler tab and shares the file path. Ask the user which approach they prefer before calling this tool.

  • compare_rendersCompare Renders

    Diff two loaded render profiles and rank the biggest regressions, improvements, additions, and removals.

  • get_captured_rendersGet Captured Renders

    Optional diagnostic: peek at the live progress of a render-capture session without stopping it. Returns commit count, components seen, whether actualDuration is populating, and an unknownEvents count (non-zero = instrumentation may not be wired correctly). Only call this if something seems wrong — it is not a required step before stop_render_capture.

  • get_hot_commitsGet Hot Commits

    Rank the most expensive commits in a loaded render profile and show the top components inside each spike.

  • get_render_summaryGet Render Summary

    Summarize the loaded Next.js render profile, including top components by render cost and detected render issues (rerender storms, commit spikes).

  • get_rerender_causesGet Rerender Causes

    Highlight components with repeated rerenders and explain likely causes using heuristics derived from the exported profile.

  • get_slow_componentsGet Slow Components

    Return the slowest components in a loaded Next.js render profile, ranked by total actual render time.

  • load_render_profileLoad Render Profile

    Load a React DevTools Profiler JSON export. This is the entry point for the manual profiling path: open React DevTools in the browser → Profiler tab → Record → interact → Stop → Export JSON → share the file path here. Returns a profileId for use with get_render_summary, get_slow_components, get_rerender_causes, and the other analysis tools.

  • run_render_captureRun Render Capture

    Called after instrumentation is wired up (steps 1–3 of begin_render_analysis). Ask the user how they want to generate renders before calling this tool: manual-interaction — start the dev server and the user clicks through the app. test-suite — run an existing automated test suite against the running app.

  • stop_render_captureStop Render Capture

    Stop a live render-capture session, finalize the buffered events into a render profile, and return a profileId you can use with get_render_summary, get_slow_components, get_rerender_causes, and compare_renders.

Signals

Stars
0
Forks
0
Open issues
0
Last commit
Oct 7, 2026 (22 days ago)
Last release
Sep 11, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name
io.github.souvikdu/perfonext-render-mcp
Version
0.5.2
Auth
No auth
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from souvikdu

Cite this page

Perfonext Render MCP. Agent Mart. https://agentmart.dev/connectors/souvikdu-perfonext-render-mcp (last updated 2026-10-24)