Ramus Android

dev.ramusPublished by ramus.devOfficial publisherv0.2.0Updated Oct 24, 2026

Disposable cloud Android emulators for coding agents: run an APK or PR build, tap, type, screenshot.

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Gives coding agents a disposable cloud Android emulator to run an APK or PR build, then tap, type, screenshot and read logs.

What you can do
  • Start an Android emulator session from a demo app or pull request
  • Inspect the UI tree and act on referenced elements: tap, type, press, wait
  • Capture screenshots and read device logs
  • Share the session so a person can watch or take over in the browser
When to use it
Useful when an agent needs to actually exercise an Android app it is building or reviewing — smoke-testing a PR build, reproducing a UI bug, or verifying a fix on a real emulator instead of guessing from code.
Requirements
Remote Streamable HTTP endpoint; no local process. Needs a Ramus account and a Ramus API key sent as an Authorization bearer token, or a 60-minute CLI trial that needs no account. Local APK upload and the dev loop require the separate CLI.
Before you install
The Authorization header carries a Ramus API key, so keep it out of shared configs. The agent can drive a live device and start sessions, which may consume account quota or cost once alpha ends. Only test apps you build or are authorized to test; device activity and logs go to the hosted Ramus service.

Installation

In SourceWeft

  1. Open Ramus Android 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/dev.ramus%2Fandroid/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": {
    "ramus-android": {
      "type": "http",
      "url": "https://api.ramus.dev/api/mcp"
    }
  }
}

README

Ramus android-use

Android-use for coding agents, powered by Ramus. Give Claude Code, Codex, Cursor, Gemini CLI or any agent with a shell a disposable cloud Android emulator it can see, tap, type on, screenshot and read logs from, then watch or take over in your browser.

This plugin connects to the Ramus hosted service. It needs a Ramus account (free during alpha) or a 60-minute CLI trial.

Install

Claude Code, as a plugin (the android-use skill plus the Ramus MCP server; you are asked for an optional API key):

/plugin marketplace add ramus-dev/android-use/plugin install ramus@ramus

Cursor, Codex, GitHub Copilot, Kiro and other Agent Plugins clients: install this repository as a plugin (plugin.json at the root).

Any agent that supports skills, via the skills CLI:

sh
npx skills add ramus-dev/android-use

Claude Code, by hand: copy skills/android-use/SKILL.md to .claude/skills/android-use/SKILL.md.

Gemini CLI, as an extension (bundles the skill and the Ramus MCP server):

sh
gemini extensions install https://github.com/ramus-dev/android-use

Any MCP client (Cline, Claude Desktop, Cursor, Windsurf, VS Code), as a remote server. Streamable HTTP, no local process:

json
{  "mcpServers": {    "ramus": {      "url": "https://api.ramus.dev/api/mcp",      "headers": { "Authorization": "Bearer <RAMUS_API_KEY>" }    }  }}

Create the key at https://ramus.dev/settings. The server exposes android_* tools (start a session from a demo app or pull request, snapshot the UI tree, tap, type, press, wait, screenshot, logs, share); list them with tools/list. Local APK upload and the dev loop need the CLI below.

The trial needs no account:

sh
npx ramus-cli trialnpx ramus-cli session start --apk app-debug.apk --wait

ChatGPT and Codex (OpenAI plugin)

The same repository is the OpenAI plugin package: plugin.json carries the directory listing under extensions.com.openai, mcp.json points at the remote MCP server (people connect by signing in to Ramus; no API key), and the skills declare where they run in skills/*/agents/openai.yaml. The OpenAI package ships only android-mcp (MCP tools, ChatGPT and Codex): android-use drives the CLI through the shell, which OpenAI's skill scan flags, so the OpenAI packaging workflow leaves it out.

Maintainers can build the upload for the OpenAI plugin portal ("With MCP" path) using the manual Package OpenAI plugin workflow:

  1. Open Actions → Package OpenAI plugin → Run workflow and choose the branch or tag to package.
  2. After it succeeds, download the ramus-openai-upload artifact from the run and unpack it.
  3. Upload the enclosed ramus-openai-plugin.zip to the OpenAI plugin portal.

The workflow checks the listing against OpenAI's limits and packages only the OpenAI manifest, MCP configuration, license, logo and android-mcp skill. It runs only in GitHub Actions when a maintainer requests an upload; the installed plugin does not run the packaging code.

How it works

The device is a real Android emulator running stock Google images on the Ramus fleet, streamed over WebRTC. The skill teaches the agent the observe, act, verify loop: read a snapshot of the UI tree, act on a referenced element, then check the result before moving on.

Links

Android only. Free during alpha. For testing apps you build or are authorized to test.

SKILL.md is generated from the Ramus product contracts; the canonical copy is served at https://ramus.dev/skill.md.

Source: README.md at commit c70c2f7

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.2.0LatestSep 25, 2026

Score

85% 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
  • License10 pts