Reduck MCP
officialReduck MCP allows agents to discover, run and create browser automation scripts that serve as tools. Scripts run in your own Chrome, through our extension, which allows your agent to work where you are logged in — no credentials exposure, and same fingerprints so no bot detection.
What can you do with Reduck MCP?
- List available automation scripts — Ask your AI to call
list_scriptsto see which Reduck browser scripts are ready to use. - Run a script on a live website — Instruct your assistant to invoke
run_scriptto execute a browser task, like fetching weather data from a real site. - Set up remote MCP access — Configure your client to connect to Reduck over streamable HTTP at
https://mcp.reduck.aiwith OAuth browser sign-in. - Verify server connectivity — Have your assistant confirm the Reduck server is active by checking that both
list_scriptsandrun_scripttools are available.
Hosted MCP Server
npx add-mcp 'https://mcp.reduck.ai/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Reduck is a remote MCP server, so any client that speaks MCP over streamable HTTP can use it. There is nothing to install and no package to run.
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.
Let your agent do it
Most harnesses can add a server to their own config when asked. Paste this:
Install reduck MCP scoped to the user, which uses http transport at https://mcp.reduck.ai
Add the server by hand
If you are writing the config yourself, this is everything the client needs:
| Setting | Value |
|---|---|
| URL | https://mcp.reduck.ai |
| Transport | Streamable HTTP, not stdio and not SSE |
| Name | reduck |
| Scope | User, so every project sees it |
| Auth | OAuth. The client opens a browser on first use |
Reduck holds no API key for MCP. The client signs in through your browser and keeps the token it gets back. For a server-to-server caller that cannot open a browser, use an API key against the REST API instead.
Confirm it is connected
Restart the client, then ask it to list the tools it has. list_scripts and run_script are the two that say Reduck is live.
If it does not appear
- The client was not restarted after the config changed.
- The transport is set to stdio. A stdio client expects a command to launch, and Reduck is a URL.
- Sign-in never finished. The browser tab has to be completed before any tool call works.
Try it
Ask for something on a real site, and let the agent pick the script:
Use Reduck to get me the weather in Paris for the next two weeks.
Reduck finds a script for the site, runs it, and hands back the result. The script catalogue lists everything it can already do.