Perfonext Profiler MCP server

by souvikdu·io.github.souvikdu/perfonext-profiler-mcp·v0.7.3

No reviews yet

MCP server for analyzing V8/Chrome CPU profiles with line-level tick attribution.

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

Growing

0 stars198 downloads/wk

Reviews

Write one

Nobody has reviewed Perfonext Profiler MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Perfonext Profiler MCP tools (9)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

compare_profiles
Compare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.
explain_function
Returns detailed timing info for a specific function: self-time, total-time, callers, and callees. Use this to understand why a function is slow.
get_hotspots
Returns the top N functions by self-time (CPU time spent directly in the function, not its callees). Use this to find performance bottlenecks.
get_package_costs
Aggregate CPU self-time by npm package. Identifies which third-party
get_profile_summary
Returns an overview of a loaded profile: duration, sample count, top-level call tree (filtered to functions >0.1% of total time), and idle time percentage. For large profiles, the call tree is limited to depth 2 and top 20 children per node to keep output manageable. Also lists all loaded profiles if no ID is given.
how_to_collect
Returns a ready-to-run command and step-by-step recipe for capturing a V8
load_profile
Parse and load a V8/Chrome CPU profile from disk. Supports both .cpuprofile files and Chrome DevTools Trace JSON exports. Returns a profile ID for use with other tools.
read_source_context
Read the actual source code for a hot function and annotate each line with
suggest_optimizations
Analyzes the profile and returns structured optimization suggestions for the hottest

Public scan report

scanner v0.1.10 · 2026-10-14 · same rubric, same numbers if you re-run it

no findings

Code scan33 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 2 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Perfonext Profiler MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 92/100; higher than 93% of 48,243 servers
Tools: 9; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
Downloads a week: 198; more than 75% of 12,306 servers with a package

What its tools let an agent do: 9 read

Install Perfonext Profiler MCP in Claude Code, Cursor or VS Code

Runs npx -y @perfonext/profiler-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add perfonext-profiler-mcp -- npx -y @perfonext/profiler-mcp

Add to Cursor

What the publisher says

From the Perfonext Profiler MCP repository's README, as published. We do not edit it. Read it on GitHub

perfonext-profiler-mcp

Analyze V8 and Chrome CPU profiles to find hotspots in Next.js servers and scripts.

perfonext-profiler-mcp is a Model Context Protocol (MCP) server that gives GitHub Copilot, Claude Desktop, Claude Code, and other MCP clients structured CPU profiling data for Next.js performance work. It loads V8 and Chrome CPU profiles and turns them into hotspot rankings, per-package costs, and source-annotated hot lines — evidence agents can reason over instead of ingesting multi-megabyte profile dumps.

Quick Start

perfonext-profiler-mcp is a standard MCP stdio server, so it works with any MCP-compatible client (GitHub Copilot in VS Code, Claude Desktop, Claude Code, Cursor, and others). Run it directly with npx:

npx -y @perfonext/profiler-mcp

Or install globally:

npm install -g @perfonext/profiler-mcp

The executable command remains perfonext-profiler-mcp after installation.

VS Code

Add the server to .vscode/mcp.json (the workspace MCP configuration file):

{
  "servers": {
    "perfonext-profiler": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@perfonext/profiler-mcp"]
    }
  }
}

Reload the VS Code window and run MCP: List Servers to start it, or accept the trust prompt when it appears.

Claude Desktop

Add the server to claudedesktopconfig.json:

{
  "mcpServers": {
    "perfonext-profiler": {
      "command": "npx",
      "args": ["-y", "@perfonext/profiler-mcp"]
    }
  }
}

Restart Claude Desktop to pick up the new server.

Claude Code

Add the server with the CLI:

claude mcp add perfonext-profiler -- npx -y @perfonext/profiler-mcp

Or add the same mcpServers entry to .mcp.json.

Other MCP clients

Any client that supports stdio MCP servers can launch npx -y @perfonext/profiler-mcp. Consult your client's documentation for its MCP server configuration format.

For a locally-built checkout, point command/args at node and the repo's dist/index.js instead.

Troubleshooting

spawn npx ENOENT / spawn node ENOENT on macOS with nvm

If the server fails to start with this error, your GUI MCP client likely cannot see nvm. GUI apps on macOS do not load shell config (.zshrc/.bashrc), so nvm-installed npx/node are not on PATH. Use an absolute npx path and include the same Node directory in PATH:

{
  "servers": {
    "perfonext-profiler": {
      "type": "stdio",
      "command": "/Users/YOU/.nvm/versions/node/v<version>/bin/npx",
      "args": ["-y", "@perfonext/profiler-mcp"],
      "env": {
        "PATH": "/Users/YOU/.nvm/versions/node/v<version>/bin:/usr/bin:/bin"
      }
    }
  }
}

Merge these fields into your client's server entry, under servers for VS Code or mcpServers for Claude Desktop/Code. Then ask your assistant: "How do I capture a CPU profile of my Next.js server?"

What It Does

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Perfonext Profiler MCP: common questions

Is Perfonext Profiler MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the Perfonext Profiler MCP safety report
How do I install Perfonext Profiler MCP?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Perfonext Profiler MCP need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Perfonext Profiler MCP maintained?: The last commit was 24 days ago (2026-10-13). The latest release is v0.7.3.
How does Perfonext Profiler MCP compare with other MCP servers?: safety score 92/100 (higher than 93% of 48,243 servers); tools 9 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.