Skip to main content
Glama
Sign In
ssh-licco

ssh-licco

by Echoqili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ssh_execute

Execute shell commands on remote SSH servers; auto-connects via environment variables and supports background or persistent screen/tmux sessions for long-running tasks.

Instructions

Execute a command on a remote server. If session_id is omitted, auto-connects using environment variables. Supports background execution for long-running tasks (auto-detected or manual). Use session_type='screen' or 'tmux' for persistent sessions that survive SSH disconnect.

Input Schema

NameRequiredDescriptionDefault
hostNoSSH server hostname or IP. Alternative to session_id/name, can override hosts.json entry.
nameNoUse a pre-configured host from hosts.json by name. Alternative to session_id.
portNoSSH port (used with host).
waitNoWait for background task to complete.
commandYesShell command to execute on the remote server (required).
timeoutNoCommand timeout in seconds. Default 120s. For long tasks (docker pull, pg_basebackup), set higher or use background=true.
workdirNoWorking directory for background tasks./tmp
log_fileNoLog file path for background task output./tmp/background_task.log
passwordNoSSH password (used with host).
use_sudoNoWrap command with sudo -S using sudo_password from ssh_connect. Password is passed via stdin, not visible in process list.
usernameNoSSH username (used with host).
backgroundNoRun in background for long-running tasks. Auto-detected if not specified.
session_idNoSession ID from ssh_connect. If omitted, connects via name/host/env vars.
session_typeNoBackground session type: nohup (default), screen, or tmux (persistent).nohup
wait_timeoutNoMax wait time in seconds when wait=True.
confirm_dangerousNoAcknowledge a risky operation. Does not bypass the command allowlist, shell syntax restrictions, or hard blocks.
backup_before_deleteNoFor recursive deletion commands (rm -r/rf), explicitly choose whether to backup targets before deleting. Set true to backup to /tmp/ssh_mcp_backup_<timestamp>/ then delete; set false to delete directly. Required when a recursive deletion is detected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.0
    • changedInput schema / properties / confirm_dangerous / description
      Previous value: -"Bypass security validation for known-dangerous commands (e.g. rm -rf /path). Use with caution — only for operations you explicitly intend to perform."New value: +"Acknowledge a risky operation. Does not bypass the command allowlist, shell syntax restrictions, or hard blocks."
  2. First observedv2.7.2

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It usefully discloses auto-connection behavior, background auto-detection, and survival across SSH disconnect. It omits the most consequential traits — the command allowlist and hard blocks, sudo password delivery, and the mandatory backup decision for recursive deletion — all of which exist only in the schema, not the prose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and followed by the two most agent-relevant behaviors. No filler, though for a tool this complex the brevity trades away needed coverage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter remote-execution tool with no annotations and no output schema, the description covers connection resolution and background/persistence but says nothing about safety gating, sudo semantics, or what a call returns. Adequate to invoke a simple command, insufficient to invoke it safely or correctly in the risky cases the schema anticipates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description reinforces the session_id fallback chain and background auto-detection, but adds little syntax or semantics the schema doesn't already state for its 17 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Execute a command on a remote server.' The connection-fallback and background/persistent-session clauses clarify its scope relative to ssh_connect and ssh_session, though it never explicitly contrasts with ssh_docker or ssh_process, whose command surfaces overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditional guidance for several modes: omit session_id to auto-connect via env vars, use session_type='screen'/'tmux' for persistence, use background for long tasks. However, it offers no exclusion rules or alternatives — an agent cannot tell from the description when to reach for ssh_docker or ssh_process instead, nor when this tool should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools