For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/local-ios
Skill page: https://www.mcpbundles.com/skills/local-ios
Tools: 20
Live probe refreshed Nov 21, 2026 · Endpoint host mcp.mcpbundles.com
What you can do with Local iOS
Built for
iOS Developers, Mobile QA, Simulator Testing, Agent Workflows
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
Local iOS
Add to your AI client, then sign in once when you connect.
Automate the iOS Simulator on your Mac from Claude Code or Cursor — tap, swipe, type, screenshot, and launch apps through Appium over Desktop.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Best foriOS DevelopersMobile QASimulator TestingAgent Workflows
Capture a screenshot and page source of the current view, then list interactive elements visible on screen.
Context to know first
What is Local iOS best for?
It is best when you already run Xcode and an iOS Simulator on macOS and want your agent to drive it without cloud device farms.
Do I need MCPBundles Desktop?
Yes. Desktop bridges your agent to the Appium server on localhost. Install it on the Mac where the simulator runs and keep Appium listening on port 4723.
How is Local iOS different from Mobile Device?
Local iOS drives a simulator on your Mac through Desktop. Mobile Device provisions real phones and tablets in AWS Device Farm.
AI Skill
SKILL.md
Domain knowledge for Local iOS — workflow patterns, data models, and gotchas for your AI agent.
Local iOS (Appium / XCUITest)
Automate a developer-machine iOS Simulator (or USB-attached real device) via
the local Appium 2.x server. Traffic flows backend → desktop proxy TCP
tunnel → 127.0.0.1:4723 on the user's macOS machine. XCUITest is the
active driver.
Prerequisites
macOS with Xcode + Command Line Tools (xcode-select --install).
A booted iOS Simulator (xcrun simctl list,
xcrun simctl boot 'iPhone 15') or a real device with the
appropriate WebDriverAgent provisioning profile.
Appium 2.x running locally (appium) with the XCUITest driver
installed (appium driver install xcuitest). For Safari sessions
start with browser=true.
Start a local Appium iOS session through the MCPBundles desktop proxy. Requires a booted simulator and a running local Appium 2.x server. Returns the WebDriver session id once provisioning completes.
Local iOS Create Session — Start a local Appium iOS session through the MCPBundles desktop proxy. Requires a booted simulator and a running local Appium 2.x server. Returns the WebDriver session id once provisioning completes.
Local iOS Find Element — Find a UI element on the active local iOS session and return its WebDriver element id and visible text.
Local iOS Get Contexts — List the Appium contexts on the active local iOS session. ``NATIVE_APP`` is the native UI tree; ``WEBVIEW_<package>`` (Android) or ``WEBVIEW_<id>`` (iOS) contexts expose the embedded Chrome / WKWebView so you can drive Capacitor / Cordova / hybrid apps with HTML page source and CSS selectors.
Local iOS Get Page Source — Return the current UI hierarchy from the active local iOS session (XML for native apps, HTML for browser sessions). Use this before tapping or typing to discover element ids and accessibility labels.
Local iOS Get WebView HTML — Capture the WebView HTML on the active local iOS session. Switches to the first WEBVIEW context (auto-detected) and returns ``document.documentElement.outerHTML``. Use this for Capacitor / Cordova / hybrid apps where the native page source is just an opaque WebView shell.
Local iOS Get Window Size — Return the WebDriver viewport size for the active local iOS session, used for coordinate-based taps and swipes.
Local iOS Install App — Install an app on the active local iOS session via ``mobile: installApp``. The path is resolved on the developer machine running Appium, not the backend.
Local iOS Launch App — Activate (launch / foreground) an installed app on the active local iOS session via ``mobile: activateApp``.
Local iOS Navigate URL
Frequently Asked Questions
What is Local iOS best for?
It is best when you already run Xcode and an iOS Simulator on macOS and want your agent to drive it without cloud device farms.
Do I need MCPBundles Desktop?
Yes. Desktop bridges your agent to the Appium server on localhost. Install it on the Mac where the simulator runs and keep Appium listening on port 4723.
Standard connector25 free calls every 30 days, then from $19/month
$19 / month
Subject to fair usage limits
— Open a URL on the active local iOS session. Android uses an Android VIEW intent through the active Appium session; iOS uses the Safari WebDriver session (must be started with ``browser=true``).
Local iOS Screenshot — Capture a PNG screenshot from the active local iOS Appium session. Returns the image so the agent can see what is on screen.
Local iOS Session Info — Inspect the active local iOS Appium session — WebDriver id, base URL, capabilities, and start time.
Local iOS Stop Session — Stop the active local iOS Appium session and release the WebDriver lease so the emulator/simulator is free for the next run.
Local iOS Swipe — Swipe on the active local iOS session via W3C Actions. Use ``up`` to scroll content up, ``down`` to scroll down, etc.
Local iOS Switch Context — Switch the active Appium context on the local iOS session. After switching to a WEBVIEW context, ``*_get_page_source`` returns HTML, ``*_find_element`` accepts CSS selectors, and ``*_navigate_url`` drives the WebView directly.
Local iOS Tap — Tap at ``(x, y)`` on the active local iOS session using W3C Actions. Coordinates are WebDriver viewport units.
Local iOS Tap Element — Tap a UI element by its WebDriver element id from a prior element find on this session.
Local iOS Terminate App — Force-stop an app on the active local iOS session via ``mobile: terminateApp``. Useful between test runs to start from a cold-launch state.
Local iOS Type Text — Type text on the active local iOS session, either into a specific element or the currently focused field.
Local iOS Uninstall App — Uninstall an app from the active local iOS session via ``mobile: removeApp``.
Local iOS Wait For Element — Poll for a UI element on the active local iOS session until it is found or the timeout elapses. Returns the WebDriver element id and its text once present, or raises if the element never appears.
Local iOS drives a simulator on your Mac through Desktop. Mobile Device provisions real phones and tablets in AWS Device Farm.
What do I need installed first?
Xcode with Command Line Tools, a booted iOS Simulator, Appium 2.x with the XCUITest driver, and MCPBundles Desktop.
How do I connect Local iOS to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/local-ios. Authentication is handled automatically.
How many tools does Local iOS provide?
Local iOS provides 20 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
What authentication does Local iOS require?
Local iOS uses API Key. Local iOS requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in developer tools
Other MCP servers in this category from the directory index