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
| Tool | REST Equivalent | Auth | Description |
|---|---|---|---|
| create_account | POST /accounts | No | Register a consumer account. Returns API key. |
| create_node | POST /nodes | No | Register an operator node. Returns API key + node ID. |
| auth_challenge | POST /auth/challenge | No | Request wallet challenge for key recovery. Step 1 of 2. |
| auth_verify | POST /auth/verify | No | Submit signed challenge to recover API key. Step 2 of 2. |
| get_balance | GET /accounts/me | api_key | Check credit balance, total spent, total earned. |
| submit_task | POST /tasks | api_key | Submit a browser task for execution. |
| list_tasks | GET /tasks | api_key | List tasks with optional status filter and pagination. |
| get_task | GET /tasks/:id | api_key | Poll task status and retrieve results. |
| buy_credits | POST /accounts/credits/stripe | api_key | Create Stripe checkout session to buy credits with card. |
| add_test_credits | POST /accounts/credits/alternative | api_key | Add 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.01OUTPUT
task_id: "uuid"
status: "queued"
estimate: {
tier: "real"
estimated_steps: 5
estimated_cost: 100 // $1.00
}
max_budget: 300 // $3.00agent 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
| MCP | REST API | |
|---|---|---|
| Best for | AI agents with MCP support | Any HTTP client |
| Setup | One JSON config line | API key + HTTP calls |
| Discovery | Agent sees tools automatically | Developer reads docs |
| Use case | Claude, OpenClaw, MCP-enabled agents | SDKs, 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 →