Empower your workflow with WinWraper
WinWraper is a Windows app that helps you manage multiple processes (Node.js, Python, Next.js, EXE) from a single intuitive dashboard. Specially designed for non-technical users: confidently run open-source apps directly from downloaded source code without complex build steps, tedious cmd terminal commands, or VS Code. Everything is monitored intelligently, with auto-restart on crash and 24/7 reliability.
Multi-process dashboard
Manage Node.js, Python, Next.js and EXE apps from one table: status, CPU, RAM, uptime and crash count. Everything updates in real time. Start / stop / restart per app or in bulk.
Auto-restart + crash-loop protection
On crash, WinWraper restarts the app after a short delay. If an app crashes repeatedly in quick succession, WinWraper pauses retries to protect your machine resources - fix the issue, hit Reset, and it's back.
Minimize to system tray
WinWraper can collapse to the system tray to free up your taskbar. Right-click the tray icon for Start All / Stop All / Restart All / restore the main window. Your apps keep running in the background as normal.
24-hour CPU / RAM charts
The Metrics window plots CPU (%) and RAM (MB) for the last 24 hours. Hover over any point to see the exact values.
Watcher - full event log
Watcher records the full lifecycle of each process: starting, running, stopping, auto-restart, error and more.
Multiple script types
EXE, Node.js, Python, Next.js and Custom interpreter. WinWraper auto-detects the right runtime and pre-fills it for you.
Register as Windows Service
Register any app - including Node.js / Python - as a real Windows Service. Starts with Windows even when nobody is logged in. Toggle from the dashboard or over MCP.
🫥 Hide App Window, Window Cloak
Completely hide the application window and its icon on the Taskbar, turning any program into a background process while maintaining 100% normal operation. Extremely easy to use: just right-click the application -> select "Hide Window". Particularly useful for running multiple UI applications in the background while keeping a clutter-free desktop, with the ability to easily start, stop, restart, and toggle window visibility (e.g. running MT5/MT4 EAs, or other background software that clutter your screen).
OpenClaw, install & zero-config MCP setup
Install OpenClaw via Quick Add in WinWraper: a step-by-step wizard handles the setup. The key advantage, while installing, WinWraper simultaneously auto-configures its own MCP client so OpenClaw can control WinWraper immediately after install, with no extra steps needed. ⚠️ Note: OpenClaw is an automated AI system with the ability to execute commands on your machine. By enabling this feature, you acknowledge and accept all risks related to system security and data protection. We are not responsible for any data loss, system damage, or security incidents caused by OpenClaw on your device.
Stdio vs HTTP/SSE: Which Protocol fits your needs?
WinWraper supports both of these robust communication methods to interact with the MCP server. Consequently, you can seamlessly control WinWraper.MCP from standard Windows applications, or even call it directly from an AI agent running inside WSL2 (Linux). Let's compare them below to help you decide.
Stdio Transport (Default)
Direct process communication using Standard Input/Output with the WinWraper.MCP.exe executable. Absolutely secure with no port exposure.
- ✓Secure by Default: Limited strictly to the logged-in desktop user context.
- ✓Zero Network Overhead: Commits lightning-fast updates bypassing any TCP routing.
- ✓Best For: IDEs and clients like Claude Desktop or Cursor running locally on Windows.
HTTP / SSE Transport
Bridges events over HTTP SSE via local port 15432. Smoothly traverses path virtualization and permission layers.
- ✓WSL2 & Linux Friendly: Query WinWraper tools from virtualized environments.
- ✓Zero-Path Setup: Connect using simple HTTP endpoints rather than rigid paths.
- ✓Best For: Docker containers, WSL2 pipelines, and non-stdio web integrations.
MCP Server - control with AI agents
WinWraper ships with a built-in MCP (Model Context Protocol) Server reachable over stdio or Windows Named Pipe. Claude, Cursor, GitHub Copilot, Windsurf, OpenClaw or any MCP-compatible agent can use the 15 tools below to manage your processes for you.
Click the scenarios below to see how the AI automates WinWraper via natural language.
| Tool Command | Description |
|---|---|
get_all | Snapshot of every service: status, uptime, RAM, CPU, crash count, Windows Service status. |
get_one | Detailed info for one service by name. |
start | Start one or more services (comma-separated names). |
stop | Stop one or more services. |
restart | Restart one or more services. |
start_all | Start every service in one call. |
stop_all | Stop every service in one call. |
restart_all | Restart every service in one call. |
register_win_service | Register a service as a real Windows Service via SCM (admin required). |
unregister_win_service | Unregister a Windows Service. Stops it first if running. |
start_service | Start a registered Windows Service via SCM. |
stop_service | Stop a registered Windows Service via SCM. |
show_window | Remotely show the WinWraper window (creates it if needed). |
hide_window | Hide the WinWraper window into the system tray. |
get_license_info | Read license status: email, validity, expiry, days remaining. |
Using OpenClaw? No manual MCP setup needed.Zero Setup
When you install OpenClaw via WinWraper's Quick Add feature, WinWraper simultaneously auto-configures the MCP client for OpenClaw during the installation process. Result: the moment the wizard finishes, OpenClaw is ready to control WinWraper, no further steps required.
Add WinWraper MCP Server to your AI client
After installation, WinWraper.MCP.exe sits next to WinWraper.exe (default: C:\Programs\WinWraper\). Open WinWraper first, then add the matching configuration below to your AI client and restart the client to start controlling WinWraper with AI. 💡 Using OpenClaw? When you install OpenClaw via Quick Add in WinWraper, this step is done for you automatically, WinWraper configures the MCP client during installation, so you can control WinWraper through OpenClaw the moment setup finishes.
Select Transport Mode
Use Stdio for local desktop apps or SSE for WSL2/Virtual networks
{
"mcpServers": {
"winwraper": {
"command": "C:\\Program Files\\WinWraper\\WinWraper.MCP.exe"
}
}
}⚠ C:\Programs\WinWraper\WinWraper.MCP.exe is the default install location - adjust it if you installed WinWraper elsewhere. Backslashes in JSON must be escaped as \\. WinWraper.MCP.exe and WinWraper.exe must run on the same machine - they communicate over a local Windows Named Pipe, so WinWraper must be running for the MCP tools to work.
Ready to try?
Order the monthly plan and receive your license key by email.