Limrun

com.limrunPublished by limrun.comOfficial publisherv0.3.2Updated Oct 24, 2026

Cloud iOS simulators and Android emulators your agent can create, drive, and throw away.

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Limrun's hosted MCP server lets an assistant create, drive and delete cloud iOS simulators and Android emulators.

What you can do
  • Create, list, inspect and delete iOS simulator and Android emulator instances
  • Drive iOS devices: tap, type, scroll, action chains, open URLs, list/launch/terminate apps, read logs, capture screenshots and element trees
  • Drive Android devices: tap and interact, open URLs, capture screenshots and element trees
  • Browse pre-installable app assets and fetch step-by-step agent skill procedures for builds and local-file work
When to use it
Useful when an agent needs a real mobile device to test an app, walk through a signup or onboarding flow, or check UI behavior on iOS and Android without owning hardware or maintaining a local emulator setup.
Requirements
Remote streamable-HTTP endpoint at mcp.limrun.com; nothing to install locally. Authentication is OAuth sign-in on first use, or a Limrun org API key as a bearer token for headless use. A Limrun account is required. Network access to the hosted service.
Before you install
Requires a Limrun account and either OAuth sign-in or an org API key, which grants access to your organization's devices. The assistant can create and delete cloud devices and launch or terminate apps on them, so unintended cleanup or app actions are possible. Devices run in Limrun's cloud, so app builds and test data you load there leave your machine.

Installation

In SourceWeft

  1. Open Limrun 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/com.limrun%2Fmcp/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": {
    "limrun": {
      "type": "http",
      "url": "https://mcp.limrun.com/mcp"
    }
  }
}

README

Limrun MCP Server

https://mcp.limrun.com/mcp is Limrun's remote MCP server. Connect it once and your agent can create cloud iOS simulators and Android emulators on demand, drive them through screenshots and the accessibility tree, and delete them when done. Devices are real simulators/emulators running in Limrun's cloud, not mocks.

This repository is the listing home for the server. The server is a hosted, remote streamable-HTTP MCP server; there is nothing to install from here.

What it does

  • Create and manage devices: create-ios-simulator, create-android-emulator, list-instances, get-instance-status, delete-instance (instances also self-terminate on inactivity).
  • Drive iOS: ios-use (tap, type, scroll, action chains), ios-app (list/launch/ terminate apps), ios-open-url, ios-logs, ios-screenshot-and-element-tree.
  • Drive Android: android-use, android-open-url, android-screenshot-and-element-tree.
  • Apps and skills: list-apps (pre-installable app assets), get-agent-skill (step-by-step CLI procedures for builds and anything touching local files, which stay on the lim CLI).

Configure

The endpoint is https://mcp.limrun.com/mcp (streamable HTTP, stateless). Auth is OAuth sign-in on first use, or a Limrun org API key as a bearer token for headless use. Sign up at limrun.com.

VS Code / Copilot (mcp.json):

json
{  "servers": {    "limrun": { "type": "http", "url": "https://mcp.limrun.com/mcp" }  }}

Claude Code:

bash
claude mcp add --transport http limrun https://mcp.limrun.com/mcp

Any other MCP client that speaks streamable HTTP works the same way; the server advertises its authorization server through standard discovery metadata, so OAuth-capable clients find the sign-in flow on their own.

Use

Ask your agent things like:

  • "Create an iOS simulator and show me a screenshot."
  • "Open example.com on it and tap the first link."
  • "Install my app from the asset list and walk through the signup flow."
  • "Clean up all my running devices."

Links

Source: README.md at commit 571563d

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

4
  1. v0.3.2LatestSep 25, 2026
  2. v0.3.1Sep 23, 2026
  3. v0.3.0Sep 17, 2026
  4. v0.2.3Sep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.