Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Rent a per-minute GPU from your MCP client, run a job, download results, shut it down.
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.
CLOUDGPU_API_KEYLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
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": {
"cloudgpu": {
"command": "npx",
"args": [
"-y",
"cloudgpu-mcp"
],
"env": {
"CLOUDGPU_API_KEY": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add cloudgpu --env CLOUDGPU_API_KEY=your-value -- npx -y cloudgpu-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"cloudgpu": {
"command": "npx",
"args": [
"-y",
"cloudgpu-mcp"
],
"env": {
"CLOUDGPU_API_KEY": "your-value"
}
}
}
}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": {
"cloudgpu": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cloudgpu-mcp"
],
"env": {
"CLOUDGPU_API_KEY": "your-value"
}
}
}
}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 mrhy7176, 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.
Debes completar: CLOUDGPU_API_KEY
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.3.0) llegó al registro hace 3 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, HotCodePush
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.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
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.
CloudGPU MCP server: let an AI agent rent a GPU by the minute, run a job, bring the results back and shut the GPU down. The same API key and balance also cover CloudGPU's OpenAI-compatible model API, so an agent can call a hosted model without renting anything.
"Fine-tune a 7B base model with LoRA on data/train.jsonl and put the adapter in ./outputs."
The agent checks live prices and quotes you, rents the GPU once you say yes, uploads your code and data, starts training in the background, watches the logs, downloads the adapter and destroys the instance. You get the files and the final cost.
It is a local (stdio) MCP server. It works with any MCP client that can start one: Claude Code, Cursor, Cline, opencode, goose, VS Code, Windsurf and others.
CLOUDGPU_API_KEY.Claude Code
claude mcp add cloudgpu --env CLOUDGPU_API_KEY=cgw-sk-... -- npx -y cloudgpu-mcp
Cursor ( ~/.cursor/mcp.json or .cursor/mcp.json )
{
"mcpServers": { "cloudgpu": { "command": "npx", "args": ["-y", "cloudgpu-mcp"], "env": { "CLOUDGPU_API_KEY": "cgw-sk-..." } } } }
</details>
Cline (MCP Servers → Configure MCP Servers → cline_mcp_settings.json )
{
"mcpServers": { "cloudgpu": { "command": "npx", "args": ["-y", "cloudgpu-mcp"], "env": { "CLOUDGPU_API_KEY": "cgw-sk-..." } } } }
</details>
opencode ( opencode.json )
{
"$schema": "https://opencode.ai/config.json", "mcp": { "cloudgpu": { "type": "local", "command": ["npx", "-y", "cloudgpu-mcp"], "environment": { "CLOUDGPU_API_KEY": "cgw-sk-..." }, "enabled": true } } }
</details>
goose ( ~/.config/goose/config.yaml , or goose configure → Add Extension → Command-line Extension)
extensions:
cloudgpu: name: cloudgpu type: stdio cmd: npx args: ["-y", "cloudgpu-mcp"] envs: CLOUDGPU_API_KEY: "cgw-sk-..." enabled: true timeout: 300
</details>
rules/cloudgpu.md into your project as AGENTS.md, .cursor/rules/cloudgpu.md or .clinerules/cloudgpu.md. It tells the agent to quote before renting, download before shutting down, and never leave a GPU running. The server also exposes the same text as the resource cloudgpu://rules.To check the install, ask your agent: "List the GPUs available, then estimate the cost for a 24 GB GPU for one hour. Do not create anything." You should see list_gpus and estimate_cost calls and a quote, and nothing is rented.
The same guidance is available as two Agent Skills:
skills/cloudgpu/SKILL.md: renting and using a GPU. Claude Code loads it on demand when you ask for a GPU job. It expects the cloudgpu MCP tools to be installed (see above).skills/cloudgpu-model-api/SKILL.md: calling the OpenAI-compatible model API at https://cloudgpu.app/v1 without renting a GPU. It works with the MCP tools or with just a CLOUDGPU_API_KEY. /plugin marketplace add mrhy7176/cloudgpu-mcp
/plugin install cloudgpu@cloudgpu
skills/cloudgpu/ and skills/cloudgpu-model-api/ to ~/.claude/skills/.skills/cloudgpu/ and skills/cloudgpu-model-api/ to .claude/skills/ in your project. npx skills add mrhy7176/cloudgpu-mcp
| Tool | What it does |
|---|---|
get_account | Balance, and how many instances the account may run at once |
list_gpus | GPU models with VRAM, live price per GPU-hour and availability |
list_templates | Ready-made images: JupyterLab, Ollama, ComfyUI, LLaMA-Factory, … |
estimate_cost | Live quote for a GPU and a number of hours, plus your balance afterwards; returns a quote_id |
create_instance | Rents from an approved quote, with a budget, a time limit and an idle limit |
get_status / list_instances | Status, minutes run, cost so far, auto-shutdown limits |
run_command | Runs a command on the instance; background=true for long jobs |
tail_logs | Latest log lines, whether the job finished, GPU utilisation |
upload / download | Files and folders between your computer and the instance (SFTP) |
stop_instance | Destroys the instance and stops billing |
list_models | Models on the OpenAI-compatible API, for inference without renting a GPU |
The server also provides a train_on_cloudgpu prompt.
create_instance only takes a quote_id from estimate_cost and user_confirmed=true.max_spend_usd, max_hours and an idle limit (60 minutes by default). CloudGPU's servers check them and destroy the instance when one is hit, even if your client has disconnected or your laptop is asleep.CLOUDGPU_MAX_SPEND_USD and CLOUDGPU_MAX_HOURS cap what the agent may set.stop_instance refuses until something has been downloaded, unless the user confirms force=true..ssh, .env, key files or your whole home directory needs allow_sensitive=true.CLOUDGPU_READ_ONLY=1 registers only the look-up tools.| Env | Default | |
|---|---|---|
CLOUDGPU_API_KEY | (required) | From https://cloudgpu.app/api |
CLOUDGPU_MAX_SPEND_USD | 50 | Highest budget the agent may set for one instance |
CLOUDGPU_MAX_HOURS | 24 | Longest time limit the agent may set |
CLOUDGPU_READ_ONLY | off | 1 = look-up tools only |
CLOUDGPU_BASE_URL | https://cloudgpu.app | Override the API host |
The key also works with the OpenAI-compatible API at https://cloudgpu.app/v1. Call list_models (or GET /v1/models) to see the available model IDs. Model prices are on cloudgpu.app/api.
The server wraps CloudGPU's public REST API, which any agent or script can call with the same key:
curl https://cloudgpu.app/v1/gpu/offers -H "Authorization: Bearer $CLOUDGPU_API_KEY"
The package also installs a cloudgpu command for using the same API from a terminal (Node.js 18.3 or newer, no extra dependencies):
npm install -g cloudgpu-mcp # or run it once with: npx -p cloudgpu-mcp cloudgpu --help
cloudgpu login # saves your key to ~/.config/cloudgpu/config.json (mode 0600) cloudgpu offers # GPU models with live price and availability cloudgpu up --gpu "RTX 4090" --template comfyui --max-minutes 120 --max-spend 5 --wait cloudgpu ssh # opens your system ssh to the instance cloudgpu down # destroys it and stops billing (asks first; --yes to skip)
| Command | What it does |
|---|---|
login | Save an API key (input hidden, or piped on stdin); checked against the API first |
offers [--template ID] | GPU models, VRAM, live price per GPU-hour, availability |
templates | Ready-made images and the GPU each recommends |
up --gpu MODEL [--template ID] [--count N] [--max-minutes N] [--max-spend USD] [--idle-minutes N] [--setup FILE] [--wait] | Rent an instance; --setup runs a bash script once as root after hand-over (log in /root/cloudgpu-setup.log); --wait polls until it is running or failed, then prints the SSH command and URL |
ls / status | Instances with status, minutes run and cost so far |
ssh [-- ARGS] | Run ssh with the instance's host, port and user; --show-password prints the password if there is one |
down [--yes] | Destroy the instance; its disk is erased, so download results first |
balance | Balance and how many instances the account may run |
CLOUDGPU_API_KEY takes precedence over the saved key, and CLOUDGPU_BASE_URL overrides the API host. Read commands accept --json; SSH passwords are left out of JSON unless you pass --show-password. Every command has --help. Errors print the API's message and exit non-zero (2 for usage errors).
CloudGPU here means cloudgpu.app. Prepaid balance, billed per minute; when the balance runs out, running instances are destroyed and their disks erased, so keep enough balance for the job and download results as you go.
npm install
npm test node src/index.js # stdio server; set CLOUDGPU_API_KEY first node src/cli.js --help
MIT, see LICENSE.