AgentCloud — Hosted iOS Simulator MCP

so.agentcloudPublished by agentcloud.soOfficial publisherv0.1.0Updated Oct 24, 2026

Build, run, and inspect iOS apps in disposable hosted Simulators from cloud coding agents.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A hosted iOS Simulator MCP server that lets an assistant build, run and inspect iOS apps in disposable cloud simulators.

What you can do
Build iOS apps inside hosted, disposable Simulator instances in the cloud, without a local Mac setup. Run apps in those simulators so an assistant can exercise them. Inspect the running apps and simulator state as part of a cloud coding agent workflow. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when a cloud coding agent needs to compile, launch and check an iOS app but has no local macOS or Xcode environment, and disposable simulator sessions are acceptable.
Requirements
A remote endpoint at api.agentcloud.so over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. Network access to the hosted service is needed.
Before you install
Access requires OAuth sign-in to a third-party hosted service, so app code and build artifacts are sent to that provider. Simulators are described as disposable, so work may not persist. Pricing, quotas and data handling are not stated in the provided material.

Installation

In SourceWeft

  1. Open AgentCloud — Hosted iOS Simulator MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/so.agentcloud%2Fios-simulator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "agentcloud-hosted-ios-simulator": {
      "type": "http",
      "url": "https://api.agentcloud.so/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.