Replace a website's Node.js environment variables with your specified set. Any variable not included is deleted; an empty list removes all variables, then the Node.js process restarts.
Update or create Node.js build settings for a website, specifying node version, app type, entry file, and more. Fix auto-detection errors like wrong app type or missing entry file.
Enables AI assistants to debug Node.js applications using Chrome DevTools Protocol. Provides comprehensive debugging capabilities including breakpoints, stepping, variable inspection, expression evaluation, and console monitoring.
A basic MCP server that provides arithmetic calculation tools and system information retrieval capabilities, including platform, CPU, and memory details.
Retrieve stored Node.js build settings for a domain to diagnose failed builds—check detected framework, entry file, directories, and package manager, then correct any wrong values.
List Node.js environment variables configured for a website. Values are masked, so use this to verify which keys exist or confirm changes, not to read secrets.
Restarts the Node.js server process for a website to apply environment or configuration changes or recover a hung application. Works for server-side apps; static sites are unaffected.
Clear the Node.js runtime log file for a domain to remove old entries, so subsequent log retrieval returns only fresh data. Ideal before reproducing an issue.
Identify npm package vulnerabilities on a Node.js website, with severity, CVSS, CVE, and advisory metadata, sorted by severity. Filter by severity to prioritize critical issues.
Detect Node.js build settings from a package.json inside an archive on your server, then review or override framework, Node version, directories, and build script before starting a build.
Generate sandbox-safe code examples in cURL, Node.js, or Python for SignalEDI REST operations. Uses environment placeholders and synthetic values, avoids credentials, and sets outbound to SANDBOX.
Retrieve a paginated list of Node.js build processes for a website, filterable by state (pending, running, completed, failed). Use build UUIDs to access detailed logs.
Starts a Node.js build using files already on the server, from an uploaded archive or a Git branch, and returns a build UUID to monitor progress and logs.