[CYBERNETIC PHYSICS]

[MCP FOR ROBOTICS]

VIBE CODE
ROBOTICS.

Quad‑Code MCP turns intent into Isaac Sim actions with tool-executed runs, logged traces, and shareable outputs — no local GPU setup.

[TOOL-EXECUTED][LOGGED TRACES][WEBRTC VIEWER][SSH ACCESS][BUDGET CAPS][FROM 0 RTX 4090]
SEE QUAD-CODE ↓

POST /mcp

CLAUDE CODE ENTRYPOINT

WS /v1/bridge

CONTAINER SESSION BRIDGE

USD

ARTIFACTS + ENVIRONMENTS

[QUAD-CODE MCP]

[READY]

[INTENT]

“Start an Isaac Sim session, spawn a robot, and give me the viewer URL.”

[PLAN]

  • >Create session (RTX 4090)
  • >Wait for bridge ready
  • >Run isaac.* actions
  • >Return artifacts + logs

[TRACE]

sessions.create(gpu_spec="RTX_4090")
sessions.get(session_id="sess_…")
sessions.set_active("sess_…")
isaac.get_scene_info()
→ viewerUrl: https://wagmi…

[ARTIFACTS]

  • [+]viewer_url.txt
  • [+]session_status.json
  • [+]mcp_trace.log
  • [+]published_env.usd (optional)
TOOL-EXECUTED RUNSEVERY ACTION LOGGEDARTIFACTS ARE VERSIONEDBUDGET CAPS + AUTO SHUTDOWNNO LOCAL GPU / NO DRIVER SETUP

[WHAT IS QUAD-CODE MCP?]

One intent → four synchronized outputs. This is how “vibe coding” stays credible: the system runs tools, records the trace, and produces artifacts you can reproduce.

[INTENT]

Natural language goals, constraints, and context.

[PLAN]

Structured steps with budget/guardrails and validation.

[TRACE]

Auditable tool calls + results (not just chat).

[ARTIFACTS]

Shareable outputs: viewer URLs, logs, USD bundles, metrics.

EXAMPLE TRACE

# intent: "spawn a robot and open viewer"
sessions.create(gpu_spec="RTX_4090")
sessions.set_active("sess_…")
isaac.get_scene_info()
isaac.create_physics_scene(floor=true)
isaac.create_robot(robot_type="g1", position=[0,0,0])
→ artifacts: viewer_url.txt, session_status.json

CONNECT CLAUDE CODE (MCP)

claude mcp add cyberneticphysics --transport http --scope user \
  https://api.cyberneticphysics.com/mcp \
  --header "Authorization: Bearer <cp_live_…>"

[CONTROL LOOP]

[1]

DESCRIBE

Intent + constraints

[2]

COMPILE

Plan + guardrails

[3]

RUN

Sessions + tool calls

[4]

PUBLISH

Artifacts + versions

[MODULES]

[MCP GATEWAY]

Claude Code → MCP tools (`sessions.*`, `isaac.*`). Logged tool calls with scoped API keys.

[ISAAC SIM SESSIONS]

One-click GPU sessions with WebRTC viewer + direct SSH. Auto-shutdown and workspace environments.

[3D PIPELINE]

Upload photos/video → reconstruction job → USD/USDZ artifacts you can load into Isaac or share.

[COST GOVERNOR]

Pay for execution time. Budget caps, idle timeouts, and usage visibility built into the control plane.

VIEW PRICING

[REAL FLOWS]

[START A SESSION]

  • >One click → GPU on Vast.ai
  • >Viewer URL + SSH command
  • >Auto-shutdown guardrails
sessions.create(gpu_spec="RTX_4090")
→ viewerUrl: https://wagmi…

[CONTROL ISAAC VIA MCP]

  • >Bridge to Isaac extension
  • >Real tool calls + responses
  • >Repeatable workflows
isaac.create_robot(robot_type="g1")
isaac.transform(prim_path="/World/…")

[PUBLISH ARTIFACTS]

  • >USD bundles + logs
  • >Workspace-scoped access
  • >Shareable versions
publish(version="v12")
→ artifacts: env.usd, metrics.json

[PRICING]

PAY AS YOU GO

FROM 0

  • [+]RTX 4090 GPUs
  • [+]Pay per second
  • [+]No commitment
  • [+]Budget caps + idle shutdown

TEAM

CUSTOM

  • [+]Priority GPU access
  • [+]Team workspaces
  • [+]Volume discounts
  • [+]Dedicated support

READY TO VIBE CODE?

Connect Claude Code via MCP, start an Isaac Sim session, and ship repeatable tool runs. No local GPU setup required.