# How to connect TinyFish to Hermes Agent (no API keys) > Connect TinyFish to Hermes with ClawLink in one click — 8 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/tinyfish 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. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect TinyFish** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect tinyfish # connect TinyFish (browser OAuth) npx -y @useclawlink/cli actions tinyfish # list available actions npx -y @useclawlink/cli run tinyfish --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use TinyFish to mcp get run 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: ```bash 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 8 TinyFish tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/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 8 TinyFish tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw TinyFish integration](https://claw-link.dev/openclaw/tinyfish) works the same way. ## What the Hermes Agent TinyFish integration can do 8 TinyFish tools are ready for Hermes Agent once the account is connected. ### All 8 TinyFish tools for Hermes | Tool | What it does | |---|---| | **Mcp get run** `tinyfish_mcp_get_run` | Retrieves details of a specific automation run by its ID | | **Mcp get steps** `tinyfish_mcp_get_steps` | Retrieves the steps taken during an automation run, including screenshots | | **Mcp list runs** `tinyfish_mcp_list_runs` | Lists automation runs with optional filtering by status and pagination support | | **Mcp poll status** `tinyfish_mcp_poll_status` | Polls the current status of an automation run | | **Mcp cancel run** `tinyfish_mcp_cancel_run` | Cancels a running or pending automation run by its ID | | **Mcp discover run** `tinyfish_mcp_discover_run` | Discovers the currently running automation for this session | | **Mcp run web automation** `tinyfish_mcp_run_web_automation` | Executes web automation given a URL and a Natural Language description of the automation goal | | **Mcp run web automation async** `tinyfish_mcp_run_web_automation_async` | Starts a NEW web automation run asynchronously and returns a run_id immediately without waiting | ## Example prompts **Mcp Get Run** > Use TinyFish to mcp get run and walk me through the result in plain English. **Mcp Get Steps** > Use TinyFish to mcp get steps and walk me through the result in plain English. **Mcp List Runs** > Use TinyFish to mcp list runs and walk me through the result in plain English. **Mcp Poll Status** > Use TinyFish to mcp poll status and walk me through the result in plain English. ## ClawLink vs. building it yourself 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. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register 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 maintenance** | You 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 usability** | You still need to expose the right TinyFish actions to the runtime in a format your agent can reliably use. | 8 tools for TinyFish are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio 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 8 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### 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. ### 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 8 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`. ## Related - [DataRobot tools](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.