메뉴
Automates iOS and Android simulators/emulators for mobile app development and testing. Use when the user needs to interact with a mobile simulator, test a mobile app, tap buttons, swipe, type text, take screenshots, or automate any mobile device interaction.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Runs automated code reviews using configurable reviewer agents. Use during or after implementation to check code quality, security, and best practices.
Executes an implementation plan by writing code. Use when ready to implement a plan that has been brainstormed, planned, and approved.
Creates concrete implementation plans from brainstormed ideas. Use when ready to turn an idea into actionable steps — after px-brainstorm, before px-implement.
Fetches Figma designs via MCP and implements them as React components. Use when asked to build, implement, or code a UI from a Figma link or design.
Facilitates idea exploration through conversation. Use when starting a new project, feature, or exploring solutions — before any planning or implementation.
Reviews completed work to document learnings, mistakes, and patterns for future cycles. Use after implementation is done or when reflecting on past work.
| name | mobile-mcp |
| description | Automates iOS and Android simulators/emulators for mobile app development and testing. Use when the user needs to interact with a mobile simulator, test a mobile app, tap buttons, swipe, type text, take screenshots, or automate any mobile device interaction. |
Interact with iOS simulators, Android emulators, and real devices through structured accessibility data and coordinate-based taps. No computer vision model required — uses native accessibility trees when available, falls back to screenshot-based coordinates.
xcode-select --install)adb on PATH)Every mobile automation follows this pattern:
mobile_list_available_devices to find available simulators/emulatorsmobile_launch_app with the bundle/package IDmobile_list_elements_on_screen to get UI elements with coordinatesmobile_take_screenshot to confirm the resultBefore using mobile-mcp, ensure a simulator or emulator is running:
iOS Simulator (macOS):
xcrun simctl list devices available
xcrun simctl boot "iPhone 16"
open -a Simulator
Android Emulator:
emulator -list-avds
emulator -avd <avd_name> &
Then call mobile_list_available_devices to confirm the device is visible.
| Tool | Purpose |
|---|---|
mobile_list_available_devices | List all available devices (physical + simulators) |
mobile_get_screen_size | Get screen dimensions in pixels |
mobile_set_orientation | Set portrait or landscape |
mobile_get_orientation | Get current orientation |
| Tool | Purpose |
|---|---|
mobile_launch_app | Launch app by bundle/package ID |
mobile_terminate_app | Stop a running app |
| Tool | Purpose |
|---|---|
mobile_list_elements_on_screen | Get UI hierarchy with coordinates |
mobile_take_screenshot | Take screenshot (returns image content) |
| Tool | Purpose |
|---|---|
mobile_click_on_screen_at_coordinates | Tap at x,y |
mobile_double_tap_on_screen | Double-tap at x,y |
mobile_long_press_on_screen_at_coordinates | Long press at x,y |
mobile_swipe_on_screen | Swipe up/down/left/right |
mobile_type_keys | Type text into focused element |
mobile_press_button | Press hardware button (HOME, BACK, VOLUME_UP, etc.) |
1. mobile_list_available_devices → find your device
2. mobile_launch_app("com.example.app") → start the app
3. mobile_list_elements_on_screen → see what's on screen
4. mobile_take_screenshot → visual confirmation
1. mobile_list_elements_on_screen → find the button and its coordinates
2. mobile_click_on_screen_at_coordinates → tap at the button's x,y
3. mobile_list_elements_on_screen → verify screen changed
1. mobile_list_elements_on_screen → find input fields
2. mobile_click_on_screen_at_coordinates → tap the input field to focus it
3. mobile_type_keys("user@example.com") → type the value
4. mobile_click_on_screen_at_coordinates → tap next field
5. mobile_type_keys("password123") → type next value
6. mobile_click_on_screen_at_coordinates → tap submit button
1. mobile_press_button("BACK") → Android back button
2. mobile_press_button("HOME") → Go to home screen
1. mobile_swipe_on_screen("up") → scroll down (swipe up)
2. mobile_list_elements_on_screen → check newly visible elements
1. mobile_launch_app("com.example.shop")
2. mobile_list_elements_on_screen → find search bar
3. mobile_click_on_screen_at_coordinates → tap search
4. mobile_type_keys("wireless headphones")
5. mobile_press_button("ENTER")
6. mobile_list_elements_on_screen → find results
7. mobile_click_on_screen_at_coordinates → tap first result
8. mobile_take_screenshot → verify product page
mobile_list_elements_on_screen to get accurate coordinates before tapping.mobile_take_screenshot returns the image inline for visual confirmation.mobile_get_screen_size if you need to calculate relative positions.