Give Claude Code iOS—in the cloud.

Claude can keep running on Linux, over SSH, or in a remote session. AgentCloud accepts build-ready iOS source or a Simulator-compatible .app, then gives Claude a disposable hosted Simulator through project-scoped OAuth MCP.

Test with Claude free See exact setup

No card · 2 Simulator hours · 1 source build

claude / agentcloudproject MCP connected
Terminalcurrent Claude Code syntax
$ claude mcp add --transport http \
  --scope project agentcloud \
  https://api.agentcloud.so/mcp
Added HTTP MCP server agentcloud.

› /mcp
AgentCloud · OAuth authenticated
Build this branch for iPhone Simulator. Launch it, verify onboarding, and retain the screenshots and logs.
AgentCloud runillustrative data
ios.create_source_uploadsource accepted
ios.buildSimulator artifact ready
ios.createiPhone 16 Pro
ios.observescreen + accessibility
ios.acttap “Continue”
ios.logs0 errors
screens · actions · logs · video

Claude gets focused tools. Your team gets the run.

This is the actual AgentCloud interface with illustrative data. Each action stays beside the screen, accessibility state, logs, and recording it produced.

AgentCloud run detail showing an iPhone Simulator beside the agent action timeline and retained evidence.
Review the full Claude runInspect what the agent saw and did instead of accepting a text claim that the flow passed.Open full resolution
AgentCloud Connect screen showing the team MCP URL and OAuth connection steps.
One remote MCP URLClaude discovers OAuth metadata and authorizes team access in the browser.
AgentCloud Runs screen listing active, completed, and failed Simulator sessions.
Durable run historyCompleted and failed sessions remain available for review through the plan retention window.

One command. One OAuth approval.

Anthropic recommends remote HTTP for cloud MCP services. Project scope writes the connection to .mcp.json, so the repository carries the AgentCloud tool boundary into remote environments.

  1. 1
    Create a free workspace

    Start with 2 Simulator hours and one managed source build, without a card.

  2. 2
    Add AgentCloud at project scope

    Commit the remote HTTP MCP definition when the team should share it.

  3. 3
    Authorize from /mcp

    Select AgentCloud and approve workspace access in the browser.

  4. 4
    Ask Claude to verify

    Send build-ready source or a Simulator .app, then let Claude operate the run.

shellClaude Code CLI
# Share AgentCloud with this repository
claude mcp add --transport http \
  --scope project \
  agentcloud https://api.agentcloud.so/mcp

# In Claude Code, authorize the server
/mcp
Ready for remote iOS workClaude can discover the focused AgentCloud tools from the project configuration.

Local computer use or remote iOS MCP.

Both let Claude verify a native interface. The runtime boundary—and the session that can reach it—is different.

Constraint Claude computer use AgentCloud MCP
Where Claude runsInteractive session on the Mac that owns SimulatorCloud, Linux, SSH, or another machine with network access
iOS runtimeLocal Xcode and SimulatorManaged build capacity and hosted disposable Simulator
Machine accessApproved screen and app control on the local desktopFocused OAuth MCP; no Mac desktop, Xcode UI, or raw shell
Parallel sessionsOne computer-use session at a time1, 4, or 10 concurrent Simulators by plan
Review evidenceScreenshots and output remain in the Claude sessionScreens, actions, accessibility, logs, artifacts, and video stay joined as a run

Give the remote task an iOS acceptance loop.

Once AgentCloud is in the project configuration, Claude can choose the focused build and Simulator tools needed to verify a real change.

Build in a cloud sessionmanaged build
Build the current branch for iPhone Simulator, launch it, verify the onboarding deep link, and show me the retained screenshots and logs.
ios.create_source_uploadios.buildios.createios.observe
Verify an existing app.app upload
Install this Simulator-compatible app, reproduce checkout, use accessibility labels where possible, and report the first failing step with evidence.
ios.create_app_uploadios.installios.actios.logs
Review parallel changesdurable evidence
Run each changed flow on a clean Simulator, compare it with the acceptance criteria, then destroy the sessions and link the completed runs.
ios.observeios.actios.logsios.destroy

The exact boundary.

A hosted iOS build-and-Simulator workflow for Claude Code, not a remote Mac rental.

Can Claude Code on the web use AgentCloud?

Claude Code cloud sessions include project-scoped .mcp.json configuration from the repository. The environment must allow network access to AgentCloud, and a user must approve the project MCP server and complete OAuth.

Does AgentCloud replace Claude computer use?

No. Computer use is the local path when Claude and Simulator share a Mac. AgentCloud is the focused remote path when Claude runs elsewhere or when durable team-visible run evidence matters.

Does AgentCloud provide a Mac or Xcode?

No. Claude receives focused build and Simulator tools. AgentCloud does not expose a Mac desktop, Xcode interface, or raw worker shell.

What can Claude upload?

Build-ready iOS source containing its Xcode workspace or project, or a Simulator-compatible .app bundle. Device-signed .ipa files are not supported.

How does Claude authenticate?

Claude connects to https://api.agentcloud.so/mcp, discovers AgentCloud’s OAuth metadata, and completes OAuth 2.1 authorization with PKCE in the browser.

Let one remote Claude task verify iOS for real.

Start with 2 free Simulator hours and one managed source build. No card required.

Test with Claude free