Perfonext Profiler MCP

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-profiler-mcp

About

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, install config and code. Checked Nov 1, 2026.

Tools

9 read · 0 write · 0 deleteRead-only

Secrets

None asked for

Install scripts

None found

Runs as

Node.js package

Tools (9)

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

• compare_profilesCompare Profiles

  Compare two loaded CPU profiles side-by-side. Shows functions that got slower/faster and new/removed hotspots.

• explain_functionExplain 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_hotspotsGet 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_costsGet Package Costs

  Aggregate CPU self-time by npm package. Identifies which third-party dependencies are consuming the most CPU, by parsing node_modules paths from the profile. Useful for deciding which packages to replace, lazy-load, or avoid. Scoped packages (e.g. @babel/core) are handled correctly.

• get_profile_summaryGet 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_collectHow To Collect a CPU Profile

  Returns a ready-to-run command and step-by-step recipe for capturing a V8 CPU profile, then loading it with load_profile. Use this when you do not yet have a .cpuprofile file. Choose the scenario that matches how the code runs.

• load_profileLoad CPU 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_contextRead Source Context

  Read the actual source code for a hot function and annotate each line with sampled tick counts from positionTicks. The returned window is sized to cover the function's actual hot lines, not just the area around its declaration; if any ticks still fall outside it, a `warning` field reports how many and suggests a larger contextLines. Only reads files within the project root.

• suggest_optimizationsSuggest Optimizations

  Analyzes the profile and returns structured optimization suggestions for the hottest functions. Detects high fan-in, recursion, dominant callers, V8-specific patterns, always reports CPU self-time cost for expensive functions, and deduplicates functions split across multiple call sites.

Signals

Stars

0

Forks

0

Open issues

0

Last commit

Oct 10, 2026 (28 days ago)

Last release

Sep 11, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.souvikdu/perfonext-profiler-mcp

Version

0.7.3

Auth

No auth

Packages

npm @perfonext/profiler-mcp

License

MIT

Repository

github.com/souvikdu/perfonext-profiler-mcp

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql