Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Every machine you have, for your agent: free GPUs, jobs, served models, software, over SSH.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"fleet": {
"command": "uvx",
"args": [
"agents-fleet",
"mcp"
]
}
}
}Ejecuta esto en tu terminal
claude mcp add fleet -- uvx agents-fleet mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"fleet": {
"command": "uvx",
"args": [
"agents-fleet",
"mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"fleet": {
"type": "stdio",
"command": "uvx",
"args": [
"agents-fleet",
"mcp"
]
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub sinolion, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.6.2) llegó al registro hace 8 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
**Claude Code, Codex and Gemini see one machine: the one they run on.
fleet shows them all of yours — every GPU and what is running on it, the models being served, the software installed, and where your models and data live.**
No account, no cloud service, nothing installed on the machines you add, no keys handed out: fleet logs in exactly as you do, with the SSH you already use.
https://github.com/user-attachments/assets/d35e0200-c2a2-44aa-8f60-a3b6e4addfb7
Ask your agent to train a model and it starts on your laptop — while a 4090 sits idle across the room and a rented A100 bills you by the hour. It cannot use what it cannot see.
nvidia-smi, compare in your head.Paste this into Claude Code, Codex, Gemini CLI, or any agent that can run commands, on the machine you work from:
Install fleet from https://github.com/sinolion/fleet
Agents: the steps are in INSTALL.md.
That is the whole setup. fleet is installed once on this machine, and every supported agent you have here learns it — not only the one you asked. From here on you say what you want in plain words, with no commands to remember.
Tell the agent how you reach a machine — the SSH command you already use is enough — or let it look in your ~/.ssh/config and on your tailnet for machines you can already reach:
You: add my GPU server,
ssh ubuntu@10.0.0.7
Agent: Added as
gpu-box: 2× RTX 4090, both idle, 46 GB free. It's ready to use.
Each one takes a sentence, whatever the machine is:
| The machine | What you tell the agent |
|---|---|
| a server you can already SSH into | "add ssh ubuntu@10.0.0.7" — fleet logs in as you do, with your key |
| one you reach with a particular key file | "add ssh -i ~/.ssh/my_key ubuntu@1.2.3.4" — or a Host from your ~/.ssh/config |
| a machine on your tailnet | "find my machines" — it lists your ssh config hosts and tailnet machines, and adds the ones you pick |
| a new rental (vast.ai, RunPod, AutoDL) | "add ssh -p 40001 root@1.2.3.4, it costs $1.89/hr" — with the key on your provider account |
| one that only takes a password | "add it" — fleet offers ssh-copy-id, you type the password once into ssh, and your key goes on it |
| one that will not let you in | "why can't you reach the NAS?" — fleet doctor names the one thing to fix |
Nothing is installed on the machines you add: they only need SSH, on Linux, macOS or Windows. fleet probes each one for its GPUs, memory and disks, and keeps that current.
You describe the work; the agent finds where it fits. It checks what each machine has *and* what is free on it right now, so it will not send a job to a busy card:
You: train
train.pyon whatever has a free 24 GB card
Agent:
rtx4090has 23.1 GB free and an idle GPU;a100-spotis free too but costs
$1.89/hr. Starting on
rtx4090, logging totrain.log.
| You say | How the agent finds it |
|---|---|
| "what's free right now?" | every machine checked, the free ones listed |
| "find me a box with a 24 GB card" | matched by what machines have — NVIDIA or AMD, VRAM, cores, RAM — not by name |
| "run the tests on the Linux box" | the machine that runs Linux, results brought back |
| "what's costing me money?" | idle paid rentals flagged, with their hourly price |
| "who is using the GPUs?" | every job on every card — user, VRAM, how long, the command |
| "is Llama 3 already served somewhere?" | every model server's models, and the URL or ssh tunnel to reach it |
| "which box has torch 2.5 and CUDA 12?" | each machine's CUDA or ROCm, Python environments and package versions |
| "download the dataset where datasets go" | the folder that machine says holds datasets, and the room left there |
Keys and passwords never go into the conversation, and anything irreversible waits for your yes.
Only install fleet where you use it. The machines you add need nothing but SSH. Install fleet on another machine only if you also run agents there; it works the same everywhere, with nothing to join or sync. There, fleet ls --discover lists the machines in your ssh config and on your tailnet; the ones you added by hand are in one file you can share with your dotfiles.
Desktop apps and editors get fleet in one click; it runs as an MCP server:
| App | Install |
|---|---|
| Claude Desktop | open fleet.mcpb from the latest release |
| Cursor | |
| VS Code |
Plus plugins for Claude Code, Codex, Copilot CLI and Gemini CLI, and OpenCode, Amp, Windsurf, Cline, Zed, Qwen Code, Goose, Kiro, Hermes — 35+ agents in all: [every agent →](docs/guides/agents.md)
fleet doctor tells you the fix; fleet never makes it.Everything the agent does is a plain fleet command. To install fleet yourself, run this on the machine you work from (this is also what your agent runs when you ask it):
curl -LsSf https://raw.githubusercontent.com/sinolion/fleet/main/install.sh | sh
Windows: powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/sinolion/fleet/main/install.ps1 | iex"
Then drive it yourself:
fleet ls # every machine, with what is free right now
fleet ls --tag cuda --tag vram-24g # by capability: NVIDIA, a card of 24 GB or more fleet ls --tag rocm # every AMD machine fleet top # live view, like htop for the whole fleet fleet show gpu-box # one machine in detail: jobs, software, models, folders fleet ps # every job on every GPU, and which GPUs are idle fleet models # every model being served, and how to reach it fleet edit gpu-box --path models=/data/models # where that machine keeps its models fleet ssh gpu-box -- nvidia-smi # run something there fleet add "ssh ubuntu@10.0.0.7" # add a machine fleet ls --discover # machines in your ssh config and on your tailnet fleet doctor nas # why a machine will not let you in, and the fix
Where a machine keeps its models, datasets and media is written on the machine itself, in machine.yaml (fleet edit NAME --path models=/data/models). Whoever looks at that machine reads the same answer, and the folder sizes and free space come with every probe.
Rentals from vast.ai, RunPod or AutoDL show their price (fleet edit a100 --cost 1.89), the fleet's burn rate, and an alert when a rental sits idle. On Tailscale, ZeroTier or WireGuard? fleet just needs an address it can route to.
fleet is about the machines you already have. It complements tools that launch new ones.
ssh + nvidia-smi | nvitop / gpustat | all-smi / gpuwho | SkyPilot / dstack | fleet | |
|---|---|---|---|---|---|
| All your machines in one view | ✗ | ✗ one machine | ✓ | ✓ the ones it manages | ✓ |
| Built for coding agents (skill / MCP) | ✗ | ✗ | ✗ | partly | ✓ |
| Nothing installed on target machines | ✓ | ✗ | gpuwho ✓, all-smi ✗ | ✗ | ✓ |
| Jobs, served models, software, data folders | ✗ | jobs, one machine | jobs | ✗ | ✓ |
| NVIDIA, AMD and Apple GPUs | NVIDIA | NVIDIA | all-smi ✓ | ✓ | ✓ |
| Launches new cloud VMs | ✗ | ✗ | ✗ | ✓ | ✗ |
| History, alerts sent to you | ✗ | ✗ | all-smi ✓ | partly | ✗ alerts when asked |
When to use something else. To rent GPUs on demand at the lowest price, use SkyPilot or dstack: they launch and stop machines, and fleet does not. For weeks of metrics and paging on a large cluster, use DCGM with Prometheus and Grafana. For a live dashboard of many accelerator kinds (Gaudi, NPUs), use all-smi. fleet is for the machines you already have, and for letting your agent use them.
Why not just Tailscale, Ansible, or an `~/.ssh/config`? Use them with fleet, not instead of it
Solo se muestra el principio; lee el resto en el repo