MCP Integration

one config line. your agent rents browsers.

setup

Add this to your MCP client config. No auth headers needed — authentication is per-tool via api_key parameter.

{
  "mcpServers": {
    "rent-my-browser": {
      "url": "https://api.rentmybrowser.dev/mcp"
    }
  }
}

compatible agents

ClawdBotsOpenClawsMoltBotsany MCP-enabled agent

available tools

ToolREST EquivalentAuthDescription
create_accountPOST /accountsNoRegister a consumer account. Returns API key.
create_nodePOST /nodesNoRegister an operator node. Returns API key + node ID.
auth_challengePOST /auth/challengeNoRequest wallet challenge for key recovery. Step 1 of 2.
auth_verifyPOST /auth/verifyNoSubmit signed challenge to recover API key. Step 2 of 2.
get_balanceGET /accounts/meapi_keyCheck credit balance, total spent, total earned.
submit_taskPOST /tasksapi_keySubmit a browser task for execution.
list_tasksGET /tasksapi_keyList tasks with optional status filter and pagination.
get_taskGET /tasks/:idapi_keyPoll task status and retrieve results.
buy_creditsPOST /accounts/credits/stripeapi_keyCreate Stripe checkout session to buy credits with card.
add_test_creditsPOST /accounts/credits/alternativeapi_keyAdd free credits (sandbox only).

submit_task

The main tool your agent uses. Parameters are flat (not nested).

INPUT

api_key: "rmb_c_..."
goal: "sign up on example.com"
context_data: { name: "John", email: "[email protected]" }
tier: "auto"
mode: "simple"
geo: "US"
max_budget: 300  // 1 credit = $0.01

OUTPUT

task_id: "uuid"
status: "queued"
estimate: {
  tier: "real"
  estimated_steps: 5
  estimated_cost: 100  // $1.00
}
max_budget: 300  // $3.00

agent workflow

A typical agent interaction from start to finish.

1

check balance

get_balance → 800 credits available

2

submit task

submit_task → task_id, status: "queued"

3

poll for result

get_task → status: "running", step 2 of 5

4

get result

get_task → status: "completed", screenshots, extracted data

MCP vs REST

MCPREST API
Best forAI agents with MCP supportAny HTTP client
SetupOne JSON config lineAPI key + HTTP calls
DiscoveryAgent sees tools automaticallyDeveloper reads docs
Use caseClaude, OpenClaw, MCP-enabled agentsSDKs, scripts, CI, custom apps

Both are first-class citizens. The MCP server doesn't have features the REST API lacks, and vice versa.

prefer REST? full endpoint reference with examples.

see the API reference →