Skip to main content
Glama
jiahuidegit

SSH MCP Server

by jiahuidegit

exec

Execute commands on remote SSH servers with support for alias, timeout, and dangerous command confirmation.

Instructions

在远程服务器执行命令。必须指定目标服务器:使用 alias(推荐,需先 save_server)或使用已连接的 host。只有一个活跃连接时可省略目标。多服务器场景下切换目标时会要求确认。危险命令需要 confirmationToken。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes要执行的命令
aliasNo服务器别名(推荐,需先通过 save_server 保存)
hostNo服务器地址(多个活跃连接时必须指定 alias 或 host,单连接时可省略)
portNoSSH 端口(可选)
usernameNo用户名(可选,配合 host 使用)
timeoutNo命令超时时间(毫秒,最小 1000)
useLongTimeoutNo使用长超时(最长 30 分钟),用于 docker build/npm install 等耗时操作。设置后忽略 timeout 参数
cwdNo工作目录(可选)
confirmationTokenNo危险命令确认 token(首次调用危险命令会返回 token,携带 token 再次调用以确认执行)
targetConfirmationTokenNo服务器切换确认 token(切换目标服务器时返回,确认后重新调用)
Behavior3/5

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

With no annotations, the description carries full burden. It discloses target selection rules and dangerous command handling, but does not mention permissions, side effects, or output behavior. Moderately transparent but incomplete.

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?

Efficient 5-sentence paragraph, front-loaded with purpose, no redundant or irrelevant content. Each sentence contributes unique information.

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?

Covers target specification and dangerous command handling, but does not explain output/return, error behavior, or differentiate from similar siblings. With no output schema, additional context on results would improve completeness.

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 already provides 100% coverage with descriptions. The description adds minor value (e.g., recommending alias) but largely repeats schema info. Baseline 3 is appropriate.

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 'execute command on remote server' (specific verb+resource). However, it does not differentiate from siblings like exec_shell or exec_sudo, which also execute commands, making it less helpful for distinction.

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?

Provides concrete guidance: use alias (preferred) or host, single-connection shortcut, multi-server confirmation requirement, and dangerous command confirmation token. Lacks explicit comparison to alternative tools but gives good operational context.

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