rtrvr.ai
All use cases

MCP

Bring the live page into your assistant.

Connect through MCP so Claude Code, Codex, or another client can read or act on the signed-in tab you select.

BEST FORDevelopers and technical teams connecting browser context to an MCP client.

WHAT YOU GET

Current page context inside your assistant

  • 01The state of the selected tab
  • 02Structured facts returned to the client
  • 03Browser actions only when the request calls for them

COPY A START

Use a prompt. Make it yours.

Replace the examples with your pages, rules, and approval point. rtrvr will work from the request you give it.

QUICK START

Read the dashboard in my current tab, compare this month with last month, and explain the three largest changes with the source values.

MORE SPECIFIC

Inspect the signed-in page I have selected. Return its current state, the records that need attention, and the next browser action you recommend.

HOW THE RUN WORKS

Start small. Check the result.

Tell Retriever AI which pages to use, what to return, and where to pause. Review a small sample before expanding the task.

  1. 01

    Connect the client

    Authorize the rtrvr MCP server from the assistant you use.

  2. 02

    Choose the browser

    Select which browser and tabs may take part in the request.

  3. 03

    Ask with context

    The client can retrieve facts or request an action through the same connection.

WHY THIS FITS

OAuth connects the MCP client without putting an API key in the conversation.

WHERE TO RUN IT

Pick the fastest way to start.

Use Chrome for sites you’re already signed into. Use Cloud for a separate browser, or the API for tasks from your own tools. Schedules require a paid plan.

01

MCP setup

Connect your assistant to rtrvr and the selected browser.

MCP setup
02

Add to Chrome

Make your signed-in browser session available to the connection.

Add to Chrome

RUN YOUR VERSION

Put this work on repeat.

Copy a prompt, point rtrvr at your pages, and keep the final approval where it belongs.