Skip to main content
Glama
Sign In
perfonext-render-mcp

perfonext-render-mcp

by souvikdu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to perfonext-render-mcp

  • perfonext-profiler-mcp

    souvikdu
    A
    license
    A
    quality
    B
    maintenance
    Analyze V8/Chrome CPU profiles in Next.js & Node.js apps. Hotspots, package cost attribution, and optimization suggestions for MCP clients like Claude Code and GitHub Copilot
    9
    62 npm
    MIT

Related Servers

  • Debugger MCP Server

    Phoenixrr2113
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides real-time debugging, code quality monitoring, and performance insights for React/Next.js applications with features including Chrome DevTools integration, breakpoint management, complexity analysis, and live error streaming.
    13 npm
    1
    MIT

  • recount

    dainemawer
    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

  • BIP Monitor MCP Server

    The-Bip-App
    A
    license
    B
    quality
    D
    maintenance
    Monitors Next.js development servers with intelligent error categorization, smart diagnostics, and performance tracking.
    8
    MIT

  • react-performance-mcp

    JoseanAyala
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to inspect why React components re-rendered, replay recorded browser interactions as performance scenarios in headless Chrome, and verify fixes against performance budgets.
    MIT
Deploy Server
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

A4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools are clearly separated by role: capture lifecycle (begin/run/stop/diagnostic), manual loading, and distinct analysis outputs. The main ambiguity is that both begin_render_analysis and load_render_profile are described as entry points for the manual path, and get_render_summary/get_hot_commits both mention commit spikes, though descriptions are specific enough to disambiguate.

Naming Consistency5/5

All tool names follow a predictable snake_case verb_noun pattern. Analysis tools use get_ or compare_, capture lifecycle tools use begin/run/stop, and the manual path uses load_, so an agent can infer the role of each tool from its name.

Tool Count5/5

Ten tools is well-scoped for a render-profiling server: there are enough tools to cover both manual and live capture workflows plus analysis, but none feel redundant or purely decorative. Each tool earns its place in a focused pipeline.

Completeness4/5

The core profiling workflows are well covered: manual JSON loading and live capture both lead to analysis tools, and compare_renders adds regression diffing. The only minor gaps are profile-management conveniences like listing loaded profiles or deleting them, and there is no deep single-commit flamegraph drill-down beyond get_hot_commits.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues

Resources