Rtrvr.ai – AI Web Agent Turns Your Browser into an MCP Endpoint

TL;DR

TL;DR: Rtrvr.ai is a Chrome Extension that turns your browser into a remote MCP server, allowing any AI agent (Claude, Cursor, etc.) to drive web tasks on your behalf via a single MCP URL — no context switching required.

What Is Rtrvr.ai?

Rtrvr.ai started as an in-browser AI agent. After hitting architectural limits, the team rebuilt it around a core insight: expose the Chrome Extension itself as a Remote MCP server. This turns the user’s browser into a controllable, sandboxed endpoint that any AI can talk to via a copy/paste MCP URL.

The product was launched on HN in November 2025 by Arjun Chint, one of the founders.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: rtrvr.ai
• Source repository: none publicly listed — Chrome Extension only
• Chrome Extension: chromewebstore.google.com/detail/rtrvrai-ai-web-agent
• License: proprietary (no open-source license found)
• HN launch thread: news.ycombinator.com/item?id=45898043
• OpenAPI spec: rtrvr.ai/openapi/a2w.yaml

How It Works

Rtrvr.ai installs as a Chrome Extension. Once active, it registers the browser as a remote MCP endpoint. Other AI agents connect to it via the MCP protocol.

The key architecture move is that the browser itself becomes the execution environment — sandboxed, with access to the user’s logged-in sessions, cookies, and web context.

The MCP Connection Flow

Claude (or any MCP client)
    │
    │  MCP over HTTP
    ▼
Rtrvr.ai Chrome Extension
    │  (browser context, cookies, logged-in state)
    ▼
Web (as the agent's "hands")

The MCP URL for your browser is generated by the extension and looks like:

https://agent.rtrvr.ai/v1/a2w/runs?url=[target]&prompt=[task]&execution=cloud

Agents pass a target URL and a natural-language instruction. Rtrvr executes the task in the cloud browser (or optionally in your local browser via execution=browser).

BYO-Subscription Model

Because Claude drives the action, you use your existing Claude subscription for basic tasks. Rtrvr.ai provides the secure execution rails and browser context. For complex multi-step workflows, you can upgrade to Rtrvr’s own agent.

Setup Workflow

Step 1: Install the Chrome Extension

Visit the Chrome Web Store page and click Add to Chrome:

# Not installable via CLI — open in browser
open "https://chromewebstore.google.com/detail/rtrvrai-ai-web-agent/jldogdgepmcedfdhgnmclgemehfhpomg"

Step 2: Configure Your MCP Client

Once installed, open the extension to get your browser’s MCP endpoint URL. In Claude (or any MCP-compatible client), add a new MCP server:

{
  "mcpServers": {
    "rtrvr-browser": {
      "command": "fetch",
      "url": "https://agent.rtrvr.ai/v1/a2w/runs?url=https://example.com&prompt=scrape+prices&execution=cloud&wait=25&format=markdown"
    }
  }
}

Step 3: Run a Task

Tell Claude to perform a web task using your browser:

Can you file that Jira ticket for me? The link is in my open tabs.

Claude issues an MCP call to Rtrvr, which executes the task in your browser context. You stay in the chat; Rtrvr handles the web interaction.

Key Features

• Remote MCP server baked into Chrome — no extra infrastructure
• Browser as a shared execution layer — any AI agent can use it
• BYO subscription — power basic tasks with your existing AI plan
• Agentic Web vision — multiple specialized agents collaborating via browser context
• Cloud or local execution — execution=cloud runs in Rover’s hosted browser; execution=browser drives your own

Deeper Analysis

What Makes This Different

Most browser automation tools require you to choose between a hosted agent (no access to your logged-in sessions) or a local setup (complex infra). Rtrvr bridges the gap by using your actual Chrome browser — with all your cookies and session state — as the execution target, exposed over MCP.

The “agentic web” vision is interesting: rather than one monolithic agent, a network of specialized agents all sharing a common browser layer. Whether this architecture wins long-term is an open question, but the team is already in talks with other agent platforms.

Current Limitations

• Requires the Chrome Extension to be running (and Chrome to be open)
• Cloud execution is a separate hosted service with its own pricing
• No self-hosted option as of this writing
• The agent card and OpenAPI spec exist, but actual API documentation for third-party integration is minimal

Practical Evaluation Checklist

• [x] Chrome Extension installs without dev mode
• [x] MCP endpoint is reachable at agent.rtrvr.ai/v1/a2w/runs
• [x] Extension exposes an OpenAPI spec at rtrvr.ai/openapi/a2w.yaml
• [x] Supports both cloud and local browser execution modes
• [ ] Open-source license — none found; proprietary only
• [ ] Self-hosted option available — no

Security Notes

Exposing your browser as an MCP endpoint means any agent with the URL can issue commands in your browser context. Consider:

• Scope limitations: Only share the MCP URL with agents you trust
• Session isolation: The extension runs in your Chrome profile — agents operate with your actual logged-in state on sites
• Cloud execution: Uses Rover’s hosted browser instead of yours, providing a sandbox layer

FAQ

Q: Do I need a Rtrvr.ai subscription to use it? A: Basic tasks work with your own AI subscription (Claude, etc.) driving the agent. For complex multi-step workflows, Rtrvr offers paid plans with more capable agents.

Q: Is my browser data stored anywhere? A: Cloud execution runs in Rover’s hosted browser. Local execution uses your own Chrome profile directly. Review Rtrvr’s privacy policy for specifics.

Q: What AI agents support MCP and can drive Rtrvr? A: Any agent that implements the MCP client spec — including Claude (via the MCP integration), Cursor, and other MCP-compatible tools.

Q: Can I self-host this? A: No self-hosted option is available as of this writing. The infrastructure runs on Rtrvr’s servers.

Conclusion

Rtrvr.ai’s architecture is a clean answer to a real problem: how do you give an AI agent web presence without building yet another browser automation stack? By exposing Chrome itself as an MCP endpoint, it leverages the browser’s existing capabilities and your logged-in context. The BYO-subscription model is also clever — users pay for the brain (their existing AI plan) while Rtrvr provides the execution rails.

If you want your AI agent to actually touch the web without context-switching, the Chrome Extension is worth installing. Watch this space — the “agentic web” vision is early but directionally interesting.

Project page: rtrvr.ai | Chrome Extension: Add from Web Store