Skip to main content
run.cloud works as a connector in Claude. Claude can start iOS simulators and Android emulators on your run.cloud account, put an app or a web page on them, look at the screen and drive them for you. The connector URL is:

What you can ask for

  • “Start an iPhone simulator, open https://example.com and take a screenshot.”
  • “Install the app from this link and tap through the onboarding. Tell me where it breaks.”
  • “Build the Xcode project at this link for the simulator and launch it.”
  • “Record a video of the sign-up flow on Android.”
  • “Which simulators are running? Stop them.”

Connect in Claude and Claude Desktop

  1. Open Customize, then Connectors. Select Add, then Add custom connector.
  2. Name it run.cloud, paste https://mcp.run.cloud/mcp as the URL and select Continue. Keep the authentication settings Claude detects, then select Add.
  3. Select Connect on the connector, or wait until Claude first uses a run.cloud tool and asks you to connect. A run.cloud page opens.
  4. Sign in, or create a run.cloud account.
  5. Review what Claude asks for, choose the organization that sessions are billed to, and select Approve.
On Team and Enterprise plans, an Owner adds the connector under Organization settings, then Connectors, and each member connects with their own run.cloud account.

Connect in Claude Code

Then run /mcp inside Claude Code, choose run-cloud and authenticate. Your browser opens the same run.cloud sign-in and approval page.

What the connection can reach

The connection can use simulators, uploaded apps and simulator builds in the one organization you chose. It cannot see your API keys, secrets, billing settings, sandboxes or other run.cloud products, and it cannot reach other organizations you belong to.

Tools

Claude picks the tools itself. You do not call them by name. Sessions
  • start_simulator: Start an iOS simulator or Android emulator.
  • list_simulators, get_simulator: See running sessions and their state.
  • keep_simulator_alive: Keep an idle session open a little longer.
  • set_simulator_tags: Label a session.
  • stop_simulator: End a session.
Apps and URLs
  • create_app_upload, finish_app_upload: Upload a build from your computer through a private, short-lived link.
  • upload_app, list_apps, download_app, delete_app: Manage app builds you upload.
  • install_app, launch_app, reload_app: Put an app on a device and run it.
  • get_app_launch: Check the progress of an install and launch.
  • open_url: Open a web page or deep link.
Seeing the screen
  • take_screenshot: Capture the screen. Claude sees the image.
  • read_screen: Read the on-screen elements and their labels.
  • get_device_logs: Read device and app logs.
Interacting
  • tap, swipe, scroll, gesture: Touch input.
  • type_text, press_key, toggle_keyboard: Keyboard input.
  • press_button: Hardware buttons such as Home.
  • rotate_device: Orientation.
  • simulate_memory_warning, set_render_debug: Debugging aids.
Recordings and media
  • start_recording, stop_recording: Record the screen.
  • list_recordings, get_recording, download_recording: Get recordings.
  • inject_camera_video, inject_microphone_audio: Feed media into the camera or microphone.
Xcode builds
  • start_xcode_build, rebundle_xcode_build: Build a source archive for the simulator.
  • get_xcode_build, list_xcode_builds: Check build status.
  • get_xcode_build_logs, get_xcode_build_events: Read the build log.
  • download_build_artifact: Get the built app.
  • cancel_xcode_build: Stop a build.

Getting an app onto a simulator

A build on your computer needs no public link. Claude calls create_app_upload and gets a private upload link that accepts the file once and expires after a short time. Claude uploads the file to it with curl and calls finish_app_upload, which checks the size and MD5. Then Claude can install or launch the app. This needs a Claude that can run commands on your computer, such as Claude Code or Claude Desktop with a terminal tool. You can also give Claude a download link to a zipped simulator app (.app.zip) or an .apk, ask it to install something you already uploaded, or upload builds with the CLI. A download link must be https on a public host, not a private network address. A signed, private link is fine, and a download that stalls is dropped. Xcode builds work the same way: give Claude an https link to a .zip of the project source, up to 100 MiB.

Xcode builds are simulator-only

Through the connector, run.cloud builds for the iOS Simulator only. It does not sign builds, create IPAs for devices or the App Store, or accept certificates, provisioning profiles or passwords. Use the CLI for signed builds.

Billing

Simulators that Claude starts are billed to the organization you chose when you connected, at the normal run.cloud rate. See pricing. To keep forgotten sessions from running up usage, every session started through the connector closes after 5 minutes without activity and after 30 minutes at most. While a connector is starting simulators, you can have at most 3 running at once in that organization, counting ones you started elsewhere. Ask Claude to stop one, or start a new one when a session has closed.

Disconnect

  • Claude and Claude Desktop: open Customize, then Connectors, and remove run.cloud.
  • Claude Code: run claude mcp logout run-cloud to revoke the connection’s tokens, then claude mcp remove run-cloud. remove alone only deletes the local configuration.
Your run.cloud account, apps and builds are not deleted.

Troubleshooting

For anything else, see support or email [email protected].