SSH MCP Server

sftp_upload

Upload a file from a local path to a remote path via SFTP using the provided session ID, enabling secure file transfer during SSH operations.

Instructions

Upload a file to remote system via SFTP

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>",
      "localPath": "<localPath>",
      "remotePath": "<remotePath>"
    },
    "name": "sftp_upload"
  }
}

Input Schema

Name	Required	Description
`localPath`	Yes	Local file path
`sessionId`	Yes	Session ID
`remotePath`	Yes	Remote file path

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Since no annotations are provided, the description carries the full burden of disclosure. It only states the action without mentioning side effects, overwrite behavior, or the need for an active connection, leaving behavioral traits unspecified.

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, succinct sentence that conveys the core action without extraneous detail, achieving high clarity in very few words.

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 with no output schema and no annotations, the description is too sparse to be fully contextual. It omits critical context such as whether the session must already be connected, overwrite semantics, and error conditions, making it inadequate for an agent to correctly invoke the tool in all scenarios.

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?

The input schema already provides descriptions for all three parameters (100% coverage), so the description adds no additional semantic nuance beyond the schema. The parameter descriptions are minimal but sufficient for identifying each field.

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 uses a specific verb ('Upload') and resource ('a file to remote system') with the method (via SFTP), clearly distinguishing it from sibling tools like sftp_download, sftp_list, and sftp_delete.

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. It doesn't mention prerequisites such as an active session or which sibling tools handle other operations like downloading or listing files.

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

Deploy Server