de en es ja ko ru zh

ftp-deploy-mcp

Name: ftp-deploy-mcp
Author: alebgl77

by alebgl77

Overview Schema Source Related Servers Discussions Admin

Remote

ftp-deploy-mcp

AIコーディングエージェントのためのデプロイボタン。 Claude Code · Claude Desktop · Cursor · Windsurf · Trae · Antigravity → あなた自身のFTP / FTPS / SFTPサーバーへ。

Version française → README.fr.md

License: MIT Node >=18 MCP compatible PRs welcome

エージェントがデプロイを実行 — あなたは頼むだけ。

なぜ

どのWebプロジェクトも最後は同じ結末を迎えます：「それをサーバーに上げて」。
AIエージェントは優れたコードを書きますが、従来のホスティング（OVH、Ionos、Hostinger、o2switchなど、共有ホスティングの世界は今もFTP/SFTPで動いており、git pushではありません）に安全に配信する手段を持たないものがほとんどです。
ftp-deploy-mcp は、あらゆるMCPクライアントに、コードが書かれたのと同じ会話の中で、あなた自身のインフラへのデプロイ経路を提供します。
汎用のSSH実行MCPサーバーとは異なり、これはファイルデプロイ専用に作られています：パス・ジェイル、読み取り専用モード、ドライラン、そしてモデルのコンテキストに決して入らない認証情報。

Related MCP server: SSH MCP Server

機能

機能	説明
マルチサーバー	FTP / FTPS / SFTP、1つの設定で任意の数のサーバー
ワンコマンドデプロイ	再帰的ディレクトリデプロイ、任意の深さでのgitignore風除外、ドライラン
パス・ジェイル	すべての操作をサーバーごとの`root`配下に制限
読み取り専用モード	変更してはならないサーバーへのすべての書き込みをブロック
FileZillaインポート	既存の`sitemanager.xml`サイトを1コマンドで変換
自動セットアップ	5以上のMCPクライアントを自動設定、タイムスタンプ付き設定バックアップ付き
ドクター	Node、設定、サーバー、クライアント配線の読み取り専用診断
ゼロビルド	プレーンなESM JavaScript — Node標準ライブラリ + 小さな依存関係5つ
デフォルトでセキュア	サーバーごとに明示的に許可しない限り、平文FTP / 未検証TLSは拒否
実戦で検証済み	実際のローカルFTP + SFTPサーバーに対する209件のe2eアサーション
テレメトリなし	あなた自身のサーバーへの呼び出し以外、何もマシンから出て行きません

クイックスタート

git clone https://github.com/alebgl77/ftp-deploy-mcp.git && cd ftp-deploy-mcp
install.cmd（ダブルクリック、Windows）または ./install.sh（macOS / Linux）を実行します。
IDEを再起動して、エージェントにこう頼みます："./dist を prod にデプロイして。"

仕組み

flowchart LR
subgraph agents [AI agents]
  A[Claude Code]; B[Cursor]; C[Windsurf]; D[Trae]; E[Antigravity]
end
agents -- MCP stdio --> S[ftp-deploy-mcp<br/>10 tools · path jail · read-only guard]
S -- FTP / FTPS --> F[(your web hosts)]
S -- SFTP --> G[(your servers)]
K[ftp-servers.json<br/>credentials stay local] -.-> S

1. これは何か

MCP（Model Context Protocol）サーバーであり、stdio上で動作し、コーディングエージェントに10個のツールを公開します。認証情報はローカルの設定ファイルに保存され、LLMのコンテキストを経由することは決してありません。すべてのリモート操作は、サーバーごとに選択したroot配下に制限されます。

Node.js >= 18 が必要です。コンパイルが必要なネイティブ依存関係はありません。

2. インストール

⚡ ワンコマンドインストール（推奨）

git clone https://github.com/alebgl77/ftp-deploy-mcp.git
cd ftp-deploy-mcp

次にウィザードを起動します：

Windows: install.cmd をダブルクリック。
macOS / Linux: ./install.sh（必要に応じて最初に chmod +x install.sh を実行）。
または手動で: npm install && npm run setup。

setupウィザードがすべてを自動で行います：

サーバー設定を作成またはインポートします（既存サイトのFileZillaインポートを含む）；
各サーバーへの接続をテストします；
検出されたMCPクライアント（Claude Code、Claude Desktop、Cursor、Windsurf、Antigravity）の設定ファイルを自動的に書き込みます — 既存ファイルを変更する前に**.backup-<date>**バックアップを作成します；
Trae用の**貼り付け可能なブロックを表示（およびコピー）**します。TraeはUIから設定します。

次にIDEを再起動して、エージェントに例えば「FTPサーバーを一覧表示して」と頼みます。

診断とオプション

いつでも、読み取り専用の診断（何も書き込みません）を実行できます：

npm run doctor          # or: node src/index.js doctor

Nodeのバージョン、使用中の設定ファイル、サーバー一覧（パスワードは決して表示されません）、およびクライアントごとにftpエントリがこのインストールに配線されているかどうかを表示します。

setupオプション（node src/index.js setup [options]）：

オプション	効果
`--yes`	非対話型（既存の設定を保持、または`--from-filezilla`でインポート）。
`--clients <all\|none\|id,id>`	設定するクライアント（デフォルト：検出されたすべて）。
`--from-filezilla [path]`	FileZillaからインポート（パスは省略可 → デフォルトの場所）。
`--config-dest <path>`	設定ファイルの保存先（デフォルト `~/.ftp-mcp/servers.json`）。
`--skip-test`	接続テストをスキップ。
`--dry-run`	予定されたアクションを表示し、何も書き込まない。
`--force`	既存だが異なる`ftp`エントリを置き換える。

(b) グローバルインストール

npm install -g .

ftp-deploy-mcpコマンドがPATHに追加されます。node .../src/index.jsの代わりにこれを使用します。

(c) npmへの公開（`npx -y`での使用向け）

このパッケージを自分の名前でnpmに公開した場合、クライアントは事前インストールなしで実行できます：

{ "command": "npx", "args": ["-y", "your-package-name"] }

3. サーバー設定

ftp-servers.jsonファイルを作成します。サーバーは次の順序で探します（最初に見つかったものが優先）：

--config <path>（コマンドライン引数）
FTP_MCP_CONFIG環境変数（JSONへのパス）
./ftp-servers.json（プロセスの作業ディレクトリ）
~/.ftp-mcp/servers.json

完全なスキーマ

{
  "defaultServer": "prod",          // optional: used when "server" is not given
  "servers": {
    "prod": {
      "protocol": "sftp",           // REQUIRED: "ftp" | "ftps" | "sftp"
      "host": "ssh.example.com",    // REQUIRED
      "port": 22,                    // optional (defaults: ftp/ftps 21, implicit ftps 990, sftp 22)
      "user": "deploy",             // REQUIRED
      "password": "${ENV:PROD_PW}", // optional: password (or an env placeholder)
      "privateKeyPath": "~/.ssh/id_ed25519", // optional (sftp); "~" is expanded
      "passphrase": "…",            // optional: private-key passphrase
      "root": "/var/www/site",      // optional (default "/"): ALL ops are jailed under it
      "readOnly": false,             // optional: blocks upload/deploy/mkdir/rename/delete
      "insecureTLS": false,           // optional (ftps): skip certificate checks — requires "allowInsecure"
      "implicitTLS": false,          // optional (ftps): implicit TLS (port 990, legacy servers)
      "allowInsecure": false         // optional: explicit opt-in REQUIRED for plain "ftp" or "insecureTLS"
    }
  }
}

上記のブロックは説明用に//コメントを使用しています。実際のファイルは厳密なJSON（コメントなし）でなければなりません。ftp-servers.example.jsonを参照してください。

環境変数の置換

任意の文字列値に${ENV:VARIABLE_NAME}を含めることができます。起動時に環境変数の値に置き換えられます。変数が未設定の場合、ツールは欠落している変数を明示した明確なエラーを返します。

"password": "${ENV:OVH_FTP_PASSWORD}"

セキュリティのヒント

SFTPを推奨します。 平文のftpおよびinsecureTLS: trueのftpsはデフォルトで拒否されます：これらのトランスポートでは、ネットワーク攻撃者が認証情報やファイルを傍受または改ざんできます。どうしても使用する場合は、そのサーバーに明示的に"allowInsecure": trueを設定する必要があります — そうすると、起動ログとツール結果のすべてに、目に見えるセキュリティ警告が表示されます。
ftp-servers.jsonを.gitignoreに追加します（このリポジトリではすでに実施済み）。
ファイルのパーミッションを制限します（Unixではchmod 600 ftp-servers.json）。
平文パスワードよりも環境変数（${ENV:…}）またはSSHキーを推奨します。
エージェントが絶対に書き込んではならないサーバーにはreadOnly: trueを使用します。
rootは可能な限り狭く設定します：ジェイルは../による脱出を防ぎます。

4. FileZillaからのインポート

すでにFileZillaにサイトがありますか？変換します：

# Auto-detect the default sitemanager.xml location…
node src/index.js import-filezilla

# …or an explicit file, written to an ftp-servers.json
node src/index.js import-filezilla --file /path/sitemanager.xml --out ./ftp-servers.json

--outを指定しない場合、JSONはstdoutに出力されます。Base64エンコードされたパスワードはデコードされます。保存されたパスワードがないサイトには${ENV:<NAME>_PASSWORD}プレースホルダーが設定されます（変数は自分で設定します）。出力例：

{
  "defaultServer": "my-site",
  "servers": {
    "my-site": {
      "protocol": "ftp",
      "host": "ftp.example.com",
      "user": "deploy",
      "password": "…",
      "root": "/www/html"
    }
  }
}

注意：生成されたファイルにはデコードされた平文パスワードが含まれています — バージョン管理（.gitignore）の対象外にし、パーミッションを制限してください（chmod 600）。

平文FTPサイト：インポートされた"protocol": "ftp"サーバー（上記の例のような）は、sftp/ftpsに切り替えるか、明示的に"allowInsecure": trueを設定するまで、接続時に拒否されます — インポートはそれぞれについて警告を表示します。セキュリティを参照してください。

5. 手動クライアント設定（`setup`を使用しない場合）

npm run setupはこれらのファイルを自動的に書き込みます（バックアップ付き）。このセクションは、すべてを手動で配線したい場合にのみ役立ちます。

/absolute/path/to/ftp-deploy-mcp/src/index.jsを実際のパスに置き換えます（Windowsではフォワードスラッシュ/も機能します）。パッケージをnpmに公開した場合は、"command": "node", "args": ["…/src/index.js"]を"command": "npx", "args": ["-y", "your-package-name"]に置き換えます。

以下のファイルの場所は、執筆時点でのデフォルトの場所です。これらの製品のUIは進化するため、必要に応じて公式ドキュメントを確認してください。

Claude Code

プロジェクトルートの.mcp.json：

{
  "mcpServers": {
    "ftp": {
      "command": "node",
      "args": ["/absolute/path/to/ftp-deploy-mcp/src/index.js"]
    }
  }
}

または1コマンドで：

claude mcp add ftp -- node /absolute/path/to/ftp-deploy-mcp/src/index.js

Claude Desktop

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ftp": {
      "command": "node",
      "args": ["/absolute/path/to/ftp-deploy-mcp/src/index.js"]
    }
  }
}

Cursor

~/.cursor/mcp.json（グローバル）または.cursor/mcp.json（プロジェクト）：

{
  "mcpServers": {
    "ftp": {
      "command": "node",
      "args": ["/absolute/path/to/ftp-deploy-mcp/src/index.js"]
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json：

{
  "mcpServers": {
    "ftp": {
      "command": "node",
      "args": ["/absolute/path/to/ftp-deploy-mcp/src/index.js"]
    }
  }
}

Trae

Traeには安定した設定ファイルがありません — すべてUIで行います。AIチャットパネル → 設定/歯車 → MCP → 追加 → 手動設定、そして貼り付けます（これはsetupが表示してクリップボードにコピーするブロックです）：

{
  "mcpServers": {
    "ftp": {
      "command": "node",
      "args": ["/absolute/path/to/ftp-deploy-mcp/src/index.js"]
    }
  }
}

Antigravity

バージョンによって、ファイルは次のいずれかです：

~/.gemini/antigravity/mcp_config.json
バリアント: ~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "ftp": {
      "command": "node",
      "args": ["/absolute/path/to/ftp-deploy-mcp/src/index.js"]
    }
  }
}

エージェントのMCPパネル（MCPサーバー管理）→ サーバー追加を使用して、同じ構造で設定することもできます。

6. 10個のツール

すべてのリモートパス（path、remote_pathなど）はサーバーのrootからの相対パスであり、POSIXスタイルを使用します。serverパラメータは常に省略可能です（解決方法は以下を参照）。

Tool	Parameters	Description
`ftp_list_servers`	(なし)	設定済みサーバーを一覧表示（プロトコル、ホスト、ポート、ルート、読み取り専用、認証種別）。パスワードは絶対に表示しません。
`ftp_test`	`server?`	接続し、ルートを一覧表示して、成功を確認します。
`ftp_list`	`server?`, `path?`	リモートディレクトリを一覧表示します（ディレクトリを先に表示）。
`ftp_read`	`server?`, `path`, `max_bytes?`	テキストファイルを読み取ります（デフォルト262144、最大1048576バイト）。バイナリファイルは拒否します。
`ftp_upload`	`server?`, `local_path`, `remote_path?`	1つのファイルをアップロードし、親ディレクトリを作成します。
`ftp_deploy`	`server?`, `local_dir`, `remote_dir?`, `include?`, `exclude?`, `dry_run?`	単一の接続でディレクトリを再帰的にデプロイし、デフォルトの除外パターンを適用します。`dry_run` は読み取り専用（`readOnly`）サーバーでも動作します。
`ftp_download`	`server?`, `remote_path`, `local_path`, `overwrite?`	ファイルをダウンロードします。`overwrite: true` でない限り上書きを拒否します。
`ftp_mkdir`	`server?`, `path`	ディレクトリを作成します（再帰的）。
`ftp_rename`	`server?`, `from_path`, `to_path`	名前の変更または移動を行います。
`ftp_delete`	`server?`, `path`, `recursive?`	ファイルを削除します。ディレクトリの場合は `recursive: true` が必要です。ルートは絶対に削除できません。

サーバーの解決方法: 明示的な server パラメータ → defaultServer → サーバーが1つだけの場合はそのサーバー → それ以外の場合は利用可能な名前を一覧表示したエラー。

ftp_deploy のデフォルト除外パターン: **/node_modules/**、**/.git/**、.env、.env.*、 *.log、.DS_Store、Thumbs.db、ftp-servers.json、**/.ftp-mcp/**（指定した exclude グロブは追加されます。include は一致するファイルのみに制限します）。スラッシュを含まないパターンは任意の深さで一致します（gitignore と同様）。ネストされた apps/api/.env も除外されます。

7. プロンプトの例

"./dist を prod サーバーにデプロイして。"
"ovh の /www の中身を一覧表示して。"
"prod から .htaccess を取得して見せて。"
"./build を /www にデプロイするドライランを実行して、何が送信されるか確認したい。"
"prod で index.old.html を index.html に名前変更して。"

8. セキュリティ

デフォルトで安全な転送: 平文の FTP と、証明書検証を無効にした FTPS（insecureTLS: true）は、サーバーエントリが明示的に "allowInsecure": true を設定しない限り拒否されます。許可された場合、起動時、ftp_list_servers、doctor、およびそのサーバーのすべてのツール結果にセキュリティ警告が表示されます。
ルートジェイル: すべての操作は正規化された後、サーバーの root 内に収まるか検証されます。root が / の場合でも、脱出の試み（../…）は拒否されます。
読み取り専用: readOnly: true はすべての書き込み操作（アップロード、デプロイ、mkdir、名前変更、削除）をブロックします。読み取りは引き続き機能します。
LLM に資格情報を渡さない: パスワード、パスフレーズ、キーはツール出力に決して返されません。
テレメトリなし、自分自身のサーバー以外への外部接続なし。
呼び出しごとの接続: 各ツールは接続を開き、操作を実行し、閉じます。永続的なセッションはありません。

9. トラブルシューティング

タイムアウト / 接続できない（FTP）: 通常はファイアウォールによってパッシブモードがブロックされています。サーバーのパッシブポートに到達可能であることを確認してください。
SFTP キー認証: privateKeyPath（~ は展開されます）を設定し、キーが暗号化されている場合は passphrase も設定します。キーのパーミッションを確認してください。
"INSECURE CONNECTION REFUSED": サーバーが平文の FTP、または証明書検証が無効な FTPS を使用しています。sftp（または有効な証明書を使用した ftps）に切り替えるか、— 傍受のリスクを完全に受け入れる場合にのみ — そのサーバーに "allowInsecure": true を設定してください。
自己署名 FTPS: insecureTLS: true は検証されていない証明書を受け入れます。これにより中間者攻撃の保護が無効になるため、"allowInsecure": true も必要となり、呼び出しのたびにセキュリティ警告が表示されます。有効な証明書をインストールすることを推奨します。
インプリシット FTPS（ポート990）: AUTH TLS コマンドなしで最初のバイトから暗号化するレガシーサーバーの場合は、implicitTLS: true（ftps プロトコル）を設定します。
"no server configured": 4つの場所のいずれにもファイルが見つかりませんでした。ftp-servers.json を作成するか、--config <path> / FTP_MCP_CONFIG=<path> を渡してください。
setup 後にクライアントがツールを認識しない: IDE を完全に再起動し（プロジェクトだけでなくすべてのウィンドウを閉じる）、その後 npm run doctor で配線を確認してください。
設定が無効でもサーバーが起動する: これは意図的なものです（MCP クライアントは起動時に停止するサーバーを嫌います）。正確なエラーは起動時に stderr に出力され、すべてのツール呼び出しで返されます。

開発

npm test          # runs the full smoke test (local FTP + SFTP, no external network)
node src/index.js --version
node src/index.js --help

コントリビューション

コントリビューションを歓迎します — 開発環境のセットアップ、プロジェクトの原則、PR チェックリストについては CONTRIBUTING.md を参照してください。

セキュリティ

脆弱性を発見しましたか？公開の issue を開くのはおやめください — 非公開で報告する方法については SECURITY.md を参照してください。

ライセンス

MIT — LICENSE を参照してください。

Available Tools

10 tools

ftp_deleteDelete a remote file or directoryA

DestructiveIdempotent

Delete a remote file, or a directory when recursive:true. Never deletes the server root.

ParametersJSON Schema

Name	Required	Description
`path`	Yes	Remote path to delete, relative to the server root.
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`recursive`	No	Required to delete a directory and its contents.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.2/5.0

Behavior4/5

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

The description adds valuable behavioral detail beyond annotations: recursive deletion applies to directories, and the server root is protected. The annotations already signal destructive/idempotent behavior, so the description's extra guardrail and recursive qualification are strong contributions.

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 short sentences with the core action front-loaded and the safety constraint immediately after. No filler or repeated schema boilerplate.

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?

The description gives the core behavior, the recursive condition, and a critical root-safety guard. It does not address errors, permissions, or edge cases like nonexistent paths, but for a simple destructive operation with strong annotations and schema coverage, it is reasonably complete.

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?

Schema description coverage is high (all parameters documented). The description adds no new parameter semantics beyond restating that recursive deletion applies to directories, so the schema carries the explanatory burden.

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 ('Delete'), identifies the target ('remote file' or 'directory'), and includes the recursive condition for directories. This clearly distinguishes it from sibling operations like ftp_read, ftp_upload, and ftp_list.

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 clearly states when the tool applies (files and directories with recursive=true) and adds a meaningful safety exclusion ('Never deletes the server root'). It does not directly compare with sibling tools, but no sibling covers deletion, so the usage context is sufficient.

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

ftp_deployDeploy a local directoryA

Destructive

Recursively upload a local directory to the server over a single connection, applying default and custom exclude globs (and optional include globs). Supports dry_run.

ParametersJSON Schema

Name	Required	Description
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`dry_run`	No	If true, list what would be uploaded without connecting.
`exclude`	No	Extra glob patterns to exclude, added to the built-in defaults.
`include`	No	Glob patterns; when given, a file must match at least one to be uploaded.
`local_dir`	Yes	Local directory to deploy, absolute or relative to the server's configured localRoot.
`remote_dir`	No	Destination remote directory, relative to the server root. Defaults to the root.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already signal destructiveHint=true and readOnlyHint=false, so the description does not need to prove the operation is a write. It adds useful context about single-connection behavior and dry-run capability, but it does not disclose what the destructive behavior actually affects, such as whether existing remote files are overwritten or whether files absent locally are deleted.

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 tight sentences lead with the action and resource, then pack the glob behavior and dry-run support without wasted words. The description is easy to scan and every clause contributes information.

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?

With a complete input schema, an output schema, and annotations covering the destructive nature, the description is largely sufficient. The only notable gap is the lack of explicit routing guidance against ftp_upload, but this does not prevent a capable agent from invoking the tool correctly.

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?

Schema description coverage is 100%, so the input schema fully documents all six parameters and the description is not required to compensate. The description reinforces exclude/include semantics and dry_run, but adds little meaning beyond what the schema already states.

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 names a specific verb ('upload'), a specific resource ('local directory'), and the key behavioral qualifiers: recursive traversal, glob-based exclusion/inclusion, single connection, and dry-run support. This separates it from the sibling ftp_upload tool, which appears to target individual files, even though that alternative is not named.

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 makes the intended use clear: deploy a whole local directory recursively rather than a single file. However, it never explicitly says when to prefer this over ftp_upload or other siblings, nor does it state exclusions such as 'for individual files, use ftp_upload'. The usage context is implied by the wording, but not spelled out.

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

ftp_downloadDownload a remote fileA

Destructive

Download a remote file to a local path, auto-creating local parent directories. Refuses to overwrite unless overwrite:true.

ParametersJSON Schema

Name	Required	Description
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`overwrite`	No	Allow overwriting an existing local file.
`local_path`	Yes	Local destination path, absolute or relative to the server's configured localRoot.
`remote_path`	Yes	Remote file path, relative to the server root.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.4/5.0

Behavior5/5

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

Discloses two meaningful behaviors beyond the annotations: it auto-creates local parent directories assuredly, and it refuses to overwrite existing files unless overwrite:true is set. This materially helps the agent anticipate side effects beyond the raw destructiveHint.

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 concise, front-loaded sentences cover the primary action and both edge-case behaviors. No redundancy with the title or the input schema.

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?

For a simple download tool with a rich input schema and output schema, this is mostly complete. It could mention what happens on remote-file absence or connection failures, but those are minor gaps given the structured context.

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?

The schema already covers all parameter descriptions (100%), giving a baseline of 3. The description adds relevant semantics by clarifying that local parent directories will be created and that overwrite is disabled by default, which supplements the parameter meaning.

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 specific verb ('download'), the source ('remote file'), the destination ('local path'), and two behavioral constraints (auto-creating parent directories, refusing to overwrite unless asked). This clearly identifies the tool's job and distinguishes it from siblings like ftp_read or ftp_upload.

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 phrase 'download a remote file to a local path' gives clear operational context for when this tool would be used. However, it does not explicitly contrast it with alternatives such as ftp_read (view without saving) or mention any selection criteria, so the guidance is mostly implicit.

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

ftp_listList a remote directoryA

Read-onlyIdempotent

List the contents of a remote directory (relative to the server root). Directories are listed first.

ParametersJSON Schema

Name	Required	Description
`path`	No	Remote directory, relative to the server root. Defaults to the root.
`limit`	No	Maximum entries to return (default 50, maximum 200).
`offset`	No	Zero-based entry offset (default 0).
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds two behavioral facts not in the annotations: directories are listed first, and paths are relative to the server root. This adds value beyond structured metadata without contradicting it.

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, zero filler. The primary action and the most important scoping constraint are front-loaded, and the behavioral note about directory ordering is a single clause. Nothing extraneous.

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?

Given the simple listing tool, annotations covering safety, schema covering all params, and an output schema present, the description is nearly complete. It could mention recursion behavior or sorting, but those are not essential for correct invocation. The provided details are sufficient.

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?

Schema coverage is 100%, so all parameters are described. The description adds context for the 'path' parameter (relative to server root) but does not elaborate on limit/offset or server defaults. Since the schema handles the heavy lifting, this is a baseline 3 with a minor enhancement.

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 states a specific verb ('List') and resource ('remote directory'), and adds a precise scoping detail ('relative to the server root'). This clearly differentiates from siblings like ftp_read (file content) and ftp_list_servers (server configuration) based on the action and target.

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 implies usage—this is the tool for listing directory contents—but does not explicitly mention when to prefer it over ftp_read or other siblings, nor does it state exclusions. The distinction is inferable from the name and title, but no explicit guidance is given.

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

ftp_list_serversList configured serversA

Read-onlyIdempotent

List all configured FTP/FTPS/SFTP servers (name, protocol, host, port, root, read-only, auth kind) and which is default. Never reveals passwords or keys.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already convey readOnlyHint and idempotentHint, but the description adds a meaningful behavioral guarantee: 'Never reveals passwords or keys.' It also specifies the exact set of fields returned (name, protocol, host, port, root, read-only, auth kind, default), which is beyond what annotations provide. No contradiction exists.

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?

A single, well-structured sentence front-loads the action and resource, then lists specifics and a security guarantee. No filler or redundant text. Every clause adds value.

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?

Given the presence of an output schema, the description does not need to elaborate return values. It covers the purpose, lists output fields, and flags a security invariant. For a parameterless configuration-listing tool, nothing critical is absent. The only minor gap is explicit usage guidance, but that is covered under dimension 2.

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?

Since the tool has zero parameters, the description cannot add parameter semantics. Per calibration, baseline for 0 params is 4. The description appropriately confirms no inputs are needed, and the schema is empty, so nothing is missing.

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 'list' and the resource 'configured FTP/FTPS/SFTP servers', enumerates the exact fields returned, and notes the default flag. It is unambiguous and distinguishes itself from sibling ftp_list (which likely lists files) by naming the resource type. The security note about not revealing passwords also clarifies its non-sensitive nature.

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 implies usage (when you need to know configured servers) but provides no explicit guidance on when to choose it over alternatives like ftp_list or ftp_test. It does not state exclusions or prerequisites, relying on the tool name and purpose. A sentence like 'Use this to discover server names before invoking other ftp_* tools' would improve clarity.

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

ftp_mkdirCreate a remote directoryA

Idempotent

Recursively create a remote directory (relative to the server root).

ParametersJSON Schema

Name	Required	Description	Default
`path`	Yes	Remote directory to create, relative to the server root.
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond annotations by stating the operation is recursive and relative to the server root. No contradiction with annotations exists.

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 sentence with no filler, front-loading the core action and the recursive behavior. Every word contributes to the tool's meaning.

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 simple two-parameter tool with full schema descriptions, annotations for safety and idempotence, and an output schema present, the description covers the essential behavioral nuance (recursion) not already in the structured data. Nothing critical appears missing.

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?

Schema description coverage is 100%, with both path and server already described in the input schema. The description's mention of 'relative to the server root' repeats the schema's path description rather than adding new meaning, so the baseline of 3 is appropriate.

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 ('create'), a concrete resource ('remote directory'), and a key qualifier ('recursively') plus scope ('relative to the server root'). It clearly distinguishes this directory-creation tool from file-oriented siblings like ftp_upload and from operations like ftp_list or ftp_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?

There is no explicit guidance about when to use this tool over alternatives such as ftp_upload or ftp_deploy, nor any mention of prerequisites, exclusions, or conditions. The only implied context is that it creates directories, leaving the agent to infer when this is the correct choice.

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

ftp_readRead a remote text fileA

Read-onlyIdempotent

Read a remote text file and return its content. Binary files are refused (use ftp_download instead).

ParametersJSON Schema

Name	Required	Description
`path`	Yes	Remote file path, relative to the server root.
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`max_bytes`	No	Maximum bytes to read (default 262144, hard max 1048576).

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the important behavioral detail that binary files are refused, which is beyond the annotations and helps the agent anticipate failure modes.

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?

A single sentence plus a parenthetical alternative. The core purpose is front-loaded, and every word earns its place—no filler or repetition.

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?

For a simple read tool with no output schema, the description covers core behavior and the binary refusal. It doesn't address error cases (e.g., file not found) but that's minor given the tool's simplicity and strong annotation coverage. Slightly more detail about failure behavior would push it to 5, but it's already solid.

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?

All three parameters (path, server, max_bytes) have descriptions in the schema, so the schema carries heavy weight. The tool description adds no new information about parameter meaning, but the high schema coverage makes this acceptable. Baseline 3 applies.

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 states a specific verb ('read') and resource ('remote text file') and explicitly distinguishes itself from ftp_download by refusing binary files. An agent can immediately tell this is the text-reading tool versus the binary-download sibling.

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

Usage Guidelines5/5

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

Explicitly names the alternative (ftp_download) and the condition that triggers it (binary files are refused). This gives clear direction on when to use this tool versus the sibling, leaving no ambiguity.

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

ftp_renameRename or move a remote entryA

Destructive

Rename or move a remote file or directory (both paths relative to the server root).

ParametersJSON Schema

Name	Required	Description
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`to_path`	Yes	New remote path, relative to the server root.
`from_path`	Yes	Existing remote path, relative to the server root.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate that. The description adds the path-relative-to-root context, but does not disclose what happens on failure, whether directories can be moved recursively, or whether overwriting is possible. With annotations covering the destructive nature, a 3 is appropriate.

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?

A single, efficient sentence that front-loads the action and includes the key scoping detail about paths. No wasted words.

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?

For a two-required-parameter mutation tool with a full output schema and annotations covering destructiveness, the description is nearly complete. It could mention whether moving directories is supported or whether overwrites are allowed, but these are minor gaps given the schema and annotations.

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?

Schema description coverage is 100%, so the schema already documents all three parameters. The description adds the shared context that paths are relative to the server root, which reinforces the schema but doesn't add new meaning beyond it. Baseline 3 is correct.

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 states a specific verb ('Rename or move') and resource ('remote file or directory'), and clarifies that paths are relative to the server root. This clearly distinguishes it from siblings like ftp_delete, ftp_upload, and ftp_download.

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 implies usage for renaming or moving remote entries, but does not explicitly state when to use this tool versus alternatives like ftp_upload or ftp_mkdir. It provides context (both paths relative to server root) but no exclusions or alternative routing.

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

ftp_testTest a server connectionA

Read-onlyIdempotent

Connect to a server, list its root directory, and report success.

ParametersJSON Schema

Name	Required	Description	Default
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the behavioral detail that it lists the root directory and reports success, which is useful context beyond the annotations. However, it doesn't disclose what 'report success' returns or whether it throws on failure, which would be valuable for a test tool.

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 sentence that front-loads the core action and includes the key behavioral detail ('report success'). Every word earns its place, and there is no redundancy or filler.

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?

For a simple test tool with one optional parameter, full annotation coverage, and an output schema, the description is nearly complete. The only gap is that it doesn't specify what the success report looks like, but the output schema likely covers that, so the description is adequate.

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?

Schema description coverage is 100%, so the single parameter 'server' is already documented in the schema. The description doesn't add any additional meaning about the parameter beyond what the schema provides, so the baseline 3 is appropriate.

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 states a specific action ('Connect to a server, list its root directory, and report success') with a clear verb and resource. It distinguishes itself from siblings like ftp_list by focusing on testing connectivity rather than general listing, though it doesn't explicitly name a sibling.

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 implies usage as a connectivity test by mentioning 'report success', but it doesn't explicitly state when to use this tool versus alternatives like ftp_list or ftp_list_servers. The context is clear enough for an agent to infer the primary use case, but no exclusions or alternative routing are provided.

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

ftp_uploadUpload a local fileA

Destructive

Upload one local file to the server, auto-creating parent directories. Remote path defaults to the file basename at the root.

ParametersJSON Schema

Name	Required	Description
`server`	No	Name of the configured server. Defaults to the configured default, or the sole server.
`local_path`	Yes	Local file path, absolute or relative to the server's configured localRoot.
`remote_path`	No	Destination remote path, relative to the server root. Defaults to the local basename at the root.

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, which signal a mutating operation. The description adds the auto-creation of parent directories and the default remote path behavior, which are valuable non-obvious details. It does not disclose potential overwrites of existing files, but the annotation covers the destructive aspect, so the description adds appropriate context.

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 one tight sentence with no filler. The key behavioral details are front-loaded: action, auto-creation, and default path. Every word contributes, and it is neither under-specified nor verbose.

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?

With an output schema present to document return values and annotations covering safety, the description is complete enough. It covers the primary behavior and defaults. It may not cover edge cases like what happens if the file doesn't exist, but given the context, it is adequately comprehensive for an upload 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 description coverage is 100%, so the schema documents each parameter clearly. The description adds the default remote path behavior (basename at root) and clarifies the auto-creation of directories, which complements the schema. This is more than a simple restatement, adding value over 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?

The description clearly states the action: uploading a single local file to the server, with the specific behavior of auto-creating parent directories. It distinguishes itself from siblings like ftp_deploy (which likely uploads multiple files or directories) and ftp_download, and the default remote path behavior is clearly explained.

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 clearly implies use for single-file uploads and implicitly contrasts with ftp_deploy for bulk deployments, but it does not explicitly state when to use this versus alternatives. It provides no explicit exclusions, but the context is enough for an agent to infer the intended use.

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.

10 tool updatesv0.2.0Sep 9, 2026

Changedftp_delete1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "deleted": {
+          "type": "boolean"
+        },
+        "entry_type": {
+          "enum": [
+            "file",
+            "directory"
+          ],
+          "type": "string"
+        },
+        "path": {
+          "type": "string"
+        },
+        "recursive": {
+          "type": "boolean"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "server",
+        "path",
+        "entry_type",
+        "recursive",
+        "deleted",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changedftp_deploy2 fields changed

changedInput schema / properties / local_dir / description

Previous value: -"Local directory to deploy (relative paths resolve against the process cwd)."New value: +"Local directory to deploy, absolute or relative to the server's configured localRoot."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "aborted_early": {
+          "type": "boolean"
+        },
+        "complete": {
+          "type": "boolean"
+        },
+        "duration_ms": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "failed_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "failures": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "message": {
+                "type": "string"
+              },
+              "path": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "path",
+              "message"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "failures_omitted": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "mode": {
+          "enum": [
+            "dry_run",
+            "deploy"
+          ],
+          "type": "string"
+        },
+        "planned": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "path": {
+                "type": "string"
+              },
+              "size_bytes": {
+                "minimum": 0,
+                "type": "number"
+              }
+            },
+            "required": [
+              "path",
+              "size_bytes"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "planned_omitted": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "remote_base": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        },
+        "total_bytes": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "total_files": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "uploaded": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "path": {
+                "type": "string"
+              },
+              "size_bytes": {
+                "minimum": 0,
+                "type": "number"
+              }
+            },
+            "required": [
+              "path",
+              "size_bytes"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "uploaded_bytes": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "uploaded_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "uploaded_omitted": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "mode",
+        "server",
+        "remote_base",
+        "total_files",
+        "total_bytes",
+        "uploaded_count",
+        "uploaded_bytes",
+        "failed_count",
+        "aborted_early",
+        "complete",
+        "duration_ms",
+        "security_warning",
+        "uploaded",
+        "uploaded_omitted",
+        "planned",
+        "planned_omitted",
+        "failures",
+        "failures_omitted"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changedftp_download2 fields changed

changedInput schema / properties / local_path / description

Previous value: -"Local destination path (relative paths resolve against the process cwd)."New value: +"Local destination path, absolute or relative to the server's configured localRoot."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "local_path": {
+          "type": "string"
+        },
+        "overwritten": {
+          "type": "boolean"
+        },
+        "remote_path": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        },
+        "size_bytes": {
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "server",
+        "remote_path",
+        "local_path",
+        "size_bytes",
+        "overwritten",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changedftp_list3 fields changed

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum entries to return (default 50, maximum 200).",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Zero-based entry offset (default 0).",
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "entries": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "modified_at": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "type": "string"
+              },
+              "size_bytes": {
+                "minimum": 0,
+                "type": "number"
+              },
+              "type": {
+                "enum": [
+                  "dir",
+                  "file",
+                  "link"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "name",
+              "type",
+              "size_bytes",
+              "modified_at"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "has_more": {
+          "type": "boolean"
+        },
+        "limit": {
+          "maximum": 200,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "next_offset": {
+          "anyOf": [
+            {
+              "minimum": 0,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "offset": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "path": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        },
+        "total": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "server",
+        "path",
+        "total",
+        "count",
+        "offset",
+        "limit",
+        "has_more",
+        "next_offset",
+        "entries",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changedftp_list_servers2 fields changed

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "configured_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "default_server": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "errors": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "message": {
+                "type": "string"
+              },
+              "server": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "server",
+              "message"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "errors_omitted": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "invalid_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "servers": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "auth": {
+                "enum": [
+                  "key",
+                  "password"
+                ],
+                "type": "string"
+              },
+              "connection_refused": {
+                "type": "boolean"
+              },
+              "host": {
+                "type": "string"
+              },
+              "is_default": {
+                "type": "boolean"
+              },
+              "local_root_status": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "port": {
+                "exclusiveMinimum": 0,
+                "type": "integer"
+              },
+              "protocol": {
+                "enum": [
+                  "ftp",
+                  "ftps",
+                  "sftp"
+                ],
+                "type": "string"
+              },
+              "read_only": {
+                "type": "boolean"
+              },
+              "root": {
+                "type": "string"
+              },
+              "security_warning": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "name",
+              "protocol",
+              "host",
+              "port",
+              "root",
+              "read_only",
+              "auth",
+              "is_default",
+              "local_root_status",
+              "connection_refused",
+              "security_warning"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "servers_omitted": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "status": {
+          "enum": [
+            "configured",
+            "missing",
+            "invalid"
+          ],
+          "type": "string"
+        },
+        "valid_count": {
+          "minimum": 0,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "status",
+        "configured_count",
+        "valid_count",
+        "invalid_count",
+        "default_server",
+        "servers",
+        "servers_omitted",
+        "errors",
+        "errors_omitted"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changedftp_mkdir1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "created": {
+          "type": "boolean"
+        },
+        "path": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "server",
+        "path",
+        "created",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Addedftp_read
Addedftp_rename

Changedftp_test1 field changed

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "entries_visible": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "host": {
+          "type": "string"
+        },
+        "port": {
+          "exclusiveMinimum": 0,
+          "type": "integer"
+        },
+        "protocol": {
+          "enum": [
+            "ftp",
+            "ftps",
+            "sftp"
+          ],
+          "type": "string"
+        },
+        "root": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "server",
+        "protocol",
+        "host",
+        "port",
+        "root",
+        "entries_visible",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changedftp_upload2 fields changed

changedInput schema / properties / local_path / description

Previous value: -"Local file path (relative paths resolve against the process cwd)."New value: +"Local file path, absolute or relative to the server's configured localRoot."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "local_path": {
+          "type": "string"
+        },
+        "remote_path": {
+          "type": "string"
+        },
+        "security_warning": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "server": {
+          "type": "string"
+        },
+        "size_bytes": {
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "server",
+        "local_path",
+        "remote_path",
+        "size_bytes",
+        "security_warning"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "error": {
+          "additionalProperties": false,
+          "properties": {
+            "code": {
+              "enum": [
+                "CONFIG_REQUIRED",
+                "CONFIG_INVALID",
+                "SERVER_REQUIRED",
+                "SERVER_UNKNOWN",
+                "INVALID_ARGUMENT",
+                "READ_ONLY",
+                "TRANSPORT_POLICY",
+                "HOST_KEY_REJECTED",
+                "REMOTE_ROOT_REJECTED",
+                "PATH_REJECTED",
+                "NOT_FOUND",
+                "ALREADY_EXISTS",
+                "TRANSFER_LIMIT",
+                "TRANSFER_VERIFY",
+                "TARGET_CHANGED",
+                "CANCELLED",
+                "TIMEOUT",
+                "DEPLOY_PARTIAL",
+                "TRANSPORT_ERROR",
+                "OUTPUT_LIMIT",
+                "INTERNAL_ERROR",
+                "SCAN_LIMIT",
+                "CAPACITY_LIMIT"
+              ],
+              "type": "string"
+            },
+            "effects": {
+              "enum": [
+                "none",
+                "possible",
+                "confirmed"
+              ],
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "next_action": {
+              "enum": [
+                "fix_input",
+                "fix_config",
+                "select_server",
+                "inspect_target",
+                "retry",
+                "contact_operator",
+                "none"
+              ],
+              "type": "string"
+            },
+            "partial": {
+              "additionalProperties": false,
+              "properties": {
+                "completed_bytes": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "completed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "failed_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "final": {
+                  "type": "boolean"
+                },
+                "total_files": {
+                  "maximum": 9007199254740991,
+                  "minimum": 0,
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "completed_files",
+                "completed_bytes",
+                "failed_files",
+                "final"
+              ],
+              "type": "object"
+            },
+            "request_id": {
+              "format": "uuid",
+              "type": "string"
+            },
+            "retryable": {
+              "type": "boolean"
+            },
+            "schema_version": {
+              "const": 1,
+              "type": "number"
+            }
+          },
+          "required": [
+            "schema_version",
+            "code",
+            "message",
+            "retryable",
+            "request_id",
+            "next_action",
+            "effects"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "error"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

8 tool updatesv0.1.0Jul 22, 2026
- First observedftp_delete
- First observedftp_deploy
- First observedftp_download
- First observedftp_list
- First observedftp_list_servers
- First observedftp_mkdir
- First observedftp_test
- First observedftp_upload

Deploy Server

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.1/5.0

Scored 2026-09-09 21:21 across 10 tools

Disambiguation4/5

Most tools have clear, distinct purposes (list, read, upload, download, mkdir, rename, delete, deploy, list servers, test). The only potential overlap is between ftp_deploy and ftp_upload, but ftp_deploy is for recursive directory uploads while ftp_upload is for a single file, so they are distinguishable with descriptions.

Naming Consistency5/5

All tool names follow a consistent ftp_ prefix with a verb (deploy, list, test, read, upload, download, mkdir, rename, delete). The pattern is uniform and predictable, making it easy for an agent to infer functionality.

Tool Count5/5

With 10 tools, the set is well-scoped for an FTP deployment server. Each tool covers a distinct operation (connection management, file operations, directory operations, deployment), and the count is within the ideal range of 3-15 tools.

Completeness4/5

The core FTP operations are covered: list, read, upload, download, mkdir, rename, delete, and deploy. Missing features like file permissions or detailed metadata (e.g., last modified time) are minor gaps, but the CRUD lifecycle is complete for file and directory operations.

Maintenance

ActivityActive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

microservices.sh
sh.microservices
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloud Platforms Agent Orchestration Developer Tools
21
anotherai
dev.anotherai
MCP server for building and testing AI agents with multi-model experimentation and insights.
Agent Orchestration Autonomous Agents Testing & QA Tools
2
secureflows-mcp A
io.github.michal-lefler
MCP server for secureFlows: token-free URL builders and integration-linting tools for AI agents.
Code Analysis Developer Tools Security
181
ClawLinkOAuth
dev.claw-link
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
App Automation Workplace & Productivity
24

Related MCP Servers

ftp-mcp
File Systems Command Line
Kynlos
A
license
A
quality
D
maintenance
An enterprise-grade MCP server for FTP and SFTP operations optimized for AI coding assistants, featuring smart synchronization, connection pooling, and unified diff patching.
Updated 6 months ago (2026-04-10 23:17 UTC)
28
37 npm
3
MIT
SSH MCP Server
Shell Access Command Line
avranju
A
license
Not graded
quality
D
maintenance
An MCP server that gives AI agents SSH capabilities to execute commands, transfer files, and inspect remote systems through a preconfigured host list.
Updated 7 months ago (2026-03-08 17:03 UTC)
41 npm
MIT
sshcode-mcp
Shell Access Command Line
guanhxuan
A
license
Not graded
quality
D
maintenance
An MCP server that enables AI assistants to perform development operations on remote servers via SSH, including executing commands, managing files, and browsing directories.
Updated 3 months ago (2026-07-21 08:39 UTC)
1
MIT
open-ssh-mcp
Shell Access Command Line
cjp1016
A
license
Not graded
quality
C
maintenance
An MCP server for managing remote SSH servers, enabling AI agents to execute commands, transfer files, and perform deployment operations securely.
Updated 3 months ago (2026-07-24 14:33 UTC)
MIT

ftp-deploy-mcp

なぜ

機能

クイックスタート

仕組み

1. これは何か

2. インストール

⚡ ワンコマンドインストール（推奨）

診断とオプション

(b) グローバルインストール

(c) npmへの公開（npx -yでの使用向け）

3. サーバー設定

完全なスキーマ

環境変数の置換

セキュリティのヒント

4. FileZillaからのインポート

5. 手動クライアント設定（setupを使用しない場合）

Claude Code

Claude Desktop

Cursor

Windsurf

Trae

Antigravity

6. 10個のツール

7. プロンプトの例

8. セキュリティ

9. トラブルシューティング

開発

コントリビューション

セキュリティ

ライセンス

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

(c) npmへの公開（`npx -y`での使用向け）

5. 手動クライアント設定（`setup`を使用しない場合）