> ## Documentation Index
> Fetch the complete documentation index at: https://docs.run.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# run.cloud MCP server

> Infrastructure that agents love: connect Claude, ChatGPT, Claude Code, Codex or any MCP client to cloud iOS simulators, Android emulators and Xcode builds with one URL.

Give your agent a phone. The run.cloud MCP server lets an AI agent start iOS
simulators and Android emulators, install your app, look at the screen, tap
through it and build Xcode projects for the simulator. One URL, sign in with
your run.cloud account, done.

```text theme={null}
https://mcp.run.cloud/mcp
```

The server speaks streamable HTTP and signs you in with OAuth 2.1 and dynamic
client registration, so there is no API key to copy.

## Set up your client

> [tab] Claude
>
> Add `https://mcp.run.cloud/mcp` as a custom connector in Claude or Claude
> Desktop. Step by step: [Use run.cloud in Claude](https://docs.run.cloud/integrations/claude.md).

> [tab] ChatGPT
>
> Connect run.cloud from ChatGPT. Step by step:
> [Use run.cloud in ChatGPT](https://docs.run.cloud/integrations/chatgpt.md).

> [tab] Claude Code
>
> ```bash theme={null}
> claude mcp add --transport http run-cloud https://mcp.run.cloud/mcp
> ```
>
> Then run `/mcp` inside Claude Code, choose **run-cloud** and sign in.

> [tab] Codex
>
> ```bash theme={null}
> codex mcp add run-cloud --url https://mcp.run.cloud/mcp
> codex mcp login run-cloud
> ```
>
> Run `/mcp` in the Codex TUI to check that **run-cloud** is connected. On a
> machine without a browser, use `codex mcp login run-cloud --no-browser`.

> [tab] Other clients
>
> Any MCP client works if it supports streamable HTTP with OAuth and uses a
> loopback callback (`http://localhost` or `http://127.0.0.1`). Add
> `https://mcp.run.cloud/mcp` as a remote server and sign in when the client
> asks.

## Sign in, organization and billing

The first time your client connects, a run.cloud page opens. Sign in or create
an account, choose the organization to bill, and approve.

Simulators your agent starts are billed to that organization at the normal
rate, \$0.02 per active simulator minute. See [pricing](https://run.cloud/pricing/).

The connection reaches simulators, uploaded apps and simulator builds in that
one organization. It cannot see your API keys, secrets, billing settings or
other organizations you belong to.

## What your agent can do

Your agent picks the tools itself. You do not call them by name.

* **Sessions:** start, list, keep alive, tag and stop iOS simulators and
  Android emulators.
* **Apps and URLs:** upload, install, launch and reload apps, and open web
  pages or deep links.
* **Seeing the screen:** screenshots, on-screen elements with their labels, and
  device logs.
* **Interacting:** taps, swipes, scrolls, gestures, typing, keys, hardware
  buttons and rotation.
* **Recordings and media:** record the screen and feed video or audio into the
  camera and microphone.
* **Xcode builds:** build a project for the iOS Simulator, read the build log
  and install the result.

Try: "Start an iPhone simulator, install the app from this link and tap
through the onboarding. Tell me where it breaks."

## Limits

Sessions started through MCP close after **5 minutes** without activity and
after **30 minutes** at most. An organization can have at most **3** running
at once while an agent is starting them. Organization-wide limits are on the
[Limits](https://docs.run.cloud/limits.md) page.

Xcode builds through MCP are simulator-only and unsigned. Use the
[CLI](https://docs.run.cloud/ios/build-with-xcode.md) for signed builds.

## Troubleshooting

**Sign-in keeps coming back.** The MCP server does not accept API keys. If
your client config sends a run.cloud API key (`rc_live_...`) as an
`Authorization` header or bearer token, the client keeps sending it after you
sign in, and every tool call fails. Remove the key from the config, for
example `bearer_token_env_var` or `http_headers` in Codex's `config.toml`,
then sign in again.

## Disconnect

* **Claude:** remove **run.cloud** under **Customize**, then **Connectors**.
* **ChatGPT:** disconnect **run.cloud** in the connected apps settings.
* **Claude Code:** `claude mcp logout run-cloud`, then
  `claude mcp remove run-cloud`.
* **Codex:** `codex mcp logout run-cloud`, then `codex mcp remove run-cloud`.

Log out before removing: `remove` alone only deletes the local configuration.
Your run.cloud account, apps and builds are not deleted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.