DeviceMirror
A workspace for your devices

Your devices.
Your agents.
Anywhere.

See your phone, take control, and let your agents get things done. One secure connection for live video, MCP, and your own code.

Connect your first device Explore the API

Start with two devices. Try the simulator without a phone.

◉ Live WebRTC video⌘ Standard MCP⌥ Open HTTP API▣ Your devices, your access
From connection to action

A small setup.
A much bigger workspace.

Connect once, then choose how you work. In your browser, through an agent, or with an API call.

01 / CONNECT

Bring your own devices.

Register a device in your workspace and connect its local bridge. No phone nearby? Start a clearly labeled simulated device.

02 / SEE

A real view, from anywhere.

Open a live WebRTC session to see what is happening. Switch between devices and capture a screenshot when you need one.

03 / ACT

Make your next move.

Tap, swipe, and type from the console. Or create a scoped credential and connect an MCP client or your own application.

Made for the way you work

One device. Many possibilities.

A shared foundation for people, agents, and software that need a phone within reach.

Give your agent eyes.

Let a compatible MCP client inspect a screenshot and send a precise action, with access restricted to the devices you choose.

Keep your devices close.

Use a single console for a multi-device workspace. See connection status, open live views, and control each screen independently.

Build your own workflow.

Use the same HTTP API for device discovery, screenshots, actions, and video sessions. Start small and connect it to your tools.

Built to connect

Your favorite agent.
Your own code.
The same devices.

Use standard MCP over HTTPS or a straightforward HTTP API. Scoped, revocable credentials keep control in your hands.

Connect an MCP client ↗Read the API docs ↗
device-mirror / first action● ● ● 
# See your connected devices
curl https://device-mirror.jiulong.hu/v1/devices \
  -H "Authorization: Bearer $DM_API_KEY"

# Make your next move
curl -X POST "$DM_URL/v1/devices/$ID/actions" \
  -H "Authorization: Bearer $DM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"tap","x":195,"y":422}'
Room to get started

Start small. Connect more.

Try the full connection workflow with a free workspace.
Paid subscriptions are currently available in Stripe sandbox only.

Free GET STARTED
$0 / month

For exploring a connected workspace with your own devices or a simulator.

  • 2 registered devices
  • 3,000 operations per month
  • 60 video minutes per month
  • HTTP API and MCP access
  • Scoped, revocable credentials
Create your workspace →
Pro STRIPE SANDBOX
$19 / month · test mode

For testing larger workspaces and the complete subscription flow. No live payments.

  • 10 registered devices
  • 100,000 operations per month
  • 1,000 video minutes per month
  • Everything in Free
  • Hosted Checkout and customer portal
Explore Pro in sandbox →

Simulated devices use the same permissions and resource limits as physical connections.
Model access requires server configuration. Real-device support depends on the local bridge.

A closer connection starts here.

Bring a device, connect an agent, or try the simulator.

Open your workspace