Skip to main content
Glama
jiahuidegit

SSH MCP Server

by jiahuidegit

shell_send

Send commands, passwords, or selections to a persistent SSH shell session for multi-step interactions like bastion host logins. Specify server by alias or host.

Instructions

发送输入到持久化 shell 会话(用于多轮交互,如堡垒机穿透登录流程)。必须指定目标服务器:使用 alias(推荐)或 host。只有一个活跃连接时可省略目标。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes要发送的输入内容(如命令、密码、选择项等)
aliasNo服务器别名(推荐)
hostNo服务器地址(多个活跃连接时必须指定 alias 或 host,单连接时可省略)
portNoSSH 端口(可选)
usernameNo用户名(可选,配合 host 使用)
timeoutNo等待响应超时时间(毫秒,默认 10000,最小 1000)
waitForPromptNo是否等待提示符出现(默认 true)
clearBufferNo发送前是否先清空输出缓冲区(默认 false)
confirmationTokenNo危险命令确认 token
targetConfirmationTokenNo服务器切换确认 token
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions persistence but fails to describe side effects (e.g., sending commands, potential risks), auth requirements, or error handling. The description is insufficient for safe usage without annotations.

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 concise with two sentences, front-loading the purpose and target rules. Every sentence provides actionable information without redundancy or fluff.

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

Completeness2/5

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

With 10 parameters and no output schema, the description is too minimal. It does not explain return values, how to read responses (despite a sibling shell_read), or the behavior after input is sent. For a multi-turn interaction tool, this leaves significant gaps.

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 coverage is 100%, so baseline is 3. The description adds minor context about target specification (alias/host) but does not elaborate on other parameters like confirmation tokens, waitForPrompt, or timeout beyond what the schema already provides.

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 sends input to a persistent shell session for multi-turn interactions like bastion host login. It specifies the target requirement (alias or host) and differentiates from siblings by emphasizing persistence and interactivity.

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 explicitly states when to specify target (alias/host) and that target can be omitted when only one connection exists. It implies use for persistent sessions but does not explicitly exclude alternatives like exec or shell_close.

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/jiahuidegit/ssh-mcp-server'

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