- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- AI-assisted profiling
- IDE integration
- Profile .NET executable
- Profile ASP.NET application in IIS
- Profile ASP.NET web app on Azure App Service on Linux
- Profile ASP.NET web app on Azure App Service on Windows
- Profile all .NET processes that will start
- Attach profiler to a running application
- Profile remote applications
- Profiling in Docker container
- Manually enable profiling of local applications
- Agent startup options
- Connect to profiled application
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting and FAQ
Cursor
Instructions for integrating YourKit .NET Profiler MCP server with Cursor and Cursor CLI.
Cursor integration from the profiler UI
Use the Profile with AI... action on the Welcome screen or in the Profile menu. Follow the steps in the wizard to configure the YourKit MCP server integration.
Cursor integration from the profiler command line
The following command adds
YourKit-NET-Profiler MCP server to the default configuration.
Optionally, use the -mcp-integrate-config=<path>
parameter to update a different configuration file, for example,
a project configuration.
Linux
<profiler directory>/bin/profiler.sh -mcp-integrate=cursor
macOS
<profiler directory>/Contents/Resources/bin/profiler.sh -mcp-integrate=cursor
Windows
<profiler directory>\bin\profiler.bat -mcp-integrate=cursor