App Logo

Let OpenClaw work in your own browser

OpenClaw answers from your chat app, day and night.
Reduck lets it act on the sites you are signed into, in the Chrome on your desk.

Set up Reduck now

  1. Create your Reduck account
  2. Install our Chrome extension
  3. Add the Reduck MCP server
    openclaw mcp add reduck \ --url https://mcp.reduck.ai \ --auth oauth \ --transport streamable-http
  4. Authorize
    openclaw mcp login reduck

    Opens your browser. Approve the Reduck authorization, and the CLI picks up the callback.

Running another agent in the same terminal? Hermes and Claude Code reach the same server at https://mcp.reduck.ai, and read the same account and the same scripts.

OpenClaw already reaches you anywhere.
Reduck gives it the web.

OpenClaw without Reduck
It drives a page it cannot see A headless browser hands back a wall of HTML and no picture. OpenClaw guesses which control it just pressed, and learns whether it was right from whatever comes back.
Your logins end up in the gateway To act as you on a site, it needs your session. So the password goes into the process that runs unattended, and it stays there between runs.
The routine lives on one machine A browser routine that finally works is a file on the host that wrote it. Move the gateway, or run a second one, and it does not come along.
OpenClaw with Reduck
It calls a script someone proved Each site has a named script with a declared input and a declared output. OpenClaw picks one and reads the result — there is no page left to interpret.
Your sessions stay in your Chrome The extension pairs the browser you already use. The script runs in that profile, so the cookies never reach the gateway and there is no password for it to hold.
The script belongs to the account It is saved under your handle rather than on a host. A second gateway, a new laptop or a teammate reaches the same one through the same MCP server.

One server, every site it has to touch.

OpenClaw
01

One entry in the OpenClaw config, and every site in the catalogue answers. The site after that costs you no new skill to write, no dependency on the gateway host, and no restart.

02

The Chrome that opens the page is the one on your desk, paired to your account. OpenClaw sends arguments and reads results, so a session you hold never passes through the gateway.

03

What comes back is typed JSON against the schema the script declares. A run left alone overnight can branch on a field instead of on a guess about a page.

One message, four scripts, three replies sent

What OpenClaw does with the tools once Reduck is connected.

Prompt

Three people asked me this week when I am free. Read the WhatsApp threads I have not answered, find a slot that suits each of them, and reply.

Automation
  1. get_inbox Lists the WhatsApp threads still waiting on a reply
  2. get_conversation Reads each thread in full, not only the last message
  3. list_events Checks the calendar for the days it can offer
  4. send_message Sends the answer from your own account
Output

Three answers sent, each naming a slot the calendar says is open — plus the threads it chose to leave for you, and why.

What people hand it

Official scripts, already written and already tested.

Answer WhatsApp without opening it

OpenClaw reads the threads still waiting on you, drafts each reply with the conversation in front of it, and sends from your own account. No Business API to apply for.

Learn more

Book the appointment you keep postponing

Finding practitioners is easy; finding one free when you are is not. OpenClaw checks the calendars and comes back only with the slots that fit yours.

Learn more

Close the month without the invoice hunt

Each vendor hides its invoices behind its own login and its own download button. OpenClaw walks the list on the last day of the month and tells you which one still owes you a PDF.

Learn more

Buy on the evidence, not the stars

A rating hides the thing that will annoy you in a month. OpenClaw opens the listings worth opening and reads what recent buyers wrote before it names one.

Learn more

Watch a brand on Instagram

Set it once and OpenClaw reports back on its own: what the account posted, what landed, and what the numbers did since the last time it looked.

Learn more

Keep up with a topic on X

Name a subject and OpenClaw brings back the posts moving it and the accounts behind them, in the chat you already read, without an X account or an API key.

Learn more

Where the automation runs

Your own Chrome for anything that needs your account; ours for everything else.

In your browser Default Run locally with Reduck Chrome extension
In the cloud On demand Run in Reduck cloud browser
Run cost Free up to 100 scripts Free up to ≈ 100 scripts (1h)
Site covers Every authenticated site Auth-based sites coming soon with connectors
Always-on Needs your device on Independent of your hardware
Parallel runs Limited by your Chrome (usually up to 5) Many sessions in parallel (up to 99)
Geo control Your own location Residential proxies, any country (not antibot bypass)
In your browser Default Run locally with Reduck Chrome extension
Cost & access
Run cost Free up to 100 scripts
Site covers Every authenticated site
Scale & reach
Always-on Needs your device on
Parallel runs Limited by your Chrome (usually up to 5)
Geo control Your own location
In the cloud On demand Run in Reduck cloud browser
Cost & access
Run cost Free up to ≈ 100 scripts (1h)
Site covers Auth-based sites coming soon with connectors
Scale & reach
Always-on Independent of your hardware
Parallel runs Many sessions in parallel (up to 99)
Geo control Residential proxies, any country (not antibot bypass)

Pick your plan

Start free, scale up as you run more.

Starter

Free forever

Discover Reduck: run and build scripts with limited access.


  • Run up to 100 scripts/month in your browser or in the cloud
  • 1 hour of cloud browser time/month
  • Build unlimited scripts including 3 private ones
  • Community support on Discord

Max

$100 per month

Unlimited usage for power users.


  • All of Pro, scaled up
  • Run unlimited scripts/month in your browser
  • 50 hours of cloud browser time/month
  • Project repositories with up to 25 people each
  • Priority support

Enterprise

Custom for your org

Scale mission-critical automations across your org.


  • Everything in Max, plus
  • Shared access cookies to third-party apps
  • Central observability, billing, logs & admin panel
  • Unlimited users
  • Dedicated infrastructure: your region or self-hosted, enterprise-grade compliance
  • Premium support with a forward-deployed engineer

FAQ

The OAuth flow uses whichever Reduck account the browser it opened is signed into, which is not always the one you meant. Ask OpenClaw to call whoami and read the handle back before you leave an unattended job running against it. Signing out of the wrong account and repeating openclaw mcp login reduck is enough to correct it.
Yes. openclaw mcp configure reduck --approval auto approves the Reduck server once instead of once per call, which is what an unattended job needs — otherwise a run that calls twenty scripts stops twenty times. Scoping it to that one server leaves your approval rules for everything else alone.
OpenClaw works through a local Gateway, so it has to be alive for a scheduled job to fire. openclaw onboard --install-daemon keeps it up after you close the terminal. Reduck adds nothing to that: the MCP connection is re-established with the Gateway, and the browser work happens on your machine either way.
No, and that is the point of pairing a browser. The Chrome extension connects the profile where you are already signed in, and the script runs there. OpenClaw sends arguments and reads a JSON result; the cookies never leave your machine and there is nothing for the gateway to store.
A script that needs your account needs your browser, so that run waits. Everything that does not — a public search, a listing, a price — can run on a Reduck-hosted browser instead, which is always up. You choose per run, and a job can mix the two.
Tell OpenClaw to write one. The same MCP server carries the authoring tools, so it builds the script against the live page, runs it to check the output, and saves it under your handle. From then on it is a call like any other, and a site change can be repaired the same way.

OpenClaw is already listening, give it a browser to work in