Cloud iOS simulators and Android emulators your agent can create, drive, and throw away.
One address for any MCP client. You sign in at api.limrun.com once, after adding it.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
| Access to | Read | Change |
|---|---|---|
| Mcp | Not stated: mcp | |
From the sign-in at api.limrun.com, as the endpoint publishes it. You approve it there.
Odel could not list its tools without signing in.
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.
create-ios-simulator, create-android-emulator,
list-instances, get-instance-status, delete-instance (instances also
self-terminate on inactivity).ios-use (tap, type, scroll, action chains), ios-app (list/launch/
terminate apps), ios-open-url, ios-logs, ios-screenshot-and-element-tree.android-use, android-open-url,
android-screenshot-and-element-tree.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).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):
{
"servers": {
"limrun": { "type": "http", "url": "https://mcp.limrun.com/mcp" }
}
}
Claude Code:
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.
Ask your agent things like:
com.limrun/mcp in the official MCP registry