OpenClaw

OpenClaw reaches Reduck over streamable HTTP, and runs it through a local gateway of its own.

Before you start

You need a Reduck account, and a paired browser if you want scripts to run on your own Chrome. Both are in the quick start.

OpenClaw needs Node 20 or later, and a model provider of its own, and it ships with none.

npm i -g openclaw

Add the server

openclaw mcp add reduck \
  --url https://mcp.reduck.ai \
  --auth oauth \
  --transport streamable-http

Then authorize. This opens your browser; approve the request and the CLI picks up the callback.

openclaw mcp login reduck

Confirm it is connected

openclaw mcp probe

A working connection lists Reduck’s tools, about thirty of them.

The OAuth flow signs you in as whichever Reduck account your browser is already using, which is not always the one you meant. Ask your agent to call whoami and read the handle back before you rely on it.

Settings worth changing

OpenClaw asks for approval before each tool call, which interrupts a script mid-run. To let Reduck run unattended:

openclaw mcp configure reduck --approval auto

OpenClaw reaches the server through a local gateway. Install it as a daemon to keep it alive after the terminal closes:

openclaw onboard --install-daemon

If it does not appear

The transport was left out, so the connection failed as SSE. See the warning above. The error names a status code, not the flag that caused it.
Node is older than 20.
Sign-in never finished. openclaw mcp login reduck has to complete in the browser before any tool call works.

Try it

Ask for something on a real site, and let the agent pick the script:

Reduck finds a script for the site, runs it, and hands back the result. The script catalogue lists everything it can already do.