What can you do with this server?

This server lets AI coding agents deploy and manage files on their own FTP/FTPS/SFTP servers. * List configured servers (ftp_list_servers) — see name, protocol, host, port, root, read-only state, and auth kind without ever exposing credentials. * Test connectivity (ftp_test) — connect, list the root directory, and confirm the server is reachable. * List remote directories (ftp_list) — browse folder contents, with directories shown first. * Read remote text files (ftp_read) — fetch file contents directly into the conversation (binary files are refused). * Upload files (ftp_upload) — push a local file, auto-creating parent directories. * Deploy whole directories (ftp_deploy) — recursively upload a local folder over a single connection, with gitignore-like include/exclude globs and a read-only dry-run mode. * Download files (ftp_download) — pull remote files locally, protecting against accidental overwrites. * Create directories (ftp_mkdir) — make one or more nested remote folders. * Rename or move entries (ftp_rename) — relocate files or folders on the server. * Delete files or directories (ftp_delete) — remove a file, or recursively remove a directory (never the server root). It enforces security by design: a path jail confines all operations under each server's root, a read-only mode blocks all writes on protected servers, and credentials never enter the model's context or tool output.

Which integrations are available for this server?

Allows AI agents to deploy and manage files on Hostinger FTP/FTPS/SFTP hosting, including uploads, downloads, directory listings, and deletions. Allows AI agents to deploy and manage files on Ionos FTP/FTPS/SFTP hosting, including uploads, downloads, directory listings, and deletions. Allows AI agents to deploy and manage files on OVH FTP/FTPS/SFTP hosting, including uploads, downloads, directory listings, and deletions.

How do I use ftp-deploy-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ftp-deploy-mcp deploy ./build to staging" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

ftp-deploy-mcp

by alebgl77

Overview Schema Related Servers Score Discussions

JavaScript

Remote

ftp-deploy-mcp

The deploy button for AI coding agents. Claude Code · Claude Desktop · Cursor · Windsurf · Trae · Antigravity → your own FTP / FTPS / SFTP servers.

Version française → README.fr.md

License: MIT Node >=18 MCP compatible PRs welcome

Your agent runs the deploy — you just ask.

Why

Every web project ends the same way: "now put it on the server."
AI agents write great code, but most have no safe way to ship it to classic hosting — OVH, Ionos, Hostinger, o2switch and the rest of the shared-hosting world still run on FTP/SFTP, not git push.
ftp-deploy-mcp gives any MCP client a deploy path to your own infrastructure, in the same conversation where the code was written.
Unlike generic SSH-exec MCP servers, this one is purpose-built for file deployment: a path jail, a read-only mode, dry-run, and credentials that never enter the model's context.

Related MCP server: mcp-remote-ssh

Features

Feature	Description
Multi-server	FTP / FTPS / SFTP, any number of servers in one config
One-command deploy	Recursive directory deploy, gitignore-like excludes at any depth, dry-run
Path jail	Every operation confined under a per-server `root`
Read-only mode	Block every write on servers that must stay untouched
FileZilla import	Convert your existing `sitemanager.xml` sites in one command
Auto-setup	Configures 5+ MCP clients automatically, with timestamped config backups
Doctor	Read-only diagnostic of Node, config, servers and client wiring
Zero build	Plain ESM JavaScript — Node stdlib + 5 small dependencies
Secure by default	Plain FTP / unverified TLS refused unless explicitly allowed per server
Battle-tested	209 e2e assertions against real local FTP + SFTP servers
No telemetry	Nothing leaves your machine except calls to your own servers

Quickstart

git clone https://github.com/alebgl77/ftp-deploy-mcp.git && cd ftp-deploy-mcp
Run install.cmd (double-click, Windows) or ./install.sh (macOS / Linux).
Restart your IDE and ask your agent: "Deploy ./dist to prod."

How it works

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. What it is

An MCP (Model Context Protocol) server that runs over stdio and exposes 10 tools to your coding agent. Credentials live in a local config file and never travel through the LLM context. Every remote operation is confined under a root you choose per server.

Requires Node.js >= 18. No native dependency to compile.

2. Installation

⚡ One-command install (recommended)

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

Then launch the wizard:

Windows: double-click install.cmd.
macOS / Linux: ./install.sh (run chmod +x install.sh first if needed).
Or manually: npm install && npm run setup.

The setup wizard does everything for you:

builds or imports your server configuration (including a FileZilla import of your existing sites);
tests the connection to each server;
automatically writes the config files of the detected MCP clients (Claude Code, Claude Desktop, Cursor, Windsurf, Antigravity) — with a .backup-<date> backup before modifying any existing file;
prints (and copies) a paste-ready block for Trae, which is configured from its UI.

Then restart your IDE and ask your agent, e.g. "List my FTP servers".

Diagnostics and options

At any time, a read-only diagnostic (writes nothing):

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

It prints the Node version, which config file is in use, the server list (never passwords), and — per client — whether the ftp entry is wired to this install.

setup options (node src/index.js setup [options]):

Option	Effect
`--yes`	Non-interactive (keeps the existing config, or imports with `--from-filezilla`).
`--clients <all\|none\|id,id>`	Clients to configure (default: all detected).
`--from-filezilla [path]`	Import from FileZilla (path optional → default location).
`--config-dest <path>`	Config file destination (default `~/.ftp-mcp/servers.json`).
`--skip-test`	Skip the connection tests.
`--dry-run`	Print the planned actions and write nothing.
`--force`	Replace an existing but different `ftp` entry.

(b) Global install

npm install -g .

The ftp-deploy-mcp command is now on your PATH; use it instead of node .../src/index.js.

(c) Publish to npm (for `npx -y` usage)

If you publish this package to npm under your own name, clients can run it with no prior install:

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

3. Server configuration

Create an ftp-servers.json file. The server looks for it in this order (first found wins):

--config <path> (command-line flag)
FTP_MCP_CONFIG environment variable (path to the JSON)
./ftp-servers.json (process working directory)
~/.ftp-mcp/servers.json

Full schema

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

The block above uses // comments for teaching only. The real file must be strict JSON (no comments). See ftp-servers.example.json.

Environment-variable substitution

Any string value may contain ${ENV:VARIABLE_NAME}. It is replaced with the environment variable's value at startup. If the variable is unset, tools return a clear error naming the missing variable.

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

Security tips

Prefer SFTP. Plain ftp and ftps with insecureTLS: true are refused by default: on those transports a network attacker can capture or alter credentials and files. To use one anyway you must explicitly set "allowInsecure": true on that server — and every startup log and tool result will then carry a visible security warning.
Add ftp-servers.json to your .gitignore (already done in this repo).
Restrict the file permissions (chmod 600 ftp-servers.json on Unix).
Prefer environment variables (${ENV:…}) or an SSH key over a plaintext password.
Use readOnly: true for servers the agent must never write to.
Set root as narrow as possible: the jail prevents any ../ breakout.

4. Import from FileZilla

Already have your sites in FileZilla? Convert them:

# 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

Without --out, the JSON is printed to stdout. Base64-encoded passwords are decoded; sites without a stored password get a ${ENV:<NAME>_PASSWORD} placeholder (you set the variable yourself). Example output:

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

Heads-up: the generated file contains decoded plaintext passwords — keep it out of version control (.gitignore) and restrict its permissions (chmod 600).

Plain-FTP sites: imported "protocol": "ftp" servers (like the example above) are refused at connection time until you either switch them to sftp/ftps or explicitly set "allowInsecure": true on them — the import prints a warning for each one. See Security.

5. Manual client setup (if you don't use `setup`)

npm run setup writes these files automatically (with backups). This section is only useful if you'd rather wire everything by hand.

Replace /absolute/path/to/ftp-deploy-mcp/src/index.js with the real path (forward slashes / also work on Windows). If you published the package to npm, swap "command": "node", "args": ["…/src/index.js"] for "command": "npx", "args": ["-y", "your-package-name"].

The file locations below are the default locations at the time of writing; these products' UIs evolve, so check their docs if needed.

Claude Code

Project-root .mcp.json:

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

Or in one command:

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 (global) or .cursor/mcp.json (project):

{
  "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 has no stable config file — everything is done in its UI. AI chat panel → Settings/gear → MCP → Add → Configure Manually, then paste (this is the block setup prints and copies to your clipboard):

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

Antigravity

Depending on the version, the file is one of:

~/.gemini/antigravity/mcp_config.json
variant: ~/.gemini/config/mcp_config.json

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

You can also use the agent's MCP panel (MCP server management) → add a server, with the same structure.

6. The 10 tools

All remote paths (path, remote_path, …) are relative to the server root and use POSIX style. The server parameter is always optional (see resolution below).

Tool	Parameters	Description
`ftp_list_servers`	(none)	List configured servers (protocol, host, port, root, read-only, auth kind). Never a password.
`ftp_test`	`server?`	Connect, list the root, confirm success.
`ftp_list`	`server?`, `path?`	List a remote directory (directories first).
`ftp_read`	`server?`, `path`, `max_bytes?`	Read a text file (default 262144, max 1048576 bytes). Refuses binary files.
`ftp_upload`	`server?`, `local_path`, `remote_path?`	Upload one file, creating parent directories.
`ftp_deploy`	`server?`, `local_dir`, `remote_dir?`, `include?`, `exclude?`, `dry_run?`	Recursively deploy a directory over a single connection, with default excludes. `dry_run` works even on a read-only (`readOnly`) server.
`ftp_download`	`server?`, `remote_path`, `local_path`, `overwrite?`	Download a file; refuses to overwrite unless `overwrite: true`.
`ftp_mkdir`	`server?`, `path`	Create a directory (recursive).
`ftp_rename`	`server?`, `from_path`, `to_path`	Rename or move.
`ftp_delete`	`server?`, `path`, `recursive?`	Delete a file; a directory requires `recursive: true`. Never the root.

Server resolution: explicit server parameter → defaultServer → the sole server if there is only one → otherwise an error listing the available names.

ftp_deploy default excludes: **/node_modules/**, **/.git/**, .env, .env.*, *.log, .DS_Store, Thumbs.db, ftp-servers.json, **/.ftp-mcp/** (your exclude globs are added; include restricts to matching files). Slash-less patterns match at any depth (gitignore-like): a nested apps/api/.env is excluded too.

7. Example prompts

"Deploy ./dist to the prod server."
"List what's in /www on ovh."
"Fetch the .htaccess from prod and show it to me."
"Do a dry run of deploying ./build to /www so I can see what would be sent."
"Rename index.old.html to index.html on prod."

8. Security

Secure transports by default: plain FTP and FTPS with certificate verification disabled (insecureTLS: true) are refused unless the server entry explicitly sets "allowInsecure": true. When allowed, a security warning is shown at startup, in ftp_list_servers, in doctor, and appended to every tool result for that server.
Root jail: every operation is normalized then verified to stay under the server root. Any breakout attempt (../…) is refused, even when root is /.
Read-only: readOnly: true blocks every write (upload, deploy, mkdir, rename, delete); reads still work.
Credentials out of the LLM: passwords, passphrases and keys are never returned in tool output.
No telemetry, no outbound connection other than to your own servers.
Per-call connections: each tool opens a connection, performs the op, and closes it — no persistent session.

9. Troubleshooting

Timeout / cannot connect (FTP): usually passive mode blocked by a firewall. Make sure your server's passive ports are reachable.
SFTP key auth: set privateKeyPath (~ is expanded) and, if the key is encrypted, passphrase. Check the key's permissions.
"INSECURE CONNECTION REFUSED": the server uses plain FTP, or FTPS with certificate verification disabled. Switch it to sftp (or ftps with a valid certificate), or — only if you fully accept the interception risk — set "allowInsecure": true on that server.
Self-signed FTPS: insecureTLS: true accepts an unverified certificate. This disables man-in-the-middle protection, so it also requires "allowInsecure": true and prints a security warning on every call. Prefer installing a valid certificate.
Implicit FTPS (port 990): set implicitTLS: true (ftps protocol) for legacy servers that encrypt from the first byte, without an AUTH TLS command.
"no server configured": the file was not found at any of the 4 locations. Create ftp-servers.json or pass --config <path> / FTP_MCP_CONFIG=<path>.
The client doesn't see the tools after setup: fully restart the IDE (close every window, not just the project), then verify the wiring with npm run doctor.
The server starts despite an invalid config: this is intentional (MCP clients dislike servers that die at startup). The exact error is printed on stderr at launch and returned on every tool call.

Development

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

Contributing

Contributions are welcome — see CONTRIBUTING.md for the dev setup, the project's principles, and the PR checklist.

Security

Found a vulnerability? Please do not open a public issue — see SECURITY.md for how to report it privately.

License

MIT — see LICENSE.

Available Tools

8 tools

ftp_deleteDelete a remote file or directoryA

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.

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses the recursive behavior for directories and a safety guarantee about not deleting server root. However, it does not mention error handling, confirmation requirements, or return values, leaving gaps for a destructive operation.

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, front-loaded with the primary function, and a second sentence for an important safety constraint. No extraneous information.

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

Completeness3/5

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

Covers the essential behavior and a key constraint, but lacks details on return values, error conditions, or what happens when path does not exist. For a destructive operation without output schema, more completeness would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good parameter descriptions. The tool description adds value by explicitly linking the 'recursive' parameter to directory deletion and adding the safety constraint about server root, which is not in 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?

Clearly states the action (delete) and the resource (remote file or directory), with a condition for directories (recursive:true). Distinguishes from sibling tools which perform different operations like list, upload, 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?

Provides implicit usage via the description of functionality, but no explicit when-to-use or when-to-avoid compared to siblings. The safety note 'Never deletes the server root' offers a constraint but not usage guidance.

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

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 (relative paths resolve against the process cwd).
`remote_dir`	No	Destination remote directory, relative to the server root. Defaults to the root.

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description reveals some behaviors (recursive upload, single connection, glob application, dry_run) but omits details like default excludes, error handling, permission requirements, and return values. The mention of default excludes is helpful but incomplete.

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 sentences front-load the main action and critical features (recursive upload, connection, globs, dry_run). No wasted words.

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

Completeness3/5

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

The description covers the main functionality for a moderately complex tool (6 params, no output schema), but lacks details on default excludes, error behavior, and return values. It does not fully compensate for missing 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 coverage is 100% with clear parameter descriptions. The description adds context about recursion and glob behavior, but adds little beyond the schema's own descriptions. 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 clearly states the verb 'upload' and the resource 'local directory', and highlights key features: recursive, single connection, exclude/include globs, dry_run. It distinguishes from sibling tools like ftp_upload (single file) 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 bulk deployment via 'recursively upload a local directory' and 'over a single connection', but does not explicitly state when to use versus alternatives. No when-not or exclusion guidance is provided.

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

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 (relative paths resolve against the process cwd).
`remote_path`	Yes	Remote file path, relative to the server root.

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses two important non-obvious behaviors: auto-creating parent directories and refusing overwrite unless overwrite:true. It does not mention error handling or return value, but the core behaviors are well-covered.

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 two concise sentences with no fluff. It is front-loaded with the main action and immediately provides key constraints.

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

Completeness3/5

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

Given no output schema, the description could mention the return value or success status. However, it adequately describes the side effects (auto-create directories, overwrite behavior). It does not cover what happens on error or missing remote file, which would improve completeness.

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 baseline is 3. The description adds context about auto-creating directories and overwrite behavior, but does not add parameter-specific details beyond what the schema already provides.

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 it downloads a remote file to a local path, and adds key behaviors (auto-creating parent directories, overwrite guard). This distinguishes it from siblings like ftp_upload, ftp_list, ftp_delete, etc.

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 (download vs upload), but does not explicitly mention when to use this tool versus alternatives like ftp_deploy or ftp_list. No exclusion or alternative tool names are given.

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 directoryB

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

ParametersJSON Schema

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

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions that 'Directories are listed first', but does not disclose whether the operation is read-only, authentication requirements, error handling, or any side effects.

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 extremely concise, consisting of two short sentences. Every sentence adds value: the first defines the purpose, the second adds a behavioral detail. It is front-loaded and free of unnecessary information.

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

Completeness3/5

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

For a simple list tool with no output schema, the description is minimally adequate. It does not specify the format of returned data (e.g., full paths, file sizes, dates) or behavior for invalid paths, leaving some ambiguity for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides complete descriptions for both parameters (path and server), achieving 100% coverage. The description adds no further meaning beyond what the schema already states, earning a baseline score of 3.

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 identifies the tool's action: 'List the contents of a remote directory'. It specifies that paths are relative to the server root and that directories are listed first, which distinguishes it from sibling tools like ftp_list_servers.

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?

No guidance is provided on when to use ftp_list versus its siblings. The description lacks explicit context about when to choose this tool over ftp_list_servers, ftp_download, or other file operations.

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

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

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that passwords/keys are never revealed and lists output fields, but omits details like speed, authentication requirements, or whether it caches results. For a list tool, this is adequate but not thorough.

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 two sentences with no superfluous words. It front-loads the action and resource, then provides specifics. Every sentence serves a purpose.

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 no output schema and low complexity (zero parameters), the description sufficiently covers what the tool returns (list of server details) and a critical behavioral note (no secrets leaked). It could describe the output format (e.g., array of objects) but the listed fields compensate.

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 tool has zero parameters, so schema coverage is effectively 100%. The description adds value by enumerating the output fields and adding a security guarantee, which based on the guidelines yields a baseline of 4 with no penalty.

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 the specific verb 'List' and identifies the resource as 'all configured FTP/FTPS/SFTP servers'. It explicitly enumerates the fields returned (name, protocol, etc.), distinguishing it from sibling tools that perform file operations.

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?

While no explicit when-to-use or alternatives are stated, the context of sibling tools (all action-oriented) implies this tool is for pre-operation configuration review. A note on when to use (e.g., before downloading) 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 directoryB

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.

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden. It discloses recursion and relativity, but fails to mention authorization needs, side effects, error handling (e.g., if directory exists), or success criteria.

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?

One sentence, front-loaded, and free of verbose or redundant content. Every word earns its place.

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 directory creation tool, the description is fairly complete. It covers recursion and path relativity. Lacks error behavior and return value info, but output schema is absent and tool is straightforward.

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% for both parameters. The description adds no additional meaning beyond the schema; it simply restates the path property. Baseline 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 clearly states the action (create) and resource (remote directory), with additional specificity: 'recursively' and 'relative to the server root'. It distinguishes the tool from siblings like ftp_list, ftp_download, etc.

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?

No guidance on when to use this tool vs alternatives (e.g., ftp_upload, ftp_deploy). The description only states what the tool does, not under what circumstances it should be chosen.

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

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.

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses three actions (connect, list, report success) but does not clarify what 'report success' entails (e.g., return value, success indicator) or whether there are side effects. Moderately transparent but incomplete.

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 that is concise, front-loaded, and contains no superfluous information. Every word adds value.

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 simplicity of the tool (one optional parameter, no output schema), the description is sufficiently complete. It could mention what the tool returns, but the key actions are covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'server' is described in the input schema with default behavior. The tool description adds no further meaning beyond the schema, so it meets the baseline for full schema coverage.

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 it connects to a server, lists root directory, and reports success. It distinguishes itself from sibling tools like ftp_list (which likely lists a specific path) and ftp_list_servers (which lists configured servers).

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 testing connectivity, but does not explicitly state when to use this tool versus alternatives like ftp_list (for listing files) or ftp_list_servers (for viewing server configurations). No when-not-to-use guidance is 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

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 (relative paths resolve against the process cwd).
`remote_path`	No	Destination remote path, relative to the server root. Defaults to the local basename at the root.

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool auto-creates parent directories and sets a default remote path. However, it does not mention overwrite behavior, error handling, or authentication requirements, leaving some gaps.

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 clear sentence, front-loaded with the core action and key behavioral traits. 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?

Given 3 parameters, no output schema, and no annotations, the description covers the main purpose and two behavioral details. Missing information on success/failure response, overwrite policy, and prerequisites, but sufficient for basic understanding.

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%, and the description reinforces the default behavior for remote_path. It adds value with auto-creation context but does not significantly extend beyond schema descriptions.

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 'upload' and the resource 'local file' to the server, with specifics about auto-creating parent directories and default remote path. It effectively distinguishes from sibling tools like ftp_download, ftp_list, etc.

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 implies usage for uploading a single file to the server, with details on auto-creation and default path. It does not explicitly state when not to use it or mention alternatives, but the context is clear enough.

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

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: server listing, download, directory creation, deletion, connectivity test, directory listing, file upload, and directory deployment. No ambiguity between tools.

Naming Consistency5/5

All tools follow a consistent 'ftp_' prefix with snake_case verbs (e.g., ftp_list_servers, ftp_download). Naming is predictable and uniform.

Tool Count5/5

8 tools cover the essential operations for an FTP deployment server without being excessive or insufficient. The count is well-scoped.

Completeness4/5

Core CRUD operations are covered (list, download, upload, delete, mkdir) plus deployment and connection testing. Minor gaps like rename or file info are not critical for the deployment focus.

Maintenance

ActivityMaintained

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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
ClawLink
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 5 months ago (2026-04-10 23:17 UTC)
28
42
2
MIT
mcp-remote-ssh
Command Line Shell Access
faizbawa
A
license
A
quality
A
maintenance
MCP server giving AI agents full SSH access with persistent sessions, structured command output, SFTP file transfer, and port forwarding.
Updated 17 days ago (2026-08-17 06:29 UTC)
18
9
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 6 months ago (2026-03-08 17:03 UTC)
84
MIT
sshcode-mcp
Shell Access Command Line
guanhxuan
A
license
Not graded
quality
C
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 a month ago (2026-07-21 08:39 UTC)
1
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alebgl77/ftp-deploy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

ftp-deploy-mcp

Why

Features

Quickstart

How it works

1. What it is

2. Installation

⚡ One-command install (recommended)

Diagnostics and options

(b) Global install

(c) Publish to npm (for npx -y usage)

3. Server configuration

Full schema

Environment-variable substitution

Security tips

4. Import from FileZilla

5. Manual client setup (if you don't use setup)

Claude Code

Claude Desktop

Cursor

Windsurf

Trae

Antigravity

6. The 10 tools

7. Example prompts

8. Security

9. Troubleshooting

Development

Contributing

Security

License

Available Tools

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

(c) Publish to npm (for `npx -y` usage)

5. Manual client setup (if you don't use `setup`)