Skip to main content
Glama
jiahuidegit

SSH MCP Server

by jiahuidegit

connect

Establish SSH connections to remote servers using a saved alias or by providing host, username, and credentials. Supports password or private key authentication.

Instructions

建立 SSH 连接。两种方式二选一:(1) 通过 alias 连接已保存的服务器;(2) 通过 host + username + password/privateKey 直接连接。使用 alias 时可额外传 password/privateKey 覆盖已存储的凭证。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aliasNo已保存服务器的别名(方式一:与 host+username 二选一)
hostNo服务器地址(方式二:必须与 username 一起提供)
portNoSSH 端口(可选,默认 22)
usernameNo用户名(方式二:必须与 host 一起提供)
passwordNo密码(password 或 privateKey 至少提供一个。使用 alias 时可覆盖已存储的凭证)
privateKeyNoSSH 私钥内容或私钥文件路径(如 /path/to/id_rsa)。password 或 privateKey 至少提供一个
passphraseNo私钥密码(仅 privateKey 有密码保护时需要)
timeoutNo连接超时时间(毫秒,最小 1000)
Behavior3/5

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

With no annotations, the description bears full burden. It discloses connection methods and credential override but omits side effects, authentication requirements, or connection lifecycle details.

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?

Two sentences, no fluff, front-loaded with purpose. Every sentence contributes meaning.

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

Completeness4/5

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

Covers the two main use cases and parameter relationships well. Lacks details on return values, error handling, or post-connection behavior, but is reasonable for a connection tool.

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%, but the description adds value by explaining mutual exclusivity between alias and host+username, and the at-least-one requirement for password/privateKey, as well as override behavior.

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 verb '建立 SSH 连接' and the resource, and distinguishes two connection methods, making it distinct from sibling tools like disconnect or exec.

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 says '两种方式二选一' and explains when to use alias vs direct connection, including credential override. It provides clear context but does not mention alternatives explicitly.

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