Skip to main content
Glama
mfangtao

SSH MCP Server

by mfangtao
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

SSH MCP Server

Node.js Version TypeScript

一个基于SSH2和Model Context Protocol (MCP)的SSH服务器，提供远程命令执行功能。

功能特性

  • 通过MCP协议提供SSH远程命令执行工具

  • 支持密码和私钥认证

  • 返回命令执行结果(stdout/stderr/exit code)

  • 基于TypeScript开发，类型安全

Related MCP server: SSH MCP Server

安装

Installing via Smithery

To install SSH Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @mfangtao/mcp-ssh-server --client claude

Manual Installation

# 克隆仓库
git clone https://github.com/your-repo/ssh-server.git
cd ssh-server

# 安装依赖
npm install

# 构建项目
npm run build

使用方法

  1. 启动服务器：

npm start

  1. 通过MCP客户端调用execute_ssh_command工具：

请求示例：

{
  "connection": {
    "host": "example.com",
    "port": 22,
    "username": "user",
    "password": "password"  // 或使用 privateKey
  },
  "command": "ls -la"
}

开发

# 开发模式
npm run build -- --watch

# 运行测试
# (需要添加测试脚本)

依赖

许可证

MIT

Available Tools

1 tool
execute_ssh_commandC

Execute command on remote server via SSH

ParametersJSON Schema
NameRequiredDescriptionDefault
commandYes
connectionYes

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'execute command' implies a potentially risky operation, it doesn't mention security implications, permission requirements, error handling, or output characteristics. This leaves significant gaps for a tool that interacts with remote systems.

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 a single, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the essential information about what the tool does.

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?

For a tool that executes commands on remote servers (a complex, potentially dangerous operation) with no annotations, no output schema, and 0% schema description coverage, the description is severely incomplete. It lacks crucial information about security, permissions, error handling, and what the tool returns.

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

Parameters2/5

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

The schema has 0% description coverage, so the description must compensate but fails to do so. It mentions neither of the two parameters ('command' and 'connection') nor their nested properties, leaving all parameter meaning undocumented.

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 action ('execute command') and target ('on remote server via SSH'), providing a specific verb+resource combination. However, without sibling tools, it cannot demonstrate differentiation from alternatives, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without any usage context.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedexecute_ssh_command
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct as it is the sole operation available.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (execute_ssh_command), and with only one tool, consistency is inherently perfect as there are no other names to compare against.

Tool Count2/5

One tool is too few for a server named 'SSH MCP Server', which implies broader SSH functionality. A single command execution tool feels thin and incomplete for managing SSH connections, lacking operations like file transfer, session management, or configuration.

Completeness2/5

The tool surface is severely incomplete for SSH operations. It only covers command execution, missing essential functions such as scp for file transfer, key management, or connection setup, which are core to SSH workflows and expected from the server's name.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • MCP SSH Server

    shaike1
    F
    license
    Not graded
    quality
    F
    maintenance
    A secure SSH server implementation for Model Context Protocol that enables remote command execution and file operations, supporting both password and key-based authentication.
    57
    -

  • SSH MCP Server

    KinoThe-Kafkaesque
    A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol server implementation that enables secure remote command execution via SSH, with features for managing and using SSH credentials.
    5
    1
    10
    MIT

  • MCP SSH Tools Server

    nwnusun-cool
    F
    license
    A
    quality
    F
    maintenance
    A server based on the MCP framework that provides remote server management capabilities through SSH, supporting features like connection pooling, file transfers, and remote command execution.
    7
    -

Appeared in Searches

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

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