Invi Labs: control real iPhones

io.invilabsPublished by invilabs.ioOfficial publisherv0.1.13Updated Oct 30, 2026

Let your AI agent control real iPhones: screenshots, tap, swipe, type and open apps.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

Remote MCP server that lets an AI assistant control real iPhones: take screenshots, tap, swipe, type and open apps.

What you can do
  • Take screenshots of a real iPhone screen
  • Tap and swipe on the device
  • Type text into the device
  • Open apps on the device
When to use it
Useful when an assistant needs to operate or inspect a physical iPhone rather than a simulated one, for example to walk through an app flow, check what is on screen, or drive a device hands-off.
Requirements
A remote endpoint at api.invilabs.io over streamable HTTP; no local package. An Invi Labs API key sent as a Bearer token in the Authorization header, created in the Invi Labs panel under Resources → AI agents (MCP). Network access to the service.
Before you install
The API key in the Authorization header is a secret and grants control of your devices. The assistant can tap, swipe, type and open apps on a real phone, so actions change device state and may affect accounts or data on it. Device activity is handled by the third-party Invi Labs service.

Installation

In SourceWeft

  1. Open Invi Labs: control real iPhones in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.invilabs%2Fiphone/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "invi-labs-control-real-iphones": {
      "type": "http",
      "url": "https://api.invilabs.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.13LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.