# How to connect Fibery to OpenClaw (paste one key, 23 tools) > Connect Fibery to OpenClaw with ClawLink: paste your Fibery key once and 23 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/fibery The usual route to Fibery 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 Fibery setup: install one ClawHub skill, connect Fibery in the browser, and OpenClaw can call real Fibery actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Fibery. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Fibery** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 fibery # connect Fibery (browser OAuth) npx -y @useclawlink/cli actions fibery # list available actions npx -y @useclawlink/cli run fibery --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Fibery in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fibery API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Fibery, summarize it in plain English, and point out anything that needs attention. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Fibery is connected in the dashboard, that agent calls the same 23 Fibery 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). ## Fibery MCP for OpenClaw Looking for a Fibery MCP server for OpenClaw? ClawLink connects Fibery to OpenClaw and exposes 23 Fibery 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 Hermes instead? The [Hermes Fibery integration](https://claw-link.dev/hermes/fibery) works the same way. ## What the OpenClaw Fibery integration can do 23 Fibery tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 23. ### 20 of 23 Fibery tools for OpenClaw | Tool | What it does | |---|---| | **Get app info** `fibery_get_app_info` | Retrieve application information | | **Get custom app endpoints** `fibery_get_custom_app_endpoints` | List custom app endpoints | | **Get custom apps** `fibery_get_custom_apps` | List all custom apps in the Fibery workspace | | **Get file** `fibery_get_file` | Download a file from Fibery by its secret or ID | | **Get graph ql schema** `fibery_get_graph_ql_schema` | Retrieves the GraphQL schema for the Fibery workspace using standard GraphQL introspection | | **Get user preferences** `fibery_get_user_preferences` | Retrieve the current user's UI preferences | | **Post auth refresh token** `fibery_post_auth_refresh_token` | Validate and refresh an access token | | **Post auth token** `fibery_post_auth_token` | Validates Fibery API authentication and returns the active access token | | **Post fetch data count** `fibery_post_fetch_data_count` | Count the total number of entities for a given Fibery type (database) | | **Post fetch data list** `fibery_post_fetch_data_list` | Fetches one page of distinct values for a specific field from a Fibery entity type | | **Post fetch schema** `fibery_post_fetch_schema` | Fetch the complete schema metadata for a Fibery workspace | | **Post validate account** `fibery_post_validate_account` | Validates Fibery workspace credentials by performing a test API query to retrieve the | | **Post validate filter** `fibery_post_validate_filter` | Validates filter definitions before executing data queries | | **Execute graph ql query** `fibery_execute_graph_ql_query` | Execute GraphQL queries or mutations against a Fibery workspace | | **Post create entity** `fibery_post_create_entity` | Create a new Fibery entity | | **Post oauth2 access token** `fibery_post_oauth2_access_token` | Exchange an OAuth2 authorization code for access and refresh tokens | | **Update entity** `fibery_update_entity` | Update an existing Fibery entity's fields | | **Update user preferences** `fibery_update_user_preferences` | Update the current user's preferences by using the Commands API | | **Upload file** `fibery_upload_file` | Upload a file to Fibery's file storage | | **Post revoke token** `fibery_post_revoke_token` | Delete/revoke an existing Fibery API access token by its ID | ## Example prompts **Get App Info** > Pull the relevant data from Fibery, summarize it in plain English, and point out anything that needs attention. **Get Custom App Endpoints** > Pull the relevant data from Fibery, summarize it in plain English, and point out anything that needs attention. **Get Custom Apps** > Pull the relevant data from Fibery, summarize it in plain English, and point out anything that needs attention. **Get File** > Pull the relevant data from Fibery, 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Fibery working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fibery API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fibery 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 Fibery. | 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 Fibery actions to the runtime in a format your agent can reliably use. | 23 tools for Fibery are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fibery 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 Fibery in the browser, and the 23 tools above work from chat. There is no SDK and no config file, and the Fibery 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. ### OpenClaw installed the Fibery skill but can't call the tools The ClawHub skill teaches OpenClaw about Fibery, but the calls run through the ClawLink plugin and your connected account. Make sure Fibery 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 Fibery 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 Fibery tools Fibery 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 Fibery 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. ### Fibery 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 Fibery has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Fibery integration? Yes. ClawLink is the fastest way to connect OpenClaw to Fibery: link your Fibery account once in the browser and OpenClaw can call the Fibery API through 23 ready-made tools — no custom code or token handling. ### How do I add Fibery to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Fibery skill from ClawHub, then you click Connect in the dashboard to authorize Fibery. OpenClaw calls the tools from the next message — no config files, and the Fibery key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fibery to OpenClaw? About two minutes. Sign in, click Connect next to Fibery in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Fibery 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 Fibery working from chat. ### OpenClaw installed the Fibery skill but can't call the tools The ClawHub skill teaches OpenClaw about Fibery, but the calls run through the ClawLink plugin and your connected account. Make sure Fibery 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 - [Trello tools](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [Connect ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints