# How to connect Chameleon to Hermes Agent (paste one key, 14 tools) > Connect Chameleon to Hermes with ClawLink: paste your Chameleon key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/chameleon Most guides for giving Hermes Agent Chameleon 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 Chameleon setup: pair once in the browser and your always-on Hermes agent can act on Chameleon 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 Chameleon. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Chameleon** — 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 chameleon # connect Chameleon (browser OAuth) npx -y @useclawlink/cli actions chameleon # list available actions npx -y @useclawlink/cli run chameleon --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 Chameleon in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Chameleon API key once. Verify the connection by asking Hermes: > Use Chameleon to count customer records 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 Chameleon is connected in the dashboard, that agent calls the same 14 Chameleon 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). ## Chameleon MCP for Hermes Looking for a Chameleon MCP server for Hermes Agent? ClawLink connects Chameleon to Hermes Agent and exposes 14 Chameleon 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 Chameleon integration](https://claw-link.dev/openclaw/chameleon) works the same way. ## What the Hermes Agent Chameleon integration can do 14 Chameleon tools are ready for Hermes Agent once the account is connected. ### All 14 Chameleon tools for Hermes | Tool | What it does | |---|---| | **Count customer records** `chameleon_count_customer_records` | Count Chameleon profiles or companies matching structured filters without retrieving the | | **Get account identity** `chameleon_get_account_identity` | Return the Chameleon account ID and admin user ID associated with the connected Account Secret | | **Get delivery** `chameleon_get_delivery` | Retrieve one Chameleon experience delivery by ID without triggering, changing, or cancelling it | | **Get experience** `chameleon_get_experience` | Retrieve one Chameleon tour, microsurvey, launcher, embed, or tooltip by ID without modifying | | **List changes** `chameleon_list_changes` | List one page of Chameleon change history across the account or for one supported experience | | **List deliveries** `chameleon_list_deliveries` | List one page of scheduled Chameleon experience deliveries, optionally filtered by experience | | **List domains or environments** `chameleon_list_domains_or_environments` | List one page of configured Chameleon domains or environments without changing account routing | | **List experience analytics** `chameleon_list_experience_analytics` | List one page of tour interactions or microsurvey responses for a specific Chameleon experience | | **List experiences** `chameleon_list_experiences` | List one page of Chameleon tours, microsurveys, launchers, embeds, or tooltips without | | **List targeting metadata** `chameleon_list_targeting_metadata` | List one page of Chameleon segments, tags, themes, tracked event names, or profile/company | | **Lookup customer record** `chameleon_lookup_customer_record` | Retrieve one Chameleon profile or company by its Chameleon ID or external identifier | | **Search customer records** `chameleon_search_customer_records` | Search Chameleon profiles or companies with structured filters and return one offset-paginated | | **Upsert customer record** `chameleon_upsert_customer_record` | Create or update one Chameleon profile or company by external UID and return its Chameleon ID | | **Track event** `chameleon_track_event` | Irreversibly record one named event for a Chameleon profile identified by ID or external UID | ## Example prompts **Count Customer Records** > Use Chameleon to count customer records and walk me through the result in plain English. **Get Account Identity** > Pull the relevant data from Chameleon, summarize it in plain English, and point out anything that needs attention. **Get Delivery** > Pull the relevant data from Chameleon, summarize it in plain English, and point out anything that needs attention. **Get Experience** > Pull the relevant data from Chameleon, 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 Chameleon working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Chameleon API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Chameleon 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 Chameleon. | 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 Chameleon actions to the runtime in a format your agent can reliably use. | 14 tools for Chameleon are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Chameleon 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 Chameleon in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Chameleon 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 Chameleon 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 Chameleon 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 Chameleon tools Chameleon 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 Chameleon 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. ### Chameleon 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 Chameleon 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 Chameleon integration? Yes. ClawLink is the fastest way to connect Hermes to Chameleon: link your Chameleon account once in the browser and Hermes Agent can call the Chameleon API through 14 ready-made tools — no custom code or token handling. ### How do I connect Chameleon 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 Chameleon in the dashboard and Hermes can use it from the next message — no config files, and the Chameleon key you paste is stored server-side instead of in your environment. ### How long does it take to connect Chameleon to Hermes Agent? About two minutes. Sign in, click Connect next to Chameleon in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Chameleon 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 Chameleon working from chat. ### Hermes paired but still can't use Chameleon 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 - [Hermes DataforSEO integration](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Connect Metabase](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.