How to give Claude Code, Codex or Cursor access to GPUs (MCP setup)
Connect one MCP server and your coding agent can estimate, launch and watch GPU jobs on your account, with dry runs and spending limits.
Short answer: connect your coding agent to a GPU platform’s MCP server. The agent can then estimate, launch, watch and fetch results from GPU jobs from the same chat where it wrote the code. With Nodus that is one command per client, and every paid action shows a dry run and cost estimate before it runs.
Coding agents are great at writing a training script and terrible at the part after: finding a GPU, shipping code to it, watching logs, copying results back. MCP closes that loop.
Claude Code
Section titled “Claude Code”claude mcp add --scope user --transport http nodus https://api-next.nodus-compute.ai/mcpThen run /mcp, pick nodus, and sign in in your browser.
codex mcp add nodus --url https://api-next.nodus-compute.ai/mcpcodex mcp login nodusCursor
Section titled “Cursor”Add this to ~/.cursor/mcp.json:
{ "mcpServers": { "nodus": { "type": "http", "url": "https://api-next.nodus-compute.ai/mcp" } }}Any other MCP client
Section titled “Any other MCP client”Add a remote HTTP MCP server with URL https://api-next.nodus-compute.ai/mcp and follow the sign-in prompt. Prefer a local server? Install the CLI and run nodus mcp install, which configures the agents on your machine.
Verify without spending money
Section titled “Verify without spending money”Ask the agent: “List my Nodus jobs.” That is read only. A good first prompt for any agent that can read URLs:
Read https://nodus-compute.ai/connect.md and help me connect Nodus to this agent.Verify setup by listing my jobs. Do not start paid compute.What the agent can actually do
Section titled “What the agent can actually do”The server exposes generic tools over every resource: get, describe, logs, estimate, apply, exec and more. In practice that means prompts like:
- “Run train.py on a 24 GB GPU with a $5 cap and stream the logs.”
- “Why did job/train fail?”
- “Fine-tune Qwen3 0.6B with LoRA on chats.jsonl and download the adapter.”
- “What did my sandboxes cost this week?”
Guardrails that matter when an agent holds your credit card
Section titled “Guardrails that matter when an agent holds your credit card”- Writes are dry-run first. The agent sees the object as it would be created plus the cost estimate, and it only runs once confirmed.
- Same limits as you. The agent uses your account, projects, budgets and spending caps. A project budget stops it from overspending even if it gets creative.
- Hard caps per job.
maxCostUSDstops a job gracefully, with a checkpoint, before it passes the cap. - Frozen rates. The hourly rate is fixed when the machine is chosen and holds for the whole run.
Do I need a separate “agents” product to use Claude Code with GPUs? No. MCP is enough. Nodus Agents is a different feature for running agent conversations inside Nodus.
Which GPU does the agent get? By default the cheapest offering that fits the request and can start now, within your limits. You can ask for a specific type like H100 or B200.
What does it cost to try? New accounts get a $30 starter grant, no card needed for the first runs.
Setup for every client: nodus-compute.ai/connect
More from the blog
pricing3 min read
Cloud GPU pricing, October 2026: what an H100, H200, B200 or B300 costs per hour
Listed per GPU-hour prices for B300, B200, H200, H100, A100, L40S, L4 and RTX cards as of October 8, 2026, with a training-run cost example.
Read the postcheckpointing2 min read
How to make GPU training survive spot preemption (without babysitting it)
Save model, optimizer and step to one directory, write atomically, resume on start, and let the platform carry that directory across a reclaim.
Read the post