Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Every machine you have, for your agent: free GPUs, jobs, served models, software, over SSH.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"fleet": {
"command": "uvx",
"args": [
"agents-fleet",
"mcp"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add fleet -- uvx agents-fleet mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"fleet": {
"command": "uvx",
"args": [
"agents-fleet",
"mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"fleet": {
"type": "stdio",
"command": "uvx",
"args": [
"agents-fleet",
"mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 sinolion 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.6.2)은 8일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, FOGA node
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
**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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요