Run Linux-style commands natively on Windows

Who it is for

If you work on Windows, want to get things done with Linux-style commands, and do not want to install WSL or a virtual machine, this server matches. Officially it can run Linux-style commands on Windows natively and deterministically, with no virtual machine and no WSL. Each command is translated into PowerShell, executed natively on the machine, then returned as output that looks like GNU/Linux.

It is not suitable for non-Windows environments, nor for machines that do not yet have PowerShell 5.1+ or Node.js ≥ 18. The current excerpt does not give tool function names, a parameter table, or an official sample command for “what to run first.” If you need a call signature you can copy as-is, the evidence stops here.

This is not read-only search: after translation, the command executes on the machine. Use it only when you truly want that command to land on this Windows host.

First try in 3 minutes

First confirm three things at once: the system is Windows, built-in PowerShell 5.1 or newer is present, and Node.js ≥ 18. The official recommended main path is to install the CLI globally first, then point the MCP connection at the standard input/output service:

npm install -g fauxnix-cli

After install, point the server start command in the MCP client to fauxnix mcp. The excerpt states that you then point any MCP harness at fauxnix mcp, and that this is the MCP stdio service the agent harness should connect to. The excerpt does not hard-code a config file path, so do not treat a specific client file as confirmed.

Before you act, confirm that the Linux-style command you are about to submit is one you are willing to execute on this machine. The side effect: the command is deterministically translated into PowerShell and executed natively on the machine. The excerpt does not specify what the first command must be, so do not write an unseen command name as an official example. After that confirmation, send this one request.

The success signal is output that looks like GNU/Linux, not a message that Node.js is missing, that the PowerShell version is too low, or that fauxnix / fauxnix mcp cannot start. Do not treat this execution as no network, no local reads, or no privacy boundary.

Use cases

Case 1: Execute one Linux-style command on this Windows host and view GNU/Linux-like output. The excerpt states it deterministically translates each command into PowerShell, executes it natively, then returns output that looks like GNU/Linux. Confirm the command content first, then submit. What can be confirmed is only “translate and execute natively, then give Linux-like output”; which commands are supported and the error-text format do not fully appear in the current excerpt.

Case 2: Let an agent harness connect to this MCP service over standard input/output. The excerpt states the command to run the MCP stdio service is fauxnix mcp, and that this is the entry the harness should connect to. On success the client should be able to connect to that stdio service. The excerpt also mentions fauxnix install --claude, but does not explain which files it changes; do not treat it as the main installer on the first try, and do not treat an unwritten write scope as confirmed.

These two cases correspond to “execute one command” and “attach a harness over stdio.” Do not merge them into one unconfirmed call.

Limits

Runtime preconditions are Windows, PowerShell 5.1+, and Node.js ≥ 18. The main install path is npm install -g fauxnix-cli, and the main connect command is fauxnix mcp. It explicitly does not depend on a virtual machine or WSL, but what you get instead is native PowerShell execution, not a run inside an isolated distro.

The official page is https://github.com/20000419/fauxnix . The excerpt does not give credential fields, a client list, revoke steps, or a command-coverage table. Do not invent missing command names, and do not treat “no WSL required” as zero risk or freely rollbackable.