ftp-deploy-mcp

Overview Schema Source Related Servers Discussions Admin

Create a remote directory

ftp_mkdir

Idempotent

Create remote directories recursively on FTP/FTPS/SFTP servers. Specify a path relative to the server root to prepare deployment destinations.

Instructions

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

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Sep 9, 2026

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"
+}

First observedv0.1.0Jul 22, 2026

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.

Deploy Server