Skip to main content
Glama

rendertrail

MCP App that records how React components render in headless Chrome and explains the main performance problem in a card inside Claude

Development

Needs Node 22 or later.

npm install
npm run build          # card -> dist/card.html, server -> dist/server.js, dist/instrument.js
npm test               # unit tests
npm run test:golden    # builds, then golden tests: records fixtures/ in your installed Chrome
node dist/server.js    # the MCP server over stdio
npm run start:http     # the MCP server over HTTP, for the ext-apps basic-host
cd spike && npm install && RT_CHANNEL=chrome npm run record   # the recorder spike (Git Bash)
cd spike; npm install; $env:RT_CHANNEL='chrome'; npm run record   # the same in PowerShell

The recorder uses your installed Google Chrome. Without Chrome, install Playwright's Chromium (about 150 MB) once with npx playwright-core install chromium.

Connect it to Claude Code with claude mcp add rendertrail -- node <absolute path>/dist/server.js, or to Claude Desktop with an mcpServers entry that runs node <absolute path>/dist/server.js.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Bridges unnecessary React re-render data from the browser to coding agents, enabling performance diagnosis and optimization through MCP tools.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to ask about render performance in React and React Native apps via natural language, exposing tools for listing render hotspots and explaining component re-renders.
      MIT