The cloudgpu-mcp Model Context Protocol (MCP) server provides seamless integration between AI assistants (such as Claude Desktop, Cursor, and Claude Code) and CloudGPU MCP server: let MCP clients rent a per-minute GPU, run a job, download results and shut it down. By connecting this server, your AI agent gains specialized capabilities to inspect, query, and automate tasks within the DevOps domain.
Once installed in Claude Desktop or Cursor, try asking your assistant:
Copy the config for your editor. Verify environment variables or setup notes in the README.
Add to claude_desktop_config.json:
{
"mcpServers": {
"cloudgpu-mcp": {
"command": "npx",
"args": [
"-y",
"cloudgpu-app/cloudgpu-mcp"
]
}
}
}
# CloudGPU MCP
CloudGPU MCP server: let an AI agent compare GPU compute costs, approve source-specific billing, 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: Codex, Claude Code, Cursor, Cline, open