Mobilerun

io.github.droidrunPublished by GitHub account droidrunv1.1.0Updated Nov 5, 2026

Let AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.

VerifiedStreamable HTTPWeb executableBrowser Automation

Overview

AI-generated overview

Mobilerun Cloud lets an AI assistant control Android and iOS devices remotely — screen, input, apps and workflows — through a hosted MCP endpoint.

What you can do
  • Inspect and interact with the screen of a connected Android or iOS device
  • Send input such as taps, typing and gestures
  • Launch and manage apps on the device
  • Run and manage device workflows on Mobilerun Cloud
When to use it
Useful when an assistant needs to operate real or cloud-hosted mobile devices: driving app flows, testing mobile UI, or automating tasks that only exist on Android or iOS.
Requirements
A remote MCP endpoint at cloud.mobilerun.ai over streamable HTTP. OAuth authentication is required; CI and headless clients can instead send an API key from cloud.mobilerun.ai in the Authorization header. Devices must be available in the Mobilerun Cloud account.
Before you install
The server controls real mobile devices, so assistant actions can tap, type, install or change things on them and in the apps they hold. Access is granted through OAuth or an API key sent in the Authorization header; treat that key as a secret. Device screens and app data are handled by a third-party cloud service.

Installation

In SourceWeft

  1. Open Mobilerun 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.github.droidrun%2Fmobilerun/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": {
    "mobilerun": {
      "type": "http",
      "url": "https://cloud.mobilerun.ai/api/mcp"
    }
  }
}

README

This repository has no README.

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

2
  1. v1.1.0LatestOct 29, 2026
  2. v1.0.0Sep 16, 2026

Score

70% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts