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_listA | 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_mkdirA | Recursively create a remote directory (relative to the server root). |
| ftp_renameA | 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 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.
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.
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.
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.