ftp-deploy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FTP_MCP_CONFIG | No | Path to the server configuration JSON file. If not set, the server looks for ./ftp-servers.json or ~/.ftp-mcp/servers.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ftp_list_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. |
| ftp_testA | Connect to a server, list its root directory, and report success. |
| ftp_listB | List the contents of a remote directory (relative to the server root). Directories are listed first. |
| ftp_readA | Read a remote text file and return its content. Binary files are refused (use ftp_download instead). |
| ftp_uploadA | Upload one local file to the server, auto-creating parent directories. Remote path defaults to the file basename at the root. |
| ftp_deployA | 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. |
| ftp_downloadA | Download a remote file to a local path, auto-creating local parent directories. Refuses to overwrite unless overwrite:true. |
| ftp_mkdirB | Recursively create a remote directory (relative to the server root). |
| ftp_renameB | Rename or move a remote file or directory (both paths relative to the server root). |
| ftp_deleteA | Delete a remote file, or a directory when recursive:true. Never deletes the server root. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes (list/test/read/upload/deploy/download/mkdir/rename/delete). Minor ambiguity exists between ftp_list_servers and ftp_list (listing configured servers vs remote directory contents), and between ftp_upload and ftp_deploy (single file vs recursive directory), but the descriptions clarify the boundaries.
All 10 tools follow a consistent ftp_ prefix with verb-based snake_case names (ftp_list_servers, ftp_test, ftp_list, ftp_read, ftp_upload, ftp_deploy, ftp_download, ftp_mkdir, ftp_rename, ftp_delete). The pattern is predictable and easy to scan.
Exactly 10 tools is well-scoped for an FTP/FTPS/SFTP deployment server. Each tool covers a clear operation (connectivity check, listing, read/write, deploy, directory management) and none feels redundant or missing.
The tool set covers essential FTP deployment operations: listing, testing, reading, uploading, recursive deploying, downloading, creating directories, renaming, and deleting. Minor gaps exist (e.g., no file metadata/stat tool, no remote chmod or in-place edit), but these are not core to deployment workflows.