Ftp Deploy MCP

Name: Ftp Deploy MCP
Author: alebgl77

by alebgl77version 0.3.2i★ –iRuns on your computer

Registry nameio.github.alebgl77/ftp-deploy-mcp

Install

Overview

Description from the maker (original English)

FTP/FTPS/SFTP deployment · Déploiement FTP/FTPS/SFTP. Local confinement / Confinement local.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: FTP_MCP_CONFIG, FTP_MCP_LANG

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ftp-deploy": {
      "command": "npx",
      "args": [
        "-y",
        "ftp-deploy-mcp"
      ],
      "env": {
        "FTP_MCP_CONFIG": "your-value",
        "FTP_MCP_LANG": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ftp-deploy --env FTP_MCP_CONFIG=your-value --env FTP_MCP_LANG=your-value -- npx -y ftp-deploy-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ftp-deploy": {
      "command": "npx",
      "args": [
        "-y",
        "ftp-deploy-mcp"
      ],
      "env": {
        "FTP_MCP_CONFIG": "your-value",
        "FTP_MCP_LANG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ftp-deploy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ftp-deploy-mcp"
      ],
      "env": {
        "FTP_MCP_CONFIG": "your-value",
        "FTP_MCP_LANG": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

FTP_MCP_CONFIG env
Explicit config path; missing or invalid paths fail closed. / Chemin explicite de configuration ; tout chemin absent ou invalide est refusé.
FTP_MCP_LANG env
Human text language: en (default) or fr. / Langue du texte : en (défaut) ou fr.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account alebgl77, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 1393 servers in this category
Published to the registry more recently than 70% of the other 1393 servers in this category
Basic checks equal to or better than 100% of the other 1393 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ftp Deploy MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 20 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 3 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 15 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ftp-deploy-mcp

The deploy button for AI coding agents.

Give Claude Code, Claude Desktop, Cursor, Windsurf, Trae, Antigravity, or any MCP client a focused way to list, read, upload, download, and deploy files on your own FTP, FTPS, and SFTP servers.

The stdio server implements MCP revision 2026-07-28 through the stable modular TypeScript SDK v2 and retains the SDK's legacy negotiation path for older MCP clients.

*Version française → README.fr.md*

CLI and MCP language: English by default; use --lang fr or FTP_MCP_LANG=fr. Language scope and precedence.

Purpose-built deployment controls keep credentials out of tool responses, support read-only servers and dry runs, and limit local file access with localRoot. The repository is covered by an extensive end-to-end suite that runs against local FTP and SFTP servers. There is no telemetry.

Availability: version 0.3.2 is published on

npm and the

Official MCP Registry.

Use npx -y ftp-deploy-mcp@0.3.2 for that version. The

GitHub release

is a separate source distribution; main can include later changes.

Registry visibility establishes availability, not locked dependency resolution

or qualification of a different commit. See the release guide.

Deployment modes: the ten base tools provide controlled transfers and dry runs. Enabling stateDir adds four durable tools with MCP confirmation, explicit resume and conservative rollback of acknowledged changes. These guarantees belong to the optional durable workflow; legacy ftp_deploy has no transaction or rollback.

Documentation

Document	English	Français
Overview and installation	README	README
Changes	Changelog	Modifications
Contributing	Guide	Guide
Security policy	Policy	Politique
Security model	Model	Modèle
Release process	Guide	Guide
Agent evaluation	Instructions	Instructions
Agent performance and client integration	Guide	Guide
Scripted MCP conformance	Guide	Guide
CLI and MCP languages	Guide	Guide
MCP error contract	Contract	Contrat
Verified staged transfers	Guide	Guide
Scan and admission limits	Limits	Limites
Durable state storage	Library	Bibliothèque
Durable workflow model	Model	Modèle
MIT license	Canonical text	Informative translation

Architecture and scenarios

Explore the current and target architecture diagrams and illustrative scenarios in the bilingual interactive HTML guide. The guide and its English / French build instructions are in the repository, outside the npm package. After cloning, open site/index.html locally and use its language selector.

Animated verified deployment flow

For reduced motion, view the static completed-state image. See the visual system provenance and generation notes.

The visual direction was explored with ChatGPT Image; the final README assets are rendered deterministically. Their provenance and exact prompts document their illustrative role; they are not a certification.

First source install

Install a supported Node.js version: 22, 24 or 26 (minimum: 22).
Run git clone https://github.com/alebgl77/ftp-deploy-mcp.git, then cd ftp-deploy-mcp.
Run npm ci --omit=dev --ignore-scripts.
Run npm run setup, then edit the generated server config: set an absolute localRoot, replace credentials, and configure the SFTP host-key pin or the FTP/FTPS safety acknowledgments described below.
Restart the MCP client and try a dry run:

Call ftp_deploy with:

{"server":"prod","local_dir":"dist","remote_dir":"/","dry_run":true}

Windows users can run install.cmd and macOS/Linux users can run ./install.sh instead of steps 3–4. Review every generated server entry before the first connection.

For a tagged version, check out that exact tag before installing. npm ci uses the sole authoritative package-lock.json, with six exact direct pins and the reviewed graph. Keep it with the sources. --ignore-scripts disables automatic dependency lifecycle scripts; setup is a separate, explicit action.

Once published, the v0.3.2 source installation asset is named ftp-deploy-mcp-0.3.2-source.tar.gz: 90 files, including that lockfile. Verify its publication and checksums before extracting it in a fresh directory:

tar --ignore-zeros -xzf ftp-deploy-mcp-0.3.2-source.tar.gz

cd package npm ci --omit=dev --ignore-scripts node src/index.js setup

This installation archive excludes repository tests and maintainer scripts; GitHub's automatic source ZIP/tar contains the complete repository. The separate npm .tgz contains 89 files without a lockfile and follows npm dependency resolution. It provides no locked-install guarantee. See the release guide for verification and limits.

Protocol and security matrix

Protocol	Transport identity	Remote-root behavior	Recommended use
SFTP	Encrypted. `hostKeySha256` is required unless `allowUnknownHostKey: true` explicitly accepts impersonation risk.	`realpath`/`lstat` checks refuse symlink components and keep operations below `root`. A malicious or changing server can still create a race between validation and use.	Preferred. Pin a fingerprint verified out of band.
FTPS	Encrypted when certificate verification succeeds. `insecureTLS: true` also requires `allowInsecure: true` and disables MITM protection.	A client-side sub-root cannot be a reliable anti-symlink jail. `root` other than `/` is refused unless `allowUnsafeRemoteRoot: true`.	Use a dedicated, server-side chrooted account whose visible root is `/`.
FTP	Plaintext. Refused unless `allowInsecure: true` accepts interception and credential exposure.	Same limitation as FTPS: the real boundary is the server account/chroot, not lexical client path checks.	Legacy-only, on a trusted network, with a dedicated chrooted account.

All three protocols also enforce localRoot for ftp_upload, ftp_deploy, and ftp_download. This limits which local files the MCP server can access.

What you get

Ten focused MCP tools for server discovery, testing, listing, reading, uploading, recursive deploys, downloading, creating directories, renaming, and deleting.
Four additional durable-workflow tools when stateDir is configured; confirmation and rollback follow the documented bounds.
Multiple named servers in one local configuration.
Gitignore-like deploy exclusions, dry-run, and per-server readOnly mode.
FileZilla import, an interactive setup wizard, and a read-only doctor command.
Credentials loaded locally from the config, environment variables, or SSH keys and never intentionally returned to the model.

Server configuration

An explicit configuration path is authoritative:

--config
FTP_MCP_CONFIG, when --config is absent

An empty, missing, unreadable, or invalid explicit configuration reports an error without falling back to another file. The MCP tools remain available to report the configuration problem. --config requires a path argument.

Without either selector, the first configuration found wins:

./ftp-servers.json
~/.ftp-mcp/servers.json

The teaching example below is JSON with comments. Real configuration files must be strict JSON; start from ftp-servers.example.json.

"defaultServer": "prod", "stateDir": "/home/alice/.local/state/ftp-deploy-mcp", "requirePlan": true, "servers": { "prod": { "protocol": "sftp", "host": "ssh.example.com", "port": 22, "user": "deploy", "password": "${ENV:PROD_PASSWORD}", "privateKeyPath": "~/.ssh/id_ed25519", "passphrase": "${ENV:PROD_KEY_PASSPHRASE}", "localRoot": "/home/alice/projects/site", "root": "/var/www/site", "hostKeySha256": "SHA256:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA", "readOnly": false } } }

Replace the all-A fingerprint; it is deliberately non-functional for a real host. Use hostKeySha256 as an array during a controlled key rotation:

"hostKeySha256": [

"SHA256:old_verified_43_character_base64_value_here", "SHA256:new_verified_43_character_base64_value_here" ]

The illustrative labels above show the shape but are not valid pins. Each real entry is exactly SHA256: plus 43 characters of unpadded base64.

Field reference

Field	Applies to	Meaning
`stateDir`	top level	Optional absolute, normalized durable-state directory, canonically disjoint from every `localRoot`. Enabling it advertises the four durable workflow tools.
`requirePlan`	top level	With `stateDir`, defaults to `true`. Blocks legacy remote mutators except `ftp_deploy` dry runs; `false` retains them under the same persistent alias lock.

| stateLimits | top level | Optional strict durable quotas for state, backups, plans, opera

Only the beginning is shown; read the rest in the repo

Ftp Deploy MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

ftp-deploy-mcp

Documentation

Architecture and scenarios

Animated verified deployment flow

First source install

Protocol and security matrix

What you get

Server configuration

Field reference