ssh_systemctl_enable

Enable systemd units on remote hosts via SSH for boot startup.

6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-systemctl-enable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh_systemctl_enable
Source: https://github.com/Nightreaver/python-ssh-mcp/tree/main/skills/ssh-systemctl-enable
Command: npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-systemctl-enable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need to programmatically enable systemd units on remote hosts, ensuring that specific services start on boot without manual intervention.

Core Features & Use Cases

  • Remote Unit Enablement: Automates the process of enabling systemd units on remote hosts.
  • Access Control: Hidden by default, accessible only if ALLOW_DANGEROUS_TOOLS=true.
  • Use Case: Ideal for system administrators who want to ensure that critical services like web servers or databases start automatically on boot without manually enabling them.

Quick Start

Enable the 'nginx.service' on the remote host 'web01' for boot-up.

Frequently Asked Questions about ssh_systemctl_enable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable a systemd service on a remote server to start on boot?

To enable a systemd service on a remote server, this Skill automates the SSH connection and executes the enablement command, ensuring the specified unit starts automatically on boot without manual login.

Do I need root access to enable systemd units on remote hosts?

Yes, enabling systemd units on remote hosts requires root access. Additionally, this Skill is hidden by default and requires the environment variable ALLOW_DANGEROUS_TOOLS to be set to true to permit execution.

Can I automate systemd service enablement for multiple remote machines?

You can automate systemd service enablement for remote machines by specifying the target host and service unit, which programmatically configures the boot-up startup state over SSH without manual intervention.

Why is the remote systemd enablement tool hidden by default?

The remote systemd enablement tool is hidden by default because it requires root access to modify boot-up services, posing potential system risks. It is restricted unless ALLOW_DANGEROUS_TOOLS is explicitly enabled.

What is the best way to ensure critical services like nginx start automatically on boot?

The best way to ensure services like nginx start automatically on boot is to programmatically enable the systemd unit via SSH, which configures the service startup state without requiring manual server administration.