Run as Admin and Boot Startup

Run-as-Admin and Boot Startup (Windows)

Run-as-admin

Two ways to get Administrator rights.

Per-command elevation

run_command_as_admin triggers a Windows UAC prompt (unless the server is already elevated), runs the command with full rights, and captures its output:

run_command_as_admin { "command": "net session" }

Check current elevation:

is_admin {}

Whole-server elevation

Launch the server with --admin (intended for --http mode, since elevation spawns a fresh console):

uv run lowlevel-computer-use-mcp --http --admin

If not already elevated it relaunches itself through UAC. A stdio server must instead be elevated by its parent client (start Claude Code / Codex as admin).

Auto-start on boot

Registers a Windows Scheduled Task that launches the server automatically at logon — by default with Administrator privileges (RunLevel Highest) and in HTTP mode so it's always available after a reboot. The trigger is an interactive logon (not SYSTEM) so the desktop-automation tools keep access to your session.

Install (admin + HTTP on 127.0.0.1:8765):

uv run lowlevel-computer-use-mcp install-startup

Without admin privileges:

uv run lowlevel-computer-use-mcp install-startup --no-admin

Custom port:

uv run lowlevel-computer-use-mcp install-startup --port 9000

Check status:

uv run lowlevel-computer-use-mcp startup-status

Remove:

uv run lowlevel-computer-use-mcp uninstall-startup

The same operations are exposed as MCP tools: install_startup, uninstall_startup, startup_status. Registering an admin task requires elevation, so a UAC prompt appears if the server isn't already elevated.

Connect a client to the boot HTTP service

claude mcp add --transport http lowlevel-computer-use-boot http://127.0.0.1:8765/mcp