# How to connect Jungle Scout to Hermes Agent (paste one key, 6 tools) > Connect Jungle Scout to Hermes with ClawLink: paste your Jungle Scout key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/junglescout Most guides for giving Hermes Agent Jungle Scout 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 Jungle Scout setup: pair once in the browser and your always-on Hermes agent can act on Jungle Scout 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 Jungle Scout. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Jungle Scout** — 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 junglescout # connect Jungle Scout (browser OAuth) npx -y @useclawlink/cli actions junglescout # list available actions npx -y @useclawlink/cli run junglescout --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 Jungle Scout in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Jungle Scout API key once. Verify the connection by asking Hermes: > Use Jungle Scout to keyword historical volume 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 Jungle Scout is connected in the dashboard, that agent calls the same 6 Jungle Scout 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). ## Jungle Scout MCP for Hermes Looking for a Jungle Scout MCP server for Hermes Agent? ClawLink connects Jungle Scout to Hermes Agent and exposes 6 Jungle Scout 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 Jungle Scout integration](https://claw-link.dev/openclaw/junglescout) works the same way. ## What the Hermes Agent Jungle Scout integration can do 6 Jungle Scout tools are ready for Hermes Agent once the account is connected. ### All 6 Jungle Scout tools for Hermes | Tool | What it does | |---|---| | **Keyword historical volume** `junglescout_keyword_historical_volume` | Fetches the historical search volume data for a specified keyword over a given time period | | **Query the product database** `junglescout_query_the_product_database` | Queries the Jungle Scout product database to retrieve product data based on various filters | | **Retrieve data for a specific keyword query** `junglescout_retrieve_data_for_a_specific_keyword_query` | Returns data based on a specific keyword query, including search volume and competition | | **Retrieve keyword data for specified asins** `junglescout_retrieve_keyword_data_for_specified_asins` | Returns keywords for which the queried ASIN(s) appear in Amazon search results | | **Retrieve sales estimates data** `junglescout_retrieve_sales_estimates_data` | Fetches sales estimates data for specified parameters | | **Retrieve share of voice data** `junglescout_retrieve_share_of_voice_data` | Fetches share of voice data for specified keywords | ## Example prompts **Keyword Historical Volume** > Use Jungle Scout to keyword historical volume and walk me through the result in plain English. **Query The Product Database** > Use Jungle Scout to query the product database and walk me through the result in plain English. **Retrieve Data For A Specific Keyword Query** > Pull the relevant data from Jungle Scout, summarize it in plain English, and point out anything that needs attention. **Retrieve Keyword Data For Specified Asins** > Pull the relevant data from Jungle Scout, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Jungle Scout working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Jungle Scout API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Jungle Scout account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Jungle Scout. | 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 Jungle Scout actions to the runtime in a format your agent can reliably use. | 6 tools for Jungle Scout are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Jungle Scout 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 Jungle Scout in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Jungle Scout key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Jungle Scout 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 Jungle Scout 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 Jungle Scout tools Jungle Scout 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 Jungle Scout 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. ### Jungle Scout 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. ### API key setup works but results look incomplete Double-check that the API key for Jungle Scout has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Jungle Scout integration? Yes. ClawLink is the fastest way to connect Hermes to Jungle Scout: link your Jungle Scout account once in the browser and Hermes Agent can call the Jungle Scout API through 6 ready-made tools — no custom code or token handling. ### How do I connect Jungle Scout 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 Jungle Scout in the dashboard and Hermes can use it from the next message — no config files, and the Jungle Scout key you paste is stored server-side instead of in your environment. ### How long does it take to connect Jungle Scout to Hermes Agent? About two minutes. Sign in, click Connect next to Jungle Scout in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Jungle Scout up myself? The alternative to ClawLink is usually manual API key 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 Jungle Scout working from chat. ### Hermes paired but still can't use Jungle Scout 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 - [PostHog tools](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase tools](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.