Claude TinyFish connectorWhat Claude can do in your TinyFish account.
The Claude TinyFish connector exposes 23 tools: 9 read, 6 write, 8 undocumented. Below: what Claude can read on the web, what the browser agent does in your name, what it costs, and the tools whose purpose nobody publishes.
Verified Trustpilot reviews · AI, automation & growth agency
Why hand your web chores to Claude and TinyFish
TinyFish gives Claude a cloud browser and a web agent. In practice you ask for a search, a heavy page to be read, or a run of clicks on a site, and Claude handles it through TinyFish. Per the official description, the agent runs in a remote Chrome browser and returns its results as structured JSON.
Search and read. search returns structured web results with titles, snippets and URLs. fetch_content pulls clean content from one to ten pages, including ones that need JavaScript to render.
Put an agent to work. run_web_automation carries out a multi-step task on a site from a URL and a plain-English goal: clicking, navigating, filling forms, logging in. Its sibling run_web_automation_async hands back control right away for long jobs, and get_run lets you check the outcome.
Watch the spend. get_wallet shows your TinyFish wallet balance and the rates that apply.
Now what the connector doesn't do. Topping up the wallet happens in the dashboard, not from Claude. The agent and the browser both draw on that balance. Eight tools on the sheet aren't described anywhere. And nothing starts on its own: Claude calls these tools while it answers you. A job that fires on a schedule is an automation tool's job, a different trade; the Integrations hub covers that side.
The jargon, in one minute
Five terms you'll meet while connecting TinyFish.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own, and the directory lists them by name.
- Authorization
- TinyFish's own sign-in screen, where you hand Claude the access it will use. Granted once per person and withdrawn the same way.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on, which is what lets an assistant like Claude talk to an outside service.
Connect TinyFish to Claude in three steps
- 01
Find TinyFish in Claude
In Claude's settings, open Customize, then Connectors, and look for TinyFish. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on first so each member can sign in.
- 02
Start the connection
Hit Connect on its row. TinyFish opens its own sign-in page, where you confirm with Allow to link your TinyFish account. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to TinyFish, not Claude, and it sets what the access covers. You can also withdraw that access later from your TinyFish account.
All 23 tools, grouped by what they do
TinyFish gives Claude 23 tools: 9 that read your account, 6 that change something in it, and 8 no official source describes.
Three groups: what Claude reads, what it starts or changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 9 read
- 6 write
- 8 not documented
What Claude reads (9)
9 toolsNine tools that search, extract or check a status without launching anything.
batch_status
Checks where several runs stand at once, up to 8. TinyFish suggests polling every 30 to 60 seconds until all of them are done. For a single run, get_run gives the details.
fetch_content
Pulls clean, structured content from one to ten pages, running JavaScript when needed, as Markdown, HTML or JSON. TinyFish recommends it over the agent when you only need to read.
get_run
Brings back the details of one automation run from its ID: its status, its result and any error information.
get_search_usage
Lists your past searches, filterable by date range and status, so you can see what was queried and when. The searches themselves aren't billed, per TinyFish's documentation.
get_wallet
Shows your TinyFish wallet balance, auto-reload state, per-product rates and any top-up in progress. It only reads.
list_browser_sessions
Lists all your remote browser sessions, with filters by session ID, time range and status, open or ended. Closing one early goes through close_browser_session, by its ID.
list_fetch_usage
Gives a record of your past page fetches, filterable by date and status. It returns metadata only, never the page content itself. Fetching itself isn't billed, per TinyFish.
list_runs
Lists your automation runs, with a status filter and pagination for long series. The details of one run come from get_run, and the status of several at once from batch_status.
search
Queries the web and returns structured results with title, snippet and URL, covering pages, news and research papers, with recency, date, location and domain filters per the official description.
What Claude starts or changes (6)
6 toolsSix tools that launch, stop or open something on TinyFish's side. No source spells out their confirmation, so the general rule applies.
batch_cancel
Approval: see the ruleStops several running or pending runs in one go, up to 8, from their IDs. Running it again on runs that already finished changes nothing.
cancel_run
Approval: see the ruleHalts one specific automation run, running or pending, by its ID. A run that has already ended simply reports its current status back.
close_browser_session
Approval: see the ruleShuts a browser session by its ID to free it straight away, instead of waiting for it to time out from inactivity.
create_browser_session
Approval: see the ruleStarts a remote, stealth Chrome session and returns the connection details to drive it with Playwright, Puppeteer or Selenium.
run_web_automation
Approval: see the ruleCarries out a multi-step task on a site from a URL and a plain-English goal, streaming progress live: clicks, navigation, forms, logins.
run_web_automation_async
Approval: see the ruleStarts the same automation as the web agent but immediately returns a run ID without waiting for it to finish. You check on the result separately.
Undocumented (8)
8 toolsThe directory publishes these eight names and nothing more. TinyFish's connector docs don't describe them, and we won't guess their job from a name.
cancel_monitor
Only its name shows up on the directory's tool list. Neither TinyFish's connector documentation nor any Claude page describes it, so this page credits it with no capability of any kind.
create_monitor
The directory lists this name, but no explanation comes with it, and TinyFish's tool documentation gives it no description, so this page doesn't describe it. No official text gives it a direction, read or write.
get_monitor
Nothing describes this tool beyond its name on the directory sheet. TinyFish leaves it out of its tool list, and Claude's documentation doesn't cover it either.
guide_next_step
This label is part of the directory sheet, and no official source documents it. TinyFish's documentation doesn't include it among its tools, so this page refrains from assigning it any role.
list_monitors
The sheet publishes this name without a word of explanation, and no other official source fills the gap. This page won't venture a guess at its purpose.
pause_monitor
No public documentation talks about this tool: the directory shows its name, and both TinyFish and Claude stay silent on how it works. The page therefore lends it no effect.
resume_monitor
All we know is the name written on the sheet. Neither TinyFish's connection guide nor any Anthropic source explains it, so this page says nothing about what it does or touches.
run_monitor
Present on the directory list, undocumented by every official source: that's all that can be stated about it. The page credits it with neither reading nor writing, for lack of any text to back it up.
What Claude checks with you first
By default, Claude stops and asks before every action it takes on an account for you. The request shows up in the chat at the moment it counts.
With TinyFish, six tools start or change something: launching the agent, cancelling, opening or closing a session. No source describes a confirmation specific to any of them, so the default rule covers them, as it does the eight undocumented tools. On Team and Enterprise workspaces, owners decide whether a member can let some actions through without being asked again, and can shut off writing for the whole org. Claude works with your TinyFish access and nothing beyond it.
Which plans include it
None of the 819 sheets in the official directory shows plan availability, and nobody publishes it connector by connector.
Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner first switches the connector on for the org. On TinyFish's side you need an account, and both the agent and the browser draw from your wallet. For the current status, check the TinyFish sheet in the directory.
Where this connector stops
A connector isn't an automation. Claude calls these tools while it answers you, so nothing reruns by itself on a schedule.
Only TinyFish documents this connector, in its integration docs; neither Claude's help center nor Anthropic's docs have a page on it. Eight tools on the sheet remain undescribed. The official description also mentions monitoring websites for changes, but no source ties that to a specific tool on the sheet. The directory's partner badge isn't a security audit, and Anthropic notes on every sheet that it doesn't pick a publisher's tools or vouch for how they behave.
Need help connecting TinyFish to Claude?
A person reads every message.
