Skip to main content
Glama
pmboxbiz

mcp-ssh-live

by pmboxbiz

ssh_connect

Add an SSH host at runtime and open the connection, returning an alias to use with other tools like ssh_exec. Provide credentials via password or key file, or rely on SSH agent.

Instructions

Add a new SSH host at runtime and open the connection. Call this first before using ssh_exec / ssh_spawn / ssh_upload / ssh_download on a new server.

Returns an alias (e.g. 'h-3f8a1b2c') that you pass as the 'host' argument to all other tools. If you supply your own alias it will be used instead.

Auth: provide exactly one of password or key_path. If neither is given, paramiko tries the SSH agent and default key files (~/.ssh/id_*).

Calling ssh_connect again with the same alias updates the credentials and reconnects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesIP address or hostname of the remote server.
userNoSSH username. Default ``root``.root
passwordNoSSH password (plain text). Mutually exclusive with ``key_path``. Passing it here is safe — the value is never logged (only the byte count appears in DEBUG logs), and it lives only in the server process's memory for the duration of the connection.
key_pathNoPath to a private key file on the LOCAL machine running the MCP server. Mutually exclusive with ``password``.
portNoSSH port. Default 22.
aliasNoOptional short name for this host. When omitted, a stable alias is auto-generated from (host, port, user) so the same credentials always produce the same alias. Callers can pass a memorable name like ``"prod"`` or ``"mybox"`` to make subsequent tool calls more readable.
insecure_auto_addNoAccept unknown host keys automatically (paramiko AutoAddPolicy). Default True because this tool is typically called in interactive sessions where the user is actively choosing a target — production pinned deployments should use a TOML config with a known_hosts path instead. Set to False to require the host key to already be in the system known_hosts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses the return alias, authentication fallback, reconnection behavior, and security notes about password logging. It also explains the insecure_auto_add parameter's default and rationale.

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?

Four sentences, each serving a distinct purpose: purpose, alias usage, auth options, reconnection. No redundant or irrelevant information. The description is front-loaded with the most critical information.

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

Completeness5/5

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

Given the tool's complexity, the presence of an output schema, and 13 sibling tools, the description is comprehensive. It explains how to use with siblings, covers authentication, alias generation, security, and reconnection.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by integrating parameters into usage flow (e.g., 'provide exactly one of password or key_path') and explaining alias auto-generation. This goes beyond the schema's individual parameter descriptions.

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

Purpose5/5

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

The description clearly states the tool's purpose: 'Add a new SSH host at runtime and open the connection.' It also explicitly positions it as a prerequisite for other tools (ssh_exec, ssh_spawn, ssh_upload, ssh_download), making its role unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance: 'Call this first before using ssh_exec / ssh_spawn / ssh_upload / ssh_download on a new server.' It also explains alias usage, authentication options (exactly one of password or key_path), and the behavior when calling again with the same alias.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pmboxbiz/mcp-ssh-live'

If you have feedback or need assistance with the MCP directory API, please join our Discord server