iOS Simulator▌
by joshuayoes
Use iOS Simulator for testing with tools like UI interaction and device info retrieval. Perfect as an iPhone emulator fo
Enables Claude to control iOS simulators for testing and debugging applications by providing tools for UI interaction, element inspection, and device information retrieval through Facebook's IDB tool.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / iOS developers testing app functionality
- / QA engineers automating mobile app testing
- / Debugging UI issues in iOS applications
capabilities
- / Tap and swipe on simulator screens
- / Type text into simulator apps
- / Take screenshots and record videos
- / Inspect UI elements and accessibility information
- / Get simulator device information
- / Describe screen content and element locations
what it does
Controls iOS simulators for app testing by automating UI interactions like tapping, swiping, typing, and taking screenshots. Uses Facebook's IDB tool to inspect elements and interact with running simulator instances.
about
iOS Simulator is a community-built MCP server published by joshuayoes that provides AI assistants with tools and capabilities via the Model Context Protocol. Use iOS Simulator for testing with tools like UI interaction and device info retrieval. Perfect as an iPhone emulator fo It is categorized under developer tools. This server exposes 13 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install iOS Simulator in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
iOS Simulator is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
iOS Simulator MCP Server
A Model Context Protocol (MCP) server for interacting with iOS simulators. This server allows you to interact with iOS simulators by getting information about them, controlling UI interactions, and inspecting UI elements.
Security Notice: Command injection vulnerabilities present in versions < 1.3.3 have been fixed. Please update to v1.3.3 or later. See SECURITY.md for details.
https://github.com/user-attachments/assets/453ebe7b-cc93-4ac2-b08d-0f8ac8339ad3
🌟 Featured In
This project has been featured and mentioned in various publications and resources:
- Claude Code Best Practices article - Anthropic's engineering blog showcasing best practices
- React Native Newsletter Issue 187 - Featured in the most popular React Native community newsletter
- Mobile Automation Newsletter - #56 - Featured a long running newsletter about mobile testing and automation resources
- punkeye/awesome-mcp-server listing - Listed in one of the most popular curated awesome MCP servers collection
Tools
get_booted_sim_id
Description: Get the ID of the currently booted iOS simulator
Parameters: No Parameters
open_simulator
Description: Opens the iOS Simulator application
Parameters: No Parameters
ui_describe_all
Description: Describes accessibility information for the entire screen in the iOS Simulator
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
}
ui_tap
Description: Tap on the screen in the iOS Simulator
Parameters:
{
/**
* Press duration in seconds (decimal numbers allowed)
*/
duration?: string;
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/** The x-coordinate */
x: number;
/** The y-coordinate */
y: number;
}
ui_type
Description: Input text into the iOS Simulator
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/**
* Text to input
* Format: ASCII printable characters only
*/
text: string;
}
ui_swipe
Description: Swipe on the screen in the iOS Simulator
Parameters:
{
/**
* Swipe duration in seconds (decimal numbers allowed)
*/
duration?: string;
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/** The starting x-coordinate */
x_start: number;
/** The starting y-coordinate */
y_start: number;
/** The ending x-coordinate */
x_end: number;
/** The ending y-coordinate */
y_end: number;
/** The size of each step in the swipe (default is 1) */
delta?: number;
}
ui_describe_point
Description: Returns the accessibility element at given co-ordinates on the iOS Simulator's screen
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/** The x-coordinate */
x: number;
/** The y-coordinate */
y: number;
}
ui_view
Description: Get the image content of a compressed screenshot of the current simulator view
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
}
screenshot
Description: Takes a screenshot of the iOS Simulator
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/** File path where the screenshot will be saved. If relative, it uses the directory specified by the `IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR` env var, or `~/Downloads` if not set. */
output_path: string;
/** Image format (png, tiff, bmp, gif, or jpeg). Default is png. */
type?: "png" | "tiff" | "bmp" | "gif" | "jpeg";
/** Display to capture (internal or external). Default depends on device type. */
display?: "internal" | "external";
/** For non-rectangular displays, handle the mask by policy (ignored, alpha, or black) */
mask?: "ignored" | "alpha" | "black";
}
record_video
Description: Records a video of the iOS Simulator using simctl directly
Parameters:
{
/** Optional output path. If not provided, a default name will be used. The file will be saved in the directory specified by `IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR` or in `~/Downloads` if the environment variable is not set. */
output_path?: string;
/** Specifies the codec type: "h264" or "hevc". Default is "hevc". */
codec?: "h264" | "hevc";
/** Display to capture: "internal" or "external". Default depends on device type. */
display?: "internal" | "external";
/** For non-rectangular displays, handle the mask by policy: "ignored", "alpha", or "black". */
mask?: "ignored" | "alpha" | "black";
/** Force the output file to be written to, even if the file already exists. */
force?: boolean;
}
stop_recording
Description: Stops the simulator video recording using killall
Parameters: No Parameters
install_app
Description: Installs an app bundle (.app or .ipa) on the iOS Simulator
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/** Path to the app bundle (.app directory or .ipa file) to install */
app_path: string;
}
launch_app
Description: Launches an app on the iOS Simulator by bundle identifier
Parameters:
{
/**
* Udid of target, can also be set with the IDB_UDID env var
* Format: UUID (8-4-4-4-12 hexadecimal characters)
*/
udid?: string;
/** Bundle identifier of the app to launch (e.g., com.apple.mobilesafari) */
bundle_id: string;
/** Terminate the app if it is already running before launching */
terminate_running?: boolean;
}
💡 Use Case: QA Step via MCP Tool Calls
This MCP server allows AI assistants integrated with a Model Context Protocol (MCP) client to perform Quality Assurance tasks by making tool calls. This is useful immediately after implementing features to help ensure UI consistency and correct behavior.
How to Use
After a feature implementation, instruct your AI assistant within its MCP client environment to use the available tools. For example, in Cursor's agent mode, you could use the prompts below to quickly validate and document UI interactions.
Example Prompts
-
Verify UI Elements:
Verify all accessibility elements on the current screen -
Confirm Text Input:
Enter "QA Test" into the text input field and confirm the input is correct -
Check Tap Response:
Tap on coordinates x=250, y=400 and verify the expected element is triggered -
Validate Swipe Action:
Swipe from x=150, y=600 to x=150, y=100 and confirm correct behavior -
Detailed Element Check:
Describe the UI element at position x=300, y=350 to ensure proper labeling and functionality -
Show Your AI Agent the Simulator Screen:
View the current simulator screen -
Take Screenshot:
Take a screenshot of the current simulator screen and save it to my_screenshot.png -
Record Video:
Start recording a video of the simulator screen (saves to the default output directory, which is `~/Downloads` unless overridden by `IOS_SIMULATOR_MCP_DEFAULT_OUTPUT_DIR`) -
Stop Recording:
Stop the current simulator screen recording -
Install App:
Install the app at path/to/MyApp.app on the simulator -
Launch App:
Launch the Safari app (com.apple.mobilesafari) on the simulator
Prerequisites
- Node.js
- macOS (as iOS simulators are only available on macOS)
- Xcode and iOS simulators installed
- Facebook IDB tool (see install guide)
Installation
This section provides instructions for integrating the iOS Simulator MCP server with different Model Context Protocol (MCP) clients.
Installation with Cursor
Cursor manages MCP servers through its configuration file located at ~/.cursor/mcp.json.
Option 1: Using NPX (Recommended)
- Edit your Cursor MCP configuration file. You can often open it directly from Cursor or use a command like:
# Open with your default editor (or use 'code', 'vim', etc.) open ~/.cursor/mcp.json # Or use Cursor's command if available # cursor ~/.cursor/mcp.json - Add or update the
mcpServerssection with the iOS simulator server configuration:{ "mcpServers": { // ... other servers might be liste
FAQ
- What is the iOS Simulator MCP server?
- iOS Simulator is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for iOS Simulator?
- This profile displays 71 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.6★★★★★71 reviews- ★★★★★Sakura Abebe· Dec 28, 2024
iOS Simulator has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Aarav Malhotra· Dec 16, 2024
iOS Simulator is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Olivia Rao· Dec 8, 2024
iOS Simulator is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Michael Johnson· Dec 8, 2024
Useful MCP listing: iOS Simulator is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Dhruvi Jain· Dec 4, 2024
I recommend iOS Simulator for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Olivia Patel· Dec 4, 2024
According to our notes, iOS Simulator benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Ren Ramirez· Dec 4, 2024
Strong directory entry: iOS Simulator surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Oshnikdeep· Nov 23, 2024
Strong directory entry: iOS Simulator surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Arya Martinez· Nov 23, 2024
iOS Simulator has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Neel Srinivasan· Nov 23, 2024
I recommend iOS Simulator for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
showing 1-10 of 71