mcp-drone-mcp
Related Servers
Alternatives to mcp-drone-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to plan, confirm, submit, observe, and audit compute jobs across local machines, SSH workstations (including WSL), and Slurm clusters through a unified stdio interface, with node probing, environment evidence, project sync, storage governance, and progress/ETA tracking.311MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to remotely execute shell commands and transfer files on SSH hosts, including jump-host tunneling, background tasks, resumable transfers, and optional approval of destructive commands, while SSH credentials remain in the local process. It runs over stdio or a streamable HTTP daemon and supports auditing, allow/deny lists, and multiple authentication methods.ISC
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to drive a remote Linux machine over the LAN through a single TCP connection, exposing tools for shell commands, jobs, interactive PTYs, file read/write/search/transfer, process and service management, networking, packages, and power control, with optional multi-host switching. Operates without SSH or any Linux-side installation beyond one stdlib-only Python daemon, using a state-free binary protocol.MIT
- AlicenseAqualityCmaintenanceDurable MCP server for managing long-running jobs locally, over SSH, or on Slurm clusters. Jobs survive client disconnects and return exit codes, bounded logs, and JSON artifacts.1117 PyPI1MIT
- AlicenseNot gradedqualityBmaintenanceExposes 20 tools over stdio that let coding agents treat any SSH-reachable machine as a local workspace: reading, writing, editing, searching and listing files, running commands and background jobs, driving persistent terminals, and forwarding ports over one pooled connection, with nothing installed on the remote host.270 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to run shell commands, read, write, edit, search, and stream files on remote SSH servers and Docker containers, including nested multi-layer chains, without installing any runtime on the target hosts. It auto-injects a self-contained Go helper with adaptive zstd compression for fast transfers and process control.9MIT
TDQS
Scored across 13 tools
Most tools target clearly distinct resources or actions (task_status vs task_logs vs task_artifacts, fetch_artifact vs task_artifacts). The one soft overlap is run_jobs, which 'submits and by default dispatches' jobs, versus dispatch_pending and reconcile_running, which also manage task dispatch state, creating some ambiguity about when to use each. Otherwise boundaries are clean.
All names use snake_case consistently. Action tools follow verb_noun (register_drone, cancel_task, dispatch_pending, fetch_artifact) while read tools use noun_noun (task_status, task_logs, task_artifacts, fleet_snapshot), which is a readable convention but not a single uniform pattern.
13 tools sits well within the ideal range and each maps to a real facet of drone orchestration (fleet state, registration, job submission, staging, task inspection, artifact handling, dispatch/reconcile). No obvious filler or redundancy in the count.
The surface covers a full task lifecycle: register, stage, submit, dispatch, monitor, fetch artifacts, cancel, reconcile, and promote persistence. Minor gaps exist, such as no explicit drone deregistration/removal or bulk task listing, but core workflows have no dead ends.