Select your language

Support · FAQ

Use the ASDM MCP Server for AI-driven Wake-on-LAN workflows

The Auto Shutdown Manager (ASDM) MCP Server lets AI agents test connectivity, ping devices and wake managed client PCs by name through the existing ASDM Wake-on-LAN infrastructure.

MCP ServerAI agentsWake-on-LANn8n and VS Code

Quick answer

Download the free MCP Server from the EnviProt downloads page, install it next to ASDM, then connect it to your MCP client.

The MCP Server can expose ASDM Wake-on-LAN actions to AI workflows while ASDM keeps the actual power-management and WOL execution inside the managed enterprise infrastructure. Use it for test labs, development environments and controlled admin workflows.

Download location

Where you download the free MCP Server

Open the EnviProt downloads page and get the free MCP Server add-on. Go to the downloads page, open the Add-ons & Utilities section, and download ASDM_MCPServer.zip from MCP Server (AI-driven WOL).

Download itemASDM_MCPServer.zip in the MCP Server (AI-driven WOL) add-on.
Download pageOpen downloads
Who should use itYou can use it to test AI-assisted Wake-on-LAN workflows in controlled ASDM environments.
Important statusThe MCP Server is a free prototype for testing and development and is provided as-is. Use it in controlled admin/test workflows.

What it exposes

Tools available to AI agents

The MCP Server keeps the interface intentionally focused: test connectivity, check availability and wake known ASDM client PCs by their fully qualified client names.

echo

Quick connection test for the MCP client and the MCP Server.

ping

Verify whether a device is reachable before or after a wake request.

!

wake-client-pc-by-its-pc-name

Wake a client via its FQDN. The name must match the ASDM Management Console Clients Overview.

Why this matters

AI workflow convenience without bypassing ASDM control

Instead of giving an AI workflow direct network power-control responsibility, the MCP Server forwards wake requests to ASDM. ASDM then wakes the specified clients through its existing Wake-on-LAN infrastructure, including WOL proxies across subnets and VLANs.

Keep ASDM as execution layer

AI agents request machine readiness; ASDM remains the managed system that performs the actual WOL action.

Useful across routed networks

Wake requests can use ASDM’s WOL proxies for clients across subnets and VLANs.

Fit for repeatable labs

Development, QA and test environments can be started by name from an AI-assisted workflow.

Installation

Deploy the MCP Server

Install the MCP Server on a machine that also has the ASDM client installed. The ASDM server must already be configured and running.

1

Download and extract

DownloadGet ASDM_MCPServer.zip from the EnviProt downloads page.
ExtractUse the ASDM installation folder on the MCP host.
Required local componentASDM client must be installed on the machine hosting the MCP Server.

Recommended extraction folder:

C:\Program Files (x86)\AutoShutdownManager\
2

Configure ASDM connection

Edit mcp_appsettings.json to match the ASDM server and local WOL client path.

{
  "ASDM_ServerName": "asdmctrl",
  "ASDM_ServerPort": "8088",
  "ASDM_WOW_PATH": "C:\\Program Files (x86)\\AutoShutdownManager\\wow_client.exe"
}
3

Run HTTP or stdio mode

Run the MCP Server as an HTTP service on port 8080 or use --stdio for tight IDE integration.

ASDM_MCPServer.exe
ASDM_MCPServer.exe --stdio

Adjust MCP_HTTP_PORT in mcp_appsettings.json if you change the HTTP port.

4

Test with simple prompts

Wake my test-pc123 if it is offline

wake mainServer.mydomain.com and testserver.mydomain.local

My test environment consists of the following PCs:
pc1, pc2, pc3, pc4, pc5, server1, server2.
Please wake up my test environment.

VS Code

Configure an MCP client

Create or edit .vscode/mcp.json. The original page recommends stdio for tight IDE integration, with HTTP available as an alternative.

stdio mode

{
  "servers": {
    "asdm_stdio": {
      "type": "stdio",
      "command": "C:\\Program Files (x86)\\AutoShutdownManager\\ASDM_MCPServer.exe",
      "args": ["--stdio"]
    }
  }
}

HTTP mode

{
  "servers": {
    "asdm_http": {
      "type": "http",
      "url": "http://localhost:8080/mcp"
    }
  }
}

n8n integration

Use the MCP Server inside an n8n Agent

Add an MCP Client Tool to your n8n Agent and point it at the MCP Server endpoint.

SSE endpointhttp://localhost:8080/mcp/sse
Docker endpointhttp://host.docker.internal:8080/mcp/sse
Test promptecho "Hello World"
Wake testwake test-pc123 if it is offline

FAQ details

Common questions

What can the MCP Server do?

It can echo-test the connection, ping devices and wake ASDM client PCs by their fully qualified PC names.

Does it replace ASDM?

No. The MCP Server forwards requests to ASDM. ASDM remains the managed power-control layer that wakes the clients.

Which ASDM components are required?

An ASDM server must be configured and running, and the ASDM client must be installed on the machine hosting the MCP Server.

Where do I download the MCP Server?

Open the EnviProt downloads page and download ASDM_MCPServer.zip from MCP Server (AI-driven WOL) in the Add-ons & Utilities section.

Is this production software?

No. The MCP Server is described as a free prototype for testing and development purposes and is provided as-is, without warranties. Use it accordingly.

Shut down safely. Wake reliably. Prove the savings.

Bring ASDM Wake-on-LAN into controlled AI workflows

Use the MCP Server to let AI-assisted tools request machine readiness while ASDM continues to provide the central Wake-on-LAN infrastructure and policy-controlled execution.