Phone tools use 0 API credits. The MCP connection must use the same Appeeky account that is signed in to Appeeky Desktop.
Tools
phone_devices, phone_observe and phone_list_apps are marked as read-only tools.
How an assistant uses them
phone_observereturns the element list as text and the screenshot as an image.- The assistant picks an element by its number and acts, for example with
phone_tap. - Every action returns a fresh observation, so the assistant rarely needs to call
phone_observetwice in a row.
APPROVAL_DENIED: and the assistant should stop and ask you what to do. See Approvals and safety.
Common parameters
Tools that take a target accept either
element, or both x and y:
phone_devices
Lists the phones that are online. No parameters. Returns the devices as JSON:id, name, platform, driver, screen, and serial when known. When no phone is online it returns No phones connected. with the setup problems your Mac reported.
phone_observe
Returns two parts: a text list of the elements, one per line as
[3] "Send" (button, clickable) at 512,1180, and the screenshot as an image.
phone_tap
Returns the new observation, or
tap: done with observe: false.
phone_long_press
phone_swipe
Drags from one place to another. For plain scrolling, usephone_scroll.
phone_scroll
phone_type
Types into the focused text field. Tap the field first. Line breaks press Enter.phone_key
Android supports all of them. iPhone supports
home, enter, delete, lock, volume_up and volume_down.
phone_open_app
phone_list_apps
Returns the apps as JSON, each with
id and name.
phone_push_media
Copies an image or video into the phone’s gallery so apps can pick it, for example when posting. Works on Android.
Pass
url or path. Returns Copied to <path on the phone>. It is in the gallery now.
Errors
A failed tool call returns an error result with a text message. Policy errors start with a code:
Other messages describe the problem in plain words, for example
No phones are online. See Troubleshooting.

