Skip to content

Connect an agent (MCP)

Ramus is a remote MCP server at https://api.ramus.dev/api/mcp. Add it to your agent once and sign in with your Ramus account; there is no API key to paste. Your agent can then start an Android device, install a build, read the screen, tap and type, and send you a link to watch.

Pick your client below. Each one asks you to sign in the first time it uses Ramus.

Claude Code

claude mcp add --transport http ramus https://api.ramus.dev/api/mcp

Then run /mcp in Claude Code, choose ramus and sign in with Ramus in the browser window that opens.

Codex

codex mcp add ramus --url https://api.ramus.dev/api/mcp

Codex opens your browser to sign in with Ramus. To sign in again later, run codex mcp login ramus.

Cursor

Add Ramus to ~/.cursor/mcp.json, or to .cursor/mcp.json in one project:

{ "mcpServers": { "ramus": { "url": "https://api.ramus.dev/api/mcp" } } }

Save the file, then sign in with Ramus when Cursor asks.

ChatGPT

Open Ramus in ChatGPT, choose Connect, then sign in. Attach an APK to a message, or ask for a pull request's preview, and the running device appears in the conversation.

Other MCP clients

Any client that supports Streamable HTTP can use the same URL. Clients that support MCP sign-in (OAuth) connect with your Ramus account. Others send an API key from Agents as a bearer token (Claude Code: claude mcp add with --header); keep it in the client's settings, never in chat.

Cloud agents

Cloud coding agents such as Codex cloud, Cursor background agents and Claude Code on the web do not document KVM or Android emulator support, so give them a Ramus device instead:

  1. Create an API key on Agents.
  2. Add it to the agent's environment as RAMUS_API_KEY, using the platform's secrets setting rather than a file in the repository.
  3. Add one line to the repository's AGENTS.md or CLAUDE.md:
Test Android changes on Ramus: https://ramus.dev/agents.md

The agent then drives the device with the CLI. It needs network access to npm and ramus.dev; on Claude Code on the web, the default "Trusted" network level does not include ramus.dev, so allow it.

What your agent can do

  • Start a device from a pull request or an app Ramus already has, or install a new build on a running device.
  • Read the screen as elements, then tap, type, swipe and wait for the result.
  • Take screenshots and read the device log.
  • Send you a watch link, so you can follow along. It is view-only; to take control, open your device page, or have the agent make a link that lets someone use the device.
  • Make a link that gives each person their own device of your app, then read the notes they send. It asks you before it changes code because of one, and replies once it has.

An agent with a shell uploads an APK from your machine with android_upload_apk, which hands it a one-time curl command. The adb tunnel and ramus dev need the CLI; an agent with a shell can use both. Sessions your agent starts use your plan's minutes and device limit; see Plans and minutes. The full tool list and limits are in the agent reference.