MCP Linux Deployment
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Linux Deploymentrestart the Windows web server on host websrv01"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Linux Deployment
This repository contains an MCP server to manage Windows servers from Linux. It is designed for per-user installs under your home directory and does not write system-wide files.
Minimal runtime layout (after running ./scripts/setup.sh):
$HOME/MCPServer/ (per-user target)
bin/ (start, stop, health_check, uninstall)
config/ (application code and
.env)venv/ (Python virtualenv)
logs/
run/
Essentials (what to keep in the repo):
server.py— MCP server entrypoint and tool registrationscripts/— setup/start/stop/health_check/uninstall wrappersrequirements.txt— pinned dependencies
Quick start (per-user)
Make scripts executable
chmod +x scripts/*.shCreate a per-user install (targets $HOME/MCPServer by default)
./scripts/setup.sh --target "$HOME/MCPServer"Edit configuration and credentials
vi "$HOME/MCPServer/config/.env"
# set MCP_HOST, MCP_PORT, WIN_DASH_API_BASE, MCP_API_TOKEN, WIN_DEFAULT_USER, WIN_DEFAULT_PASSStart the server
"$HOME/MCPServer/bin/start.sh"Check health and logs
"$HOME/MCPServer/bin/health_check.sh"
tail -f "$HOME/MCPServer/logs/mcp-server.log"Stop the server
"$HOME/MCPServer/bin/stop.sh"Installing dependencies into the repo venv (dev only)
./venv/bin/python -m pip install -r requirements.txtTroubleshooting highlights
Port binding: This server explicitly starts uvicorn with
host=$MCP_HOSTandport=$MCP_PORT. Default is 0.0.0.0:3000. Check with:
ss -ltnp | grep :${MCP_PORT:-3000}
curl -v http://localhost:${MCP_PORT:-3000}/healthMissing packages: If you see
ModuleNotFoundError, install requirements into the venv used by your install:
"$HOME/MCPServer/venv/bin/python" -m pip install -r requirements.txtLogs and PIDs: logs are at
<install>/logs/mcp-server.log; PID file at<install>/run/mcp-server.pid.
Support
Collect these artifacts if you need help debugging:
tail -n 200 "$HOME/MCPServer/logs/mcp-server.log" > mcp-debug.log
ss -ltnp > ss-output.txt
ps aux | grep server.py > ps-output.txtThis README is compact and contains runtime, install, and key troubleshooting steps to operate the MCP server on Linux.
Related MCP Connectors
A paid remote MCP for ClawManager, built to return verdicts, receipts, usage logs, and audit-ready J
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.