AIクライアントにあなたのサーバーを安全に操作させる —— SSHベースのMCPサーバー
標準化されたMCPツールを通じてリモートでコマンド実行とファイル転送を行います。Web管理コンソールとWindowsトレイアプリを内蔵。
Claude Code、CursorなどMCPプロトコルに対応したAIクライアントをあなたのSSHサーバーに接続すれば、AIは次のことができます：
⚙️ コマンド実行 —— リモート運用・保守、ログ調査、サービス管理
📤 アップロード / 📥 ダウンロード —— 設定配布、ログ取得、大容量ファイルのレジューム転送
🖥️ 複数マシン管理 —— プロジェクト → 環境 → ホストの3階層ツリー。一度設定すればどこでも利用可能
2つの利用形態から選択できます：
形態 | 適したシーン |
CLI / npm パッケージ | stdio MCP Serverとして任意のMCPクライアントに接続。軽量ですぐ使える |
Windows デスクトップアプリ（推奨） | 純粋なトレイ常駐 + 内蔵Web管理コンソール + オンライン自動更新。Node.js環境不要 |
Related MCP server: sshops
🔐 多様な認証：パスワード / 秘密鍵（暗号化秘密鍵含む）/ SSH Agent / キーボードインタラクティブ 2FA
🔗 SOCKS5とHTTP(S)プロキシ。踏み台ネットワークを透過
🚄 デュアル転送モード：
exec —— コマンドごとに1チャネル。標準Linuxホスト
shell —— 永続セッション + マーカープロトコル。バスティオンホスト / 踏み台サーバーに適合
⏱️ 接続 / コマンド / SFTPの各タイムアウトを個別に制御可能。大容量ファイルはfastPut/fastGetによる分割・並行転送
コマンドのホワイトリスト / ブラックリスト（正規表現）。ホストレベルとグローバルレベルの二重フィルタリング
ローカルとリモートのパスホワイトリストでファイル転送範囲を制限
完全な監査ログ：コマンド、出力、転送記録を追跡可能
プロジェクト-環境-ホストの3階層ビジュアル管理。接続のドラッグ＆ドロップ並べ替え
接続テスト、JSON一括インポート/エクスポート、~/.ssh/configの自動再利用
定期バックアップスナップショットとワンクリック復元。MCPクライアント（Claude Codeなど）のワンクリック登録
ライト/ダークのデュアルテーマ。システム設定に追従して切り替え
🎯 純粋なトレイ常駐の単一exe：SSHサービス、MCP Server、Admin静的サイトをすべて内蔵。Node.js依存なし
起動時自動起動、シャットダウン時まで常駐。「管理ページを開く」でシステム標準ブラウザを直接起動
🔄 オンライン自動更新：minisignによる署名検証を内蔵。新バージョンを自動検出してサイレントアップグレード
接続管理 —— 3階層ツリーで全ホストを管理：
システムページ —— サービス状態とMCPクライアントのワンクリック登録：
ReleasesからSSH-MCP-Server_x.x.x_x64-setup.exeをダウンロードしてインストールします。起動後はシステムトレイに常駐し、トレイメニューの「管理ページを開く」でWebコンソールに入ります。
インストール済みユーザーは、その後のアップグレードが自動的に完了し、手動操作は不要です。
# 全局安装
npm install -g @sieop/ssh-mcp-serverMCPクライアントに登録します（Claude Codeを例に）：
claude mcp add ssh-server -- ssh-mcp-server --host your.server.com --username root --password YOUR_PWDまたはJSON設定を直接記述：
{
"mcpServers": {
"ssh-server": {
"command": "npx",
"args": ["-y", "@sieop/ssh-mcp-server", "--host", "your.server.com", "--username", "root", "--password", "YOUR_PWD"]
}
}
}設定ファイルとマルチ接続モードにも対応しています。詳細はdocs/migration.mdとCLIヘルプ（--help）を参照してください。
git clone https://github.com/SIE-Operations-and-Maintenance-Team/ssh-mcp-server.git
cd ssh-mcp-server && npm install
npm run build # 构建 Node 版
npm test # 运行测试
npm --prefix admin-web install && npm --prefix admin-web run build # 构建管理台前端
npm run tauri:build # 构建 Windows 桌面应用（需 Rust 工具链）ツール | 説明 |
| リモートでコマンドを実行。ディレクトリ変更、タイムアウト、出力制限に対応。ホワイト/ブラックリストの制約を受ける |
| SFTPファイル転送。大容量ファイルは分割・並行転送。パスホワイトリストを検証 |
| 利用可能なすべての接続を一覧表示 |
┌─ Windows 桌面应用（Tauri 2 纯托盘单 exe）──────────────────┐
│ │
│ SSH 连接池 ── MCP StreamableHTTP (/mcp) │
│ │ │
│ Admin API (/admin/api/*) ── 内嵌静态站点 (/admin/) │
│ │
└────────────────── 系统默认浏览器打开管理页 ────────────────┘
Node 版（npm 包）：stdio MCP Server ＋ 可选 --admin 启动同一套 Web 管理台主要モジュール：src/services/ssh-connection-manager.ts（SSHコア）、src/server/（Fastify Adminサービス）、src-tauri/（Rustデスクトップシェル）、admin-web/（React管理コンソール）。
ISC © SIE Operations and Maintenance Team
本プロジェクトはclassfang/ssh-mcp-serverをベースに、再構築と拡張を行ったものです。
Download file from connected server
| Name | Required | Description | Default |
|---|---|---|---|
| localPath | Yes | Local path | |
| remotePath | Yes | Remote path | |
| connectionName | No | SSH connection name (optional, default is 'default') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only states that a file is downloaded from a connected server; it does not mention that localPath will be written, files may be overwritten, or that a valid connectionName is needed. This is a significant gap for a tool with side effects on the local filesystem.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler words. However, it may be underspecified for a tool that writes to the local filesystem, so it is not maximally effective.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 3-parameter tool with no output schema and no annotations, the description is incomplete. It omits behavioral details such as overwrite behavior and default connection semantics (though connectionName is documented in the schema). An agent would need to infer several operational aspects beyond what is given.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already contains descriptions for all three parameters (localPath, remotePath, connectionName), and schema coverage is 100%. The description adds no additional parameter-level meaning, so the baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the precise operation ('Download file') and the source ('from connected server'), clearly identifying it as a remote-to-local transfer. It is distinct from siblings like upload, execute-command, and list-directory, though it does not explicitly distinguish itself by name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives such as upload or list-directory. The description merely restates the operation and leaves the agent to infer selection criteria from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Execute command on connected server and get output result
| Name | Required | Description | Default |
|---|---|---|---|
| timeout | No | Command execution timeout in milliseconds (optional; overrides the connection's commandTimeoutMs or shellCommandTimeoutMs, which defaults to 30000ms) | |
| cmdString | Yes | Command to execute | |
| directory | No | Working directory for command execution | |
| connectionName | No | SSH connection name (optional, default is 'default') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of behavioral disclosure. It only says commands are executed and output is returned; it fails to mention that this can run arbitrary, potentially destructive commands on the server, how timeouts or working directories affect execution, or what the output result contains (e.g., stdout, stderr, exit code).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence that front-loads the core action and outcome with no redundant words. It is concise and well-structured, though it could have included more behavioral context without becoming bloated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a powerful command-execution tool with four parameters and no output schema, the description is incomplete. It does not explain return values, failure modes, side effects, or how parameters like directory and connectionName influence execution. Given the potential for destructive commands, more context is necessary for safe and correct use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides 100% description coverage for all four parameters, including default behavior for timeout and connectionName. The description text adds no additional parameter meaning, but the schema already documents each field adequately, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: "Execute command on connected server and get output result." This clearly conveys the tool's action and outcome, and it is immediately distinguishable from the sibling tools (upload, download, list-servers, list-directory), which all perform different operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for running shell commands on a server versus the file transfer and listing operations of sibling tools, but it provides no explicit when-to-use guidance, prerequisites, or exclusions. Usage context is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List entries of a remote directory (name, type, size, mtime) via SFTP
| Name | Required | Description | Default |
|---|---|---|---|
| remotePath | Yes | Absolute POSIX directory path on the remote server, e.g. /var/log | |
| connectionName | No | SSH connection name (optional, default is 'default') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It does communicate that this is a list/read operation and what fields appear in the result, which is helpful. It doesn't mention behaviors like connection requirements, symlink handling, error conditions, or non-existent paths, but the core read-only nature is reasonably clear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, tight sentence that front-loads the action and resource, then adds the useful output-field detail. There is no wasted text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool, the description plus fully documented schema covers the essential context: what is listed, what fields are returned, and how the path/connection parameters behave. It lacks explicit return format details and error behavior, but those are minor given the simplicity and lack of an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already describes both parameters fully, including path format and the optional default for connectionName. The description adds no new parameter-level semantics, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb ('List'), a specific resource ('entries of a remote directory'), and the key returned attributes (name, type, size, mtime). It clearly distinguishes this tool from siblings like execute-command, upload, download, and list-servers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The intended use is implied by the description: when you need a directory listing over SFTP. However, there is no explicit guidance about when to prefer this over alternatives, no exclusions, and no mention of prerequisites such as needing a configured SSH connection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List all available SSH server configurations
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not clarify what 'available' means, whether the tool connects to servers, or what kind of configuration data is returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler or repetition. It communicates exactly what the tool does in the fewest words necessary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, zero-parameter listing tool, this description is mostly complete. It clearly identifies the action and resource, though adding the output format or clarifying what 'configurations' includes would make it fully self-sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema already covers everything relevant. With no parameters to explain, the baseline of 4 applies, and the description does not need to add parameter-level detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('list') and resource ('SSH server configurations'), making the tool's purpose immediately clear. It is also naturally distinct from sibling tools like execute-command, upload, download, and list-directory.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives. It does not mention workflows such as 'use this before connecting to a server' or exclude cases where list-directory might be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Upload file to connected server
| Name | Required | Description | Default |
|---|---|---|---|
| localPath | Yes | Local path | |
| remotePath | Yes | Remote path | |
| connectionName | No | SSH connection name (optional, default is 'default') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are completely absent, so the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention whether an existing remote file is overwritten, whether directories are created, what permissions are required, or any side effects. This is a significant gap for a mutation-like upload operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is concise and front-loaded with the core action ('Upload file'), containing no filler. It effectively states the purpose in minimal words, though it could be slightly expanded with useful context without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description is too sparse. It does not explain what happens on success or failure, whether the remote path refers to a file or directory, or how the 'connected server' is determined. The schema covers parameter names but the overall operational context is incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides descriptions for all three parameters, with 100% coverage, so the baseline applies. The description adds no additional parameter meaning, but because the schema fully covers 'localPath', 'remotePath', and 'connectionName', a score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Upload file') and the target ('connected server'), which distinguishes it from siblings like 'download' or 'execute-command'. However, it does not explicitly differentiate from these siblings by naming them or elaborating on the remote context, so it misses the top score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives like 'download' or 'execute-command'. It does not mention prerequisites, such as needing an existing server connection, nor when not to use this tool. Usage is only vaguely implied by the verb 'Upload'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.1.3downloadexecute-commandlist-directorylist-serversuploadScored across 5 tools
Each tool targets a distinct operation: remote command execution, file upload, file download, server configuration listing, and directory listing. There is no meaningful overlap or ambiguity between them.
Naming mostly follows a clear verb-object pattern with lowercase hyphenation, like execute-command, list-servers, and list-directory. The standalone upload and download verbs deviate slightly from the hyphenated style but remain intuitive and consistent in intent.
Five tools is well-scoped for an SSH MCP server, covering the essential interactions without unnecessary bloat. Each tool earns its place and the set feels focused.
The set covers command execution, file transfer, directory browsing, and server enumeration, which are core SSH workflows. Minor gaps like missing explicit remote delete, rename, or mkdir tools are workable because command execution can handle those operations.
Egnyte's remote MCP server for secure AI access, search, upload and file management in your account.
Secure and manage MCP servers through the Speakeasy AI Control Plane from your agent.
Termalin's hosted MCP server. Claude, ChatGPT or any MCP client runs commands, moves files over SFTP, queries databases and reads server metrics and monitoring alerts on your servers, keylessly through Termalin Connectors: no SSH key is handed over and no inbound port is opened. Per-host command policy and an audit log. Needs a termal.in Pro or Team account (new accounts start with a 14-day Pro trial).
Compliance frameworks (SOC 2, ISO 27001, CMMC, NIST, more) delivered to AI agents as MCP tools.
