Wakeonlan MCP Server

Name: Wakeonlan MCP Server
Author: cyanheads

by cyanheadsversion 0.2.0i★ –iRuns on your computer

Registry nameio.github.cyanheads/wakeonlan-mcp-server

Install

Overview

Description from the maker (original English)

Wake LAN machines with Wake-on-LAN magic packets from host profiles, then confirm they came up.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio, Streamable HTTP
Category: Other
You need to fill in: WOL_HOSTS

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: WOL_HOSTS_FILE, WOL_HOSTS, MCP_LOG_LEVEL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "wakeonlan": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/wakeonlan-mcp-server"
      ],
      "env": {
        "WOL_HOSTS_FILE": "your-value",
        "WOL_HOSTS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add wakeonlan --env WOL_HOSTS_FILE=your-value --env WOL_HOSTS=your-value --env MCP_LOG_LEVEL=your-value -- npx -y @cyanheads/wakeonlan-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "wakeonlan": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/wakeonlan-mcp-server"
      ],
      "env": {
        "WOL_HOSTS_FILE": "your-value",
        "WOL_HOSTS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "wakeonlan": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/wakeonlan-mcp-server"
      ],
      "env": {
        "WOL_HOSTS_FILE": "your-value",
        "WOL_HOSTS": "your-value",
        "MCP_LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

WOL_HOSTS_FILE env
Absolute path to the JSON hosts file (a leading ~/ expands to the home directory). Mutually exclusive with WOL_HOSTS.
WOL_HOSTS secret env
The hosts document as inline JSON, for single-host setups. Mutually exclusive with WOL_HOSTS_FILE.
MCP_LOG_LEVEL env
Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account cyanheads, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18374 servers in this category
Published to the registry more recently than 80% of the other 18374 servers in this category
Basic checks equal to or better than 100% of the other 18374 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Wakeonlan MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: WOL_HOSTS

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Happo

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Happo

by happo.io

Review Happo's visual and accessibility diffs: inspect comparisons, accept or reject, report flakes.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@cyanheads/wakeonlan-mcp-server Wake LAN machines with Wake-on-LAN magic packets from host profiles, then confirm they came up via MCP. STDIO or Streamable HTTP. 4 Tools

Overview

Wake-on-LAN by name for the machines on your network. Wake a sleeping desktop, GPU box, NAS, or lab machine, wait until it answers on a port like SSH, check whether a host is up without waking it, and troubleshoot a wake that didn't take. Runs on any machine on the same LAN as its hosts.

Tools

Tool	Description
`wol_wake_host`	Send magic packets to a configured host, then wait for its TCP check port to answer
`wol_check_host`	Probe a configured host's check port once, without sending a magic packet
`wol_list_hosts`	List the host profiles and whether this machine is attached to each host's subnet
`wol_list_reference`	Wake-on-LAN reference by topic: packet format, target setup, power states, troubleshooting, profile format, sender traps

Skills

Skill	Description
`wakeonlan-guide`	When a wake is warranted versus a status check, how to read `refused`, `no_answer`, and `not_reachable` before calling a machine off or a wake failed, which wake-failure checks need a person at the target, and how to add a host

Served over MCP as skill://wakeonlan-guide/SKILL.md and shipped in the npm package under skills/.

Capability reference

`wol_wake_host` tool

alias (from wol_list_hosts, case-insensitive) plus optional wait_for_s, 0–55 seconds, default 30; 0 sends and returns without checking. Sends 3 packets 500 ms apart, probing the check port once before sending and every 2 s after the first packet
state is already_awake, awake (with time_to_answer_ms, an upper bound at the 2 s poll interval), not_reachable, or unverified (unverified_reason: wait_disabled or no_address); the last two carry a guidance next step
Fails as unknown_host, off_segment (nothing sent: this machine has no interface on the host's subnet), retryable wake_in_progress (nothing sent: another call is already waking that host, and one wake per host runs at a time), or retryable socket_error, whose data carries the failed stage and packets_sent

`wol_check_host` tool

alias only: one TCP connect to the profile's address and check_port (22 unless the profile sets another), 1.5 s timeout, no magic packet. The port is not an input, so the tool can't scan arbitrary ports
outcome is open, refused (the machine answered, nothing listens on that port), or no_answer; reachable is true only for open, and latency_ms is present for open and refused
Fails as unknown_host, or no_address when the profile has no address to probe

`wol_list_hosts` tool

No input. Returns every profile in config order: alias, description, mac, address, check_port, wol_port, broadcast with broadcast_source (configured, derived, or unresolved), and secureon_set (never the password)
on_segment, with the sending interface and local_address when true, is resolved against this machine's interfaces on every call; nothing is sent or probed, so it says nothing about whether a host is up
config_source (file, inline, or none) and config_path name where the profiles came from

`wol_list_reference` tool

topic: packet-format, prerequisites, sleep-states, troubleshooting, host-profiles, or sender-environment
Static markdown with no network access; every response lists all topics for navigation

Features

Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.

Wake-on-LAN-specific:

Operator-configured targets only: callers pass an alias, never a MAC, IP, broadcast address, or port, so an agent or HTTP caller can wake and probe only the hosts you listed. SecureOn passwords stay in the profile, never returned or logged
Subnet-directed broadcasts: the broadcast address is derived from a host's IPv4 address and the matching local interface when the profile omits it, and a host on no local subnet is refused before anything is sent instead of being routed away silently
Wakes are confirmed by a TCP connect to a per-host check_port (SSH by default; RDP or SMB for Windows), not ICMP
The LAN layer is Node's own node:dgram, node:net, and node:os, with no third-party networking dependency

Agent-friendly output:

Results, not errors, for every wait outcome: state plus a guidance next step naming the tool or reference topic to call
Typed failures with recovery hints: unknown_host lists up to 20 configured aliases, off_segment names the local subnets it compared, and on macOS socket_error points at the Local Network permission
refused vs no_answer: a machine that is on but not listening on its check port reads differently from one that never answered. A wake still ends not_reachable either way; probe.last_outcome and guidance say which, so a wrong check_port can be told apart from a failed wake

Getting started

Add the following to your MCP client configuration file, pointing WOL_HOSTS_FILE at your hosts file.

"mcpServers": { "wakeonlan-mcp-server": { "type": "stdio", "command": "bunx", "args": ["@cyanheads/wakeonlan-mcp-server@latest"], "env": { "MCP_TRANSPORT_TYPE": "stdio", "MCP_LOG_LEVEL": "info", "WOL_HOSTS_FILE": "~/.config/wakeonlan/hosts.json" } } } }

Or with npx (no Bun required):

"mcpServers": { "wakeonlan-mcp-server": { "type": "stdio", "command": "npx", "args": ["-y", "@cyanheads/wakeonlan-mcp-server@latest"], "env": { "MCP_TRANSPORT_TYPE": "stdio", "MCP_LOG_LEVEL": "info", "WOL_HOSTS_FILE": "~/.config/wakeonlan/hosts.json" } } } }

The Claude Desktop .mcpb bundle (the install badge above) asks for a hosts file or inline hosts JSON when you install it.

For Streamable HTTP, set the transport and start the server:

MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 WOL_HOSTS_FILE=~/.config/wakeonlan/hosts.json bun run start:http

Server listens at http://localhost:3010/mcp

Prerequisites

Bun v1.4.0 or higher (or Node.js v24+).
A machine attached to the same LAN segment as the hosts it wakes. Run the server on that machine's OS, or in Docker with host networking on Linux: a container on a default bridge network, Docker Desktop on macOS or Windows, or WSL2 in its default NAT mode can't put a broadcast on the LAN.
Targets with Wake-on-LAN enabled in firmware and armed by the OS. wol_list_reference with topic prerequisites has the Windows, Linux, and macOS settings.

macOS: Local Network permission

On macOS 15 and later, sending a UDP broadcast or connecting to a LAN address needs Local Network access, and macOS grants it to the app that launched the server rather than to node:

Launched from	Who holds the permission
Claude Desktop (the `.mcpb` bundle or a JSON config)	Claude Desktop. macOS asks once, and the grant covers every server it launches.
Apple's Terminal, or an SSH session	Allowed automatically, with no prompt.
A third-party terminal or editor (iTerm2, Ghostty, VS Code, Cursor, …)	That app, which gets the prompt.
A `launchd` daemon, or a process running as root	Allowed automatically.
A `launchd` agent	Blocked until granted. Run an always-on server as a daemon instead.

Grant or check it under System Settings > Privacy & Security > Local Network. The first send can fail while the alert is pending, so wol_wake_host may return socket_error; retry after allowing. If that list shows a node entry rather than your client app, enable the node entry. A denied permission also makes wol_check_host read no_answer. Windows and Linux have no per-app gate. wol_list_reference with topic sender-environment covers the rest, including the macOS 15.5+ subnet exemption.

Installation

Clone the repository:

git clone https://github.com/cyanheads/wakeonlan-mcp-server.git

Navigate into the directory:

cd wakeonlan-mcp-server

Install dependencies:

bun install

Configure environment:

cp .env.example .env

edit .env and set WOL_HOSTS_FILE or WOL_HOSTS

Configuration

Variable	Description	Default
`WOL_HOSTS_FILE`	Absolute path to the JSON hosts file; a leading `~/` expands to the home directory. Mutually exclusive with `WOL_HOSTS`.	none
`WOL_HOSTS`	The same JSON array inline, for single-host setups or clients where a file is awkward. Mutually exclusive with `WOL_HOSTS_FILE`.	none
`MCP_TRANSPORT_TYPE`	Transport: `stdio` or `http`.	`stdio`
`MCP_HTTP_HOST`	HTTP bind address. Anything but loopback requires `MCP_AUTH_MODE` `jwt` or `oauth`.	`127.0.0.1`
`MCP_HTTP_PORT`	HTTP server port.	`3010`
`MCP_AUTH_MODE`	Authentication: `none`, `jwt`, or `oauth`.	`none`
`MCP_ALLOWED_ORIGINS`	Comma-separated browser origins allowed on the HTTP endpoint. `*` is refused without `jwt` or `oauth`.	loopback origins
`MCP_SESSION_MODE`	HTTP session mode: `stateless`, `stateful`, or `auto`.	`stateless`
`MCP_LOG_LEVEL`	Log level (`debug`, `info`, `warning`, `error`, etc.).	`info`
`LOGS_DIR`	Directory for log files (Node.js only).	`/logs`
`OTEL_ENABLED`	Enable OpenTelemetry.	`false`

See .env.example for the full list of optional overrides.

Host profiles

Profiles are a JSON array, read once at startup from WOL_HOSTS_FILE or WOL_HOSTS. Set on

Only the beginning is shown; read the rest in the repo

Wakeonlan MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Happo

README from the maker

Overview

Tools

Skills

Capability reference

wol_wake_host tool

wol_check_host tool

wol_list_hosts tool

wol_list_reference tool

Features

Getting started

Server listens at http://localhost:3010/mcp

Prerequisites

macOS: Local Network permission

Installation

edit .env and set WOL_HOSTS_FILE or WOL_HOSTS

Configuration

Host profiles

`wol_wake_host` tool

`wol_check_host` tool

`wol_list_hosts` tool

`wol_list_reference` tool