NodePilot MCP
The nodepilot-mcp server drives NodePilot workflows on Windows: 116 tools, with destructive operations disabled by default.
- 116 ★ on the repository
- Last commit
Broad access
Why this level
- Workflows run PowerShell on remote Windows machines, so through NodePilot an agent reaches the estate.
- Deleting workflows and machines and cancelling runs unlock with `NODEPILOT_MCP_ALLOW_DESTRUCTIVE=true`.
Install
- Works in
Manual install
dotnet publish src/NodePilot.Mcp -c Release -o C:\Tools\NodePilot-McpBuild from source. Both NodePilot installers already ship `nodepilot-mcp.exe` in `tools\mcp`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Workflows run PowerShell on remote Windows machines, so through NodePilot an agent reaches the estate.
- Deleting workflows and machines and cancelling runs unlock with `NODEPILOT_MCP_ALLOW_DESTRUCTIVE=true`.
This is third-party code. Review the repository files before installing.
What it does
nodepilot-mcp is a thin HTTP client for the REST API of NodePilot, a platform that automates Windows and PowerShell and runs steps over WinRM with no agents on target machines. Through MCP an agent reads data, creates and edits workflows, runs them and inspects executions. There are 116 tools in 12 groups. Destructive and administrative tools, such as `delete_workflow`, `cancel_all_executions` and `delete_machine`, are not registered at all unless `NODEPILOT_MCP_ALLOW_DESTRUCTIVE=true` is set. The `get_safety_status` call shows the active mode and lists the gated tools.
Who it is for. Sysadmins who automate a Windows estate in NodePilot and want to drive workflows through an agent.
Good fit when
- An agent builds a workflow from PowerShell, REST and SQL steps and publishes it.
- A failed run is diagnosed from step status and output without opening the web UI.
- An agent reads NodePilot data: workflows, executions and versions.
- Destructive operations stay gated while the agent gets reading and editing without deletion.
Not a fit when
- There is no Windows in the infrastructure: the server targets `net10.0-windows` and keeps its session in DPAPI.
- It runs on Linux or in CI without a token: there is no DPAPI session there, so only `NODEPILOT_MCP_TOKEN` works.
- The agent would be allowed to delete workflows and machines unattended.
Example request
Show workflows with failed runs in the last day, diagnose the latest error and propose a fix. Delete nothing.MCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
NODEPILOT_MCP_SERVERrequired- NodePilot server URL
NODEPILOT_MCP_TOKENsecret- Bearer token for CI and headless runs instead of the `np auth login` session
NODEPILOT_MCP_ALLOW_DESTRUCTIVE- The value `true` registers destructive and administrative tools
Limitations
Windows only. A deployed NodePilot and a login with `np auth login` are required. The server does not install as a dotnet tool because of the NETSDK1146 restriction: the executable ships in the installers' `tools\mcp` folder or builds with `dotnet publish`. It runs over stdio and Streamable HTTP is described as a future option. Set the server address and token with `NODEPILOT_MCP_SERVER` and `NODEPILOT_MCP_TOKEN`. A token without refresh suits short runs only.
How to disable. Remove the `nodepilot` entry from the client's `.mcp.json` and delete the executable. Clear the saved `np` session in `%APPDATA%\NodePilot` with the CLI logout.
FAQ
How do I enable destructive tools?
Set `NODEPILOT_MCP_ALLOW_DESTRUCTIVE=true`. Without the variable such tools are invisible to the agent in `tools/list`.
How do I see which tools are gated?
Call `get_safety_status`: it shows the active mode and the list of gated tools.
How do I authenticate without an interactive login?
For CI and headless runs set `NODEPILOT_MCP_TOKEN` to a bearer token. The server does not refresh such a token.
Does the server run on Linux?
No. The `net10.0-windows` build uses DPAPI for session storage, like the rest of NodePilot.
Which transport does the server use?
Stdio only. Streamable HTTP is described in the documentation as a future option.
Discussion
No questions or reviews yet.
Related
MCP serversA Node.js manager for MCP servers: it starts local servers, connects remote ones and gives a client one address, with a REST API for control
MCPM
mcpm
A package manager and registry for MCP on all platforms and clients: finds, adds and configures MCP servers, remembers the source and updates
A secure MCP runtime through which an agent operates local machines, servers and containers
MCP server for Windows: the agent searches apps, tweaks and DNS in the WinUtil CN catalog; installs and edits need a flag and a confirmation
An MCP server for ServiceNow: over 500 tools across ITSM, CMDB and scripting, with write access off by default
Dokploy MCP
Dokploy MCP Server
The official Dokploy MCP gives an agent 508 API tools covering projects, applications, databases, Docker and backups.
README in short
The server adds nothing to the backend: each tool calls an existing NodePilot REST endpoint or computes locally on `NodePilot.Core`. Settings come from environment variables and the `np` profile.