run_web_automationLABSCO SUMMARY
Streaming progress is the difference between a long automation you can supervise and one you have to trust blindly.
Browser automation runs for minutes and fails in the middle for mundane reasons — a consent banner, a changed label, a login that expired. Without progress you learn that at the end; with it you can stop a run that has gone somewhere unintended. The local proxy is a thoughtful fallback rather than a downgrade: same hosted agent, different transport, for clients that have not caught up to remote servers.
What it is
TinyFish runs a web automation agent. You describe the task rather than scripting the steps, and the run streams its progress back as it goes.
What you get
The automation tool itself, with progress streamed during a run. The tools and resources are served by the hosted endpoint rather than fixed in a package, so the surface can change without you reinstalling anything.
Requirements
A client that speaks streamable HTTP can connect directly and authorise over OAuth. For clients that cannot, they publish a local proxy that bridges to the hosted endpoint using an API key.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Automating a site without scripting it
Describe the task instead of writing the steps.
02
Watching a long run
Progress streams back rather than arriving at the end.
03
Connecting from a stdio-only client
The published local proxy bridges to the same hosted agent.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth, built into the hosted endpoint; the local proxy route uses an API key instead
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://agent.tinyfish.ai/mcpRequirements
- OAuth, built into the hosted endpoint; the local proxy route uses an API key instead
