How to connect Faraday to OpenClaw
Connect Faraday to OpenClaw with ClawLink: paste your Faraday key once and 117 tools work from chat. No MCP server to run, nothing stored on your machine.


Faraday lets you embed AI in workflows throughout your stack—to make your favorite tools perform even better.. Once connected, OpenClaw can read and act on Faraday from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Faraday access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Faraday setup: install one ClawHub skill, connect Faraday in the browser, and OpenClaw can call real Faraday actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Faraday skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Faraday" (hith3sh/faraday-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/faraday-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Faraday.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Faraday
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Faraday?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Faraday in the ClawLink dashboard — paste your Faraday API key once.
Verify the connection by asking OpenClaw:
Before using Faraday to archive cohort, show me what will change and ask for confirmation.
Using a different agent?
The OpenClaw 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 loginlogin 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.
Faraday MCP for OpenClaw
Looking for a Faraday MCP server for OpenClaw? ClawLink connects Faraday to OpenClaw and exposes 117 Faraday tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Faraday integration works the same way.
What the OpenClaw Faraday integration can do
117 Faraday tools are ready for OpenClaw 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 OpenClaw
| 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 |
Try it: find the Faraday tool you need
Browse the 30 Faraday tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Before using Faraday to archive cohort, show me what will change and ask for confirmation.
Before using Faraday to archive connection, show me what will change and ask for confirmation.
Before using Faraday to archive dataset, show me what will change and ask for confirmation.
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 OpenClaw. 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 OpenClaw 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 comparison.
Troubleshooting
OpenClaw installed the Faraday skill but can't call the tools
The ClawHub skill teaches OpenClaw about Faraday, but the calls run through the ClawLink plugin and your connected account. Make sure Faraday is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
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.
FAQ
Is there a OpenClaw Faraday integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Faraday: link your Faraday account once in the browser and OpenClaw can call the Faraday API through 117 ready-made tools — no custom code or token handling.
How do I add Faraday to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Faraday skill from ClawHub, then you click Connect in the dashboard to authorize Faraday. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to Faraday in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Faraday working from chat.
OpenClaw installed the Faraday skill but can't call the tools
The ClawHub skill teaches OpenClaw about Faraday, but the calls run through the ClawLink plugin and your connected account. Make sure Faraday is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
DataRobot tools
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
ElevenLabs tools
Generate speech and voice cloning