# How to connect Faraday to Hermes Agent (paste one key, 117 tools) > Connect Faraday to Hermes with ClawLink: paste your Faraday key once and 117 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/faraday Most guides for giving Hermes Agent Faraday 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 Faraday setup: pair once in the browser and your always-on Hermes agent can act on Faraday for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to Faraday. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Faraday** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 faraday # connect Faraday (browser OAuth) npx -y @useclawlink/cli actions faraday # list available actions npx -y @useclawlink/cli run faraday --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 Faraday in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Faraday API key once. Verify the connection by asking Hermes: > Before using Faraday to archive cohort, show me what will change and ask for confirmation. ### 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 Faraday is connected in the dashboard, that agent calls the same 117 Faraday 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). ## Faraday MCP for Hermes Looking for a Faraday MCP server for Hermes Agent? ClawLink connects Faraday to Hermes Agent and exposes 117 Faraday 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 Faraday integration](https://claw-link.dev/openclaw/faraday) works the same way. ## What the Hermes Agent Faraday integration can do 117 Faraday tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 117. ### 30 of 117 Faraday tools for Hermes | Tool | What it does | |---|---| | **Archive cohort** `faraday_archive_cohort` | Archive a cohort in Faraday | | **Archive connection** `faraday_archive_connection` | Archive a connection in Faraday | | **Archive dataset** `faraday_archive_dataset` | Archive a dataset in Faraday | | **Archive outcome** `faraday_archive_outcome` | Archive an outcome in Faraday | | **Get account** `faraday_get_account` | Retrieve detailed information about a Faraday account by its UUID | | **Get accounts** `faraday_get_accounts` | List all Faraday accounts accessible by the current user | | **Get accounts billing** `faraday_get_accounts_billing` | Get billing information about your account | | **Get cohort** `faraday_get_cohort` | Retrieve a specific cohort by ID | | **Get cohort analysis membership** `faraday_get_cohort_analysis_membership` | Get cohort membership counts over time for a specific cohort | | **Get cohorts** `faraday_get_cohorts` | List all cohorts in your Faraday account | | **Get connection datasets** `faraday_get_connection_datasets` | Retrieve all datasets that use a specific connection | | **Get connections targets** `faraday_get_connections_targets` | Retrieve all targets that use a specific connection | | **Get current account** `faraday_get_current_account` | Retrieve the current account information | | **Get current account billing** `faraday_get_current_account_billing` | Retrieve billing information about the current account | | **Get dataset** `faraday_get_dataset` | Retrieve a dataset by its UUID | | **Get datasets logs ingress** `faraday_get_datasets_logs_ingress` | Retrieve dataset ingress metrics over time | | **Get feature stores** `faraday_get_feature_stores` | List all feature stores | | **Get graph** `faraday_get_graph` | Retrieve the complete dependency graph for all resources on an account | | **Get market opportunity analyses** `faraday_get_market_opportunity_analyses` | Retrieve all market opportunity analyses from Faraday | | **Get outcome** `faraday_get_outcome` | Retrieve an outcome by its ID | | **Get outcomes** `faraday_get_outcomes` | List all outcomes for the account | | **Get persona set** `faraday_get_persona_set` | Retrieve a persona set by its UUID | | **Get persona set analysis flow** `faraday_get_persona_set_analysis_flow` | Retrieve the flow of persona sets over time, showing how individuals move between different | | **Get persona sets** `faraday_get_persona_sets` | List all persona sets | | **Get persona sets analysis dimensions** `faraday_get_persona_sets_analysis_dimensions` | Get various trait breakdown information about a persona set | | **Get place** `faraday_get_place` | Retrieve a specific place by its UUID | | **Get places** `faraday_get_places` | List all places in Faraday | | **Get recommenders** `faraday_get_recommenders` | List all recommenders | | **Get scope** `faraday_get_scope` | Retrieve detailed information about a Faraday scope by its UUID | | **Get scope analysis** `faraday_get_scope_analysis` | Get analysis for a scope including outcomes and recommenders with probability distributions | ## Example prompts **Archive Cohort** > Before using Faraday to archive cohort, show me what will change and ask for confirmation. **Archive Connection** > Before using Faraday to archive connection, show me what will change and ask for confirmation. **Archive Dataset** > Before using Faraday to archive dataset, show me what will change and ask for confirmation. **Archive Outcome** > Before using Faraday to archive outcome, show me what will change and ask for confirmation. ## 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 Faraday working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Faraday API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Faraday 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 Faraday. | 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 Faraday actions to the runtime in a format your agent can reliably use. | 117 tools for Faraday are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Faraday 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 Faraday in the browser, and the 117 tools above work from chat. There is no SDK and no config file, and the Faraday 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 Faraday 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 Faraday 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 Faraday tools Faraday 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 Faraday 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. ### Faraday 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 Faraday 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 Faraday integration? Yes. ClawLink is the fastest way to connect Hermes to Faraday: link your Faraday account once in the browser and Hermes Agent can call the Faraday API through 117 ready-made tools — no custom code or token handling. ### How do I connect Faraday 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 Faraday in the dashboard and Hermes can use it from the next message — no config files, and the Faraday key you paste is stored server-side instead of in your environment. ### How long does it take to connect Faraday to Hermes Agent? About two minutes. Sign in, click Connect next to Faraday in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Faraday 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 Faraday working from chat. ### Hermes paired but still can't use Faraday 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 - [Connect DataRobot](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](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. - [Hermes ElevenLabs integration](https://claw-link.dev/hermes/elevenlabs) — Generate speech and voice cloning