Add to ChromeYour logged-in Chrome browser becomes a programmable API. Call it from anywhere — Claude.ai (via MCP), backend code, CI/CD pipelines, Slack bots, or any HTTP client. One endpoint serves both the MCP protocol and direct HTTP requests. This controls YOUR Chrome with YOUR logged-in sessions, not cloud browsers.
Two Ways to Connect
Get your credentials from the MCP / Remote Browser Tools section in extension settings:
| Method | How | Use For |
|---|---|---|
| MCP URL | Copy the full URL → paste into Claude.ai or any MCP client | Claude.ai, Cursor, Cline, any MCP-compatible tool |
| API Key | Extract rtrvr_... from the URL → use as Bearer token | curl, scripts, backend code, CI/CD |
MCP URL format:
https://mcp.rtrvr.ai?apiKey=rtrvr_xxx&deviceId=abc123
API Key:
rtrvr_xxx (extracted from the URL)Quick Example — List Tabs (Free)
curl -X POST "https://mcp.rtrvr.ai" \
-H "Authorization: Bearer rtrvr_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"tool": "get_browser_tabs",
"params": { "filter": "all" }
}'Quick Example — AI-Powered (Credits)
curl -X POST "https://mcp.rtrvr.ai" \
-H "Authorization: Bearer rtrvr_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"tool": "planner",
"params": {
"user_input": "Go to ChatGPT, ask about top restaurants in SF, extract the response",
"tab_urls": ["https://chatgpt.com"],
"max_steps": 10
}
}'Free vs. Credit Tools
Free tools require no credits and are perfect for scripting with your own LLM provider. Credit tools leverage rtrvr.ai's custom prompts, integrations, and multi-step planning.
| Tier | Tools | Use Case |
|---|---|---|
| Free | get_browser_tabs, get_page_data, take_page_action | Direct browser control, scripting |
| Credit | planner (multi-step), act, extract, crawl | AI reasoning, complex workflows |
| Utility | list_devices, get_current_credits, list, check_results | Device management, billing, saved recordings / schedules |
Multi-Device Support
Install the extension on multiple Chrome profiles to control them independently. Each profile gets a unique deviceId. Omit deviceId to auto-select the most recently active browser.
- 01
Install extension on multiple Chrome profiles
- 02
Each gets a unique deviceId (visible in MCP URL)
- 03
Call list_devices to see all registered devices
- 04
Target a specific device: add "deviceId": "abc123" to your request body
Response Format
{
"success": true,
"data": { "tabs": [...], "tabCount": 5 },
"error": null,
"metadata": {
"tool": "get_browser_tabs",
"deviceId": "abc123",
"executionTime": 234,
"creditsUsed": 0,
"creditsRemaining": 10000
}
}Security Settings
Control which tools can be called remotely from the MCP / Remote Browser Tools settings:
- 01
Toggle entire tool families on/off (Free Tools, Credit Tools)
- 02
Fine-tune individual tool permissions
- 03
Disabled tools return clear error messages to the caller
- 04
Remote tools are enabled by default — review settings for your security needs
Troubleshooting
If you see "No online devices found" errors:
- 01
Refresh the extension: open/close the popup window
- 02
Rotate the API key from the dropdown menu in settings
- 03
Sign out and back in to reset device registration
- 04
Call {"tool": "list_devices"} to check device status