ClawLink

How to connect TinyFish to Hermes Agent

Connect TinyFish to Hermes with ClawLink in one click — 20 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
TinyFish
TinyFish
TinyFishOAUTH2MCP

Browse and act on websites with an AI agent. Once connected, Hermes Agent can read and act on TinyFish from chat — pairing, token refresh, and tool wiring handled for you.

20 tools

Most guides for giving Hermes Agent TinyFish access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical TinyFish setup: pair once in the browser and your always-on Hermes agent can act on TinyFish for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to TinyFish.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect TinyFish

    One-click OAuth in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with TinyFish?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect TinyFish in the ClawLink dashboard — a one-click OAuth approval, no API keys.

Verify the connection by asking Hermes:

Use TinyFish to mcp batch status and walk me through the result in plain English.

Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once TinyFish is connected in the dashboard, that agent calls the same 20 TinyFish tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

TinyFish MCP for Hermes

Looking for a TinyFish MCP server for Hermes Agent? ClawLink connects TinyFish to Hermes Agent and exposes 20 TinyFish tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw TinyFish integration works the same way.

What the Hermes Agent TinyFish integration can do

20 TinyFish tools are ready for Hermes Agent once the account is connected.

All 20 TinyFish tools for Hermes

ToolWhat it does
Mcp batch status tinyfish_mcp_batch_statusOnly use after batch_create to poll progress for multiple automation runs
Mcp discover run tinyfish_mcp_discover_runApp-only tool for discovering the currently running automation for this session
Mcp fetch content tinyfish_mcp_fetch_contentDefault, free, and most token-efficient tool for reading URL(s) and extracting source details
Mcp get run tinyfish_mcp_get_runOnly use after run_web_automation errors, times out, or returns a run_id that needs polling
Mcp get search usage tinyfish_mcp_get_search_usageOnly use when the user asks to review search history, check what queries were made, or audit
Mcp get steps tinyfish_mcp_get_stepsOnly use when the user asks to inspect how an automation ran
Mcp get wallet tinyfish_mcp_get_walletRead-only
Mcp guide next step tinyfish_mcp_guide_next_stepReturns the next interactive TinyFish onboarding step based on the user’s real usage
Mcp list browser sessions tinyfish_mcp_list_browser_sessionsOnly use when the user asks to check active browser sessions, review browser usage history, or
Mcp list fetch usage tinyfish_mcp_list_fetch_usageOnly use when the user asks to review fetch history or audit fetch usage
Mcp list runs tinyfish_mcp_list_runsOnly use when you need to find a run_id for a recently created automation, usually after
Mcp poll status tinyfish_mcp_poll_statusApp-only tool for polling the current status of an automation run
Mcp search tinyfish_mcp_searchDefault, free, and most token-efficient first tool for external knowledge and web grounding
Mcp batch cancel tinyfish_mcp_batch_cancelOnly use when the user explicitly asks to stop multiple running or pending automations
Mcp cancel run tinyfish_mcp_cancel_runOnly use when the user explicitly asks to stop a running or pending automation
Mcp close browser session tinyfish_mcp_close_browser_sessionOnly use when the user explicitly wants to stop or close a remote browser session
Mcp create browser session tinyfish_mcp_create_browser_sessionFor direct browser control or visual QA, open a browser session through your wallet account
Mcp create monitor tinyfish_mcp_create_monitorUse when the user asks to monitor a webpage for changes or subscribe to updates about a web
Mcp run web automation tinyfish_mcp_run_web_automationMetered web automation is available through your wallet — use it for clicking, forms, login, or
Mcp run web automation async tinyfish_mcp_run_web_automation_async⚠️ ONLY call this tool when the user has EXPLICITLY said they want to run the task in the

Try it: find the TinyFish tool you need

Browse the 20 TinyFish tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Use TinyFish to mcp batch status and walk me through the result in plain English.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want TinyFish working from chat.

ManualClawLink
Connection flowRegister a TinyFish app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift.Users connect TinyFish through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for TinyFish.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right TinyFish actions to the runtime in a format your agent can reliably use.20 tools for TinyFish are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes TinyFish to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect TinyFish in the browser, and the 20 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use TinyFish

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Connection succeeds but no tools appear

Reconnect TinyFish from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling TinyFish tools

TinyFish tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every TinyFish call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

TinyFish returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

OAuth finished in the browser but the account is still missing

Try reconnecting TinyFish and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

FAQ

Is there a Hermes Agent TinyFish integration?

Yes. ClawLink is the fastest way to connect Hermes to TinyFish: link your TinyFish account once in the browser and Hermes Agent can call the TinyFish API through 20 ready-made tools — no custom code or token handling.

How do I connect TinyFish to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect TinyFish in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

How long does it take to connect TinyFish to Hermes Agent?

About two minutes. Sign in, click Connect next to TinyFish in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring TinyFish up myself?

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want TinyFish working from chat.

Hermes paired but still can't use TinyFish

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

On this page