limrun-instance
Limrun ships a per-instance MCP server rather than one shared endpoint. Every iOS and Android instance exposes its own Model Context Protocol HTTP endpoint at status.mcpUrl once the instance reaches the ready state. The tool surface is device control only; builds, app installs, and asset uploads stay on the CLI and SDK because MCP tools have no access to the client filesystem.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport http
Tools
ios-screenshot-and-element-tree— Returns the current screenshot and the accessibility element tree in one call.ios-use— Performs a batch of actions in order. Action kinds - tap, tapElement, setElementValue, incrementElement, decrementElement, type, pressKey, scroll, wait, toggleKeyboard, openUrl, setOrientation, touchDown, touchMove, touchUp, keyDown, keyUp, buttonDown, buttonUp, deviceInfo, startRecording, stopRecording, discoverStoreKitConfig, clearStoreKitConfig, softReset.ios-open-url— Opens a URL or deep link in the simulator, including custom schemes such as exp:// for Expo Go.ios-app— Lists installed apps and launches or terminates them. Does not install apps.ios-logs— Fetches the last N combined stdout/stderr log lines for a given bundle ID.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.