
Mcp Sftp Orchestrator
io.github.fkom13Published by GitHub account fkom13v8.0.4Updated Oct 24, 2026
Serveur MCP pour l'orchestration de tâches distantes (SSH/SFTP) avec une file d'attente persistante.
Overview
A local stdio MCP server that lets an assistant orchestrate a fleet of remote servers over SSH/SFTP, with a persistent job queue, file editing, diffs, snapshots
- What you can do
- Run commands over SSH on one alias, several aliases, a group or all servers, with a persistent queue, retries and logs; open interactive and sequenced command sessions and remote tmux sessions and SSH tunnels. Read, write and hash-safe edit local and remote files, transfer files over SFTP including server-to-server, and diff files, folders and project sources. Manage the fleet: server aliases and groups, SSH public-key authorization, command blocklists, API catalogue, server notes, projects and work sessions. Audit and monitor: infrastructure overview and audit, fleet status, inventory, CPU/RAM/disk, systemd/Docker/PM2 services, Fail2Ban, API health checks and logs. Create, list, diff, and,
- When to use it
- Useful when an assistant has to operate several remote Linux servers from one place: deploying or fixing files, running commands across a fleet, comparing local and remote project trees, or keeping notes and snapshots of interventions. It fits operators who already manage servers over SSH and want the agent to work inside that same access model.
- Requirements
- Runs locally as a Node.js process (Node.js 18 or later) over stdio, started by the MCP client with the server script path. SSH access to the target hosts is needed, configured through server aliases holding a key path or password. Optional environment variables set the data directory, timeouts, connection pool, allowed local roots, read-only mode and debug logging.
Installation
In SourceWeft
- Open Mcp Sftp Orchestrator in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🚀 MCP Orchestrator — Serveur d'orchestration SSH/SFTP
v11.8.0 Security Refresh — Les 82 tools publient désormais les annotations MCP standard.
infra_overviewreste léger sans argument, maisinfra_overview { alias: "..." }effectue une découverte live et corrèle Nginx/domaines, ports, Docker/Compose et services. VoirCHANGELOG.md.
Version : 11.8.0
Tools : 82
License : MIT
Node : >= 18.0.0
Changelog : CHANGELOG.md
Serveur MCP (Model Context Protocol, transport stdio) qui donne à un agent IA la capacité d’orchestrer un parc de serveurs : SSH, SFTP, édition de fichiers locale/remote (hash-safe), diffs cross-server, shell PTY, snapshots d’infra, notes de protocole, projets, sessions de travail, inventaire, trust SSH (pubkey), groupes d’alias et audit parc.
✨ Points forts (v11.6)
📦 Installation
Prérequis : Node.js >= 18
⚙️ Configuration (.env)
Toutes les variables sont optionnelles.
Fichiers sous MCP_DATA_DIR
🔌 Connexion client MCP
Grok / config.toml
OpenCode / Claude Desktop (JSON)
Après modification du code : recharger le serveur MCP (/mcps → r ou restart session). Vérifier system_diagnostics → version: "11.8.0".
🧰 Référence des outils (82)
Diagnostic & audit
Serveurs & groupes
Projets (v11.6)
Exemple project_set :
Sessions de travail (v11.6)
Trust SSH (v11.6)
Policies
Catalogue API
Exécution de tâches
Files / Diff / Shell / Snapshots
Édition safe : file_read → hash → file_edit + expectedHash (+ dryRun / backup).
Notes serveur
Monitoring & logs
Queue
Tmux & tunnels
📖 Workflows agent recommandés
Début de session
Chantier sur un projet
Commandes longues
Cibles multi-serveurs
🏗️ Architecture
Cycle de vie d’un job
🔒 Sécurité
🧪 Tests
🛣️ Versions récentes
Détail : CHANGELOG.md · plans historiques : ROADMAP.md, ROADMAP_EXTENDED.md.
📄 Licence
MIT — Copyright (c) 2025-2026 Franck (fkom13)
Source: README.md at commit 91725bf
Tools
0Version history
1- v8.0.4LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.