cygnus-ssh-mcp

Official

Overview Schema Source Related Servers Discussions Admin

ssh_dir_transfer

Transfer directories between local and remote systems over SSH: upload or download by archiving, sending, and extracting with automatic tar.gz or zip selection.

Instructions

Transfer directories between local and remote systems.

Uses archive-based transfer for efficiency:

Upload: Archives locally, transfers, extracts on remote
Download: Archives on remote, transfers, extracts locally

Archive format is automatically selected based on remote OS:

Linux/macOS: tar.gz
Windows: zip

Where the files end up (check files_location in the result):

upload: the CONTENTS of local_path are placed directly in remote_path (local /x/proj/a.txt -> remote_path/a.txt)
download: the remote folder itself is placed inside local_path (remote /srv/proj/a.txt -> local_path/proj/a.txt)

What it returns (a dictionary): - success: whether the transfer succeeded - operation: 'upload' or 'download' - local_path, remote_path: as given - files_location: the folder where the transferred files now are - archive_format: 'tar.gz' or 'zip' - files_transferred: number of regular files (folders not counted) - directories: number of subfolders (the top folder itself not counted) - payload_bytes: total size of the transferred files - archive_bytes: size of the compressed archive actually sent - bytes_transferred: same as archive_bytes (kept for compatibility)

Long-running calls: if this takes longer than the server's wait cap (default 50s), it
returns {"status": "in_progress", "handle_id": ...} instead of the result - the work keeps
running. Get the result by polling ssh_cmd_check_status(handle_id=...), which returns this
tool's normal response once finished. Do not call it again meanwhile. Only one such
operation runs at a time; another one started meanwhile fails with a 'busy' error.

Input Schema

TableJSON Schema

Name	Required	Description
`use_sudo`	No	Use sudo for remote operations
`direction`	Yes	Transfer direction
`local_path`	Yes	Local directory path
`remote_path`	Yes	Remote directory path

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0May 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: archive-based mechanism, OS-dependent format selection, exact destination layout semantics (contents vs enclosing folder), the full result contract, long-running handle behavior, and the concurrency/busy error. This is unusually rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and uses clean bullets. Some content is redundant: an output schema exists, yet the description enumerates every return field, which consumes space without adding value beyond the schema.

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

Completeness5/5

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

For a complex, mutation-oriented transfer tool with async execution, the description covers the tricky edge cases an agent needs: destination layout, format selection, long-running handle polling, and busy errors. Nothing essential is missing.

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%, so the baseline is 3, but the description adds genuine meaning beyond the schema by explaining the asymmetric destination semantics (upload places contents into remote_path, download places the folder inside local_path). The use_sudo implication is left to the schema.

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?

States a precise verb and resource ('Transfer directories between local and remote systems') and the scope ('directories', not files) implicitly separates it from the ssh_file_transfer sibling. An agent can identify the operation and its two modes (upload/download) without opening the schema.

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

Usage Guidelines3/5

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

The description gives operational guidance for polling (use ssh_cmd_check_status, don't re-invoke meanwhile) and notes a one-at-a-time busy constraint. However, it never explicitly says when to choose this over the closely-related ssh_file_transfer or ssh_dir_copy siblings, so tool-selection guidance is only implied.

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

Deploy Server