Skip to main content
Glama
Echoqili

ssh-licco

by Echoqili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ssh_execute

Execute shell commands on remote SSH servers. Auto-connect using environment variables or saved hosts, with background 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

TableJSON 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_dangerousNoBypass security validation for known-dangerous commands (e.g. rm -rf /path). Use with caution — only for operations you explicitly intend to perform.
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. First observedv2.7.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does add useful behavior: auto-connection, background auto-detection, and persistent sessions via screen/tmux. However, it does not mention potential destructive side effects or the confirmation/backup safety mechanisms that exist in the parameters, which is relevant for arbitrary remote command execution.

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

Conciseness5/5

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

The description is compact and front-loaded with the core action, then gives only the most useful conditional guidance. Every sentence earns its place, with no filler or repetition of schema details.

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?

Given the tool's complexity (17 parameters, no output schema, no annotations), the description covers the main execution flow but leaves important invocation decisions to parameter descriptions, such as sudo prerequisites and dangerous-command confirmation. It is not incomplete, but it is not sufficiently self-contained for an agent operating without deep schema inspection.

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 adds a little context around session_id and session_type, but it does not meaningfully explain parameter precedence such as host vs name vs session_id, or the wait/wait_timeout relationship beyond what the schema already states.

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?

The description clearly states the core action: 'Execute a command on a remote server.' It also gives useful context about connection and background execution modes. It does not explicitly distinguish itself from sibling tools like ssh_process or ssh_file_transfer, but the main intent is unambiguous.

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

Usage Guidelines4/5

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

The description gives actionable guidance: use session_id when available, auto-connect via environment variables otherwise, use background execution for long-running tasks, and use screen/tmux for persistent sessions. It does not explicitly state when not to use the tool or name alternatives, but the conditions provided are clear.

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