# How to connect Poof to OpenClaw (paste one key, 11 tools) > Connect Poof to OpenClaw with ClawLink: paste your Poof key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/poof The usual route to Poof 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 Poof setup: install one ClawHub skill, connect Poof in the browser, and OpenClaw can call real Poof 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 Poof. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Poof** — 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 poof # connect Poof (browser OAuth) npx -y @useclawlink/cli actions poof # list available actions npx -y @useclawlink/cli run poof --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 Poof in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Poof API key once. Verify the connection by asking OpenClaw: > Use Poof to check balance and walk me through the result in plain English. ### 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 Poof is connected in the dashboard, that agent calls the same 11 Poof 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). ## Poof MCP for OpenClaw Looking for a Poof MCP server for OpenClaw? ClawLink connects Poof to OpenClaw and exposes 11 Poof 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 Poof integration](https://claw-link.dev/hermes/poof) works the same way. ## What the OpenClaw Poof integration can do 11 Poof tools are ready for OpenClaw once the account is connected. ### All 11 Poof tools for OpenClaw | Tool | What it does | |---|---| | **Check balance** `poof_check_balance` | Check the balance of a cryptocurrency wallet | | **Fetch gas price** `poof_fetch_gas_price` | Fetch current gas prices for blockchain transactions | | **Fetch price** `poof_fetch_price` | Fetch current cryptocurrency prices for supported tokens | | **Fetch smart contracts** `poof_fetch_smart_contracts` | Fetch all supported ERC-20 smart contracts across Ethereum, Avalanche, and Polygon networks | | **Create checkout** `poof_create_checkout` | Create a checkout session for fiat payments | | **Create deposit address** `poof_create_deposit_address` | Create a deposit address for receiving cryptocurrency payments | | **Create fiat charge** `poof_create_fiat_charge` | Create a fiat currency charge through Poof's payment gateway integration | | **Create fiat invoice** `poof_create_fiat_invoice` | Create a fiat currency invoice for payment collection | | **Create payment link** `poof_create_payment_link` | Create a payment link (invoice) for cryptocurrency payments | | **Create webhook** `poof_create_webhook` | Create a webhook subscription for receiving payment event notifications | | **Send payout** `poof_send_payout` | Send a cryptocurrency payout transaction from your wallet to an external address | ## Example prompts **Check Balance** > Use Poof to check balance and walk me through the result in plain English. **Fetch Gas Price** > Pull the relevant data from Poof, summarize it in plain English, and point out anything that needs attention. **Fetch Price** > Pull the relevant data from Poof, summarize it in plain English, and point out anything that needs attention. **Fetch Smart Contracts** > Pull the relevant data from Poof, 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 Poof working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Poof API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Poof 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 Poof. | 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 Poof actions to the runtime in a format your agent can reliably use. | 11 tools for Poof are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Poof 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 Poof in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Poof 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 Poof skill but can't call the tools The ClawHub skill teaches OpenClaw about Poof, but the calls run through the ClawLink plugin and your connected account. Make sure Poof 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 Poof 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 Poof tools Poof 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 Poof 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. ### Poof 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 Poof has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Poof integration? Yes. ClawLink is the fastest way to connect OpenClaw to Poof: link your Poof account once in the browser and OpenClaw can call the Poof API through 11 ready-made tools — no custom code or token handling. ### How do I add Poof to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Poof skill from ClawHub, then you click Connect in the dashboard to authorize Poof. OpenClaw calls the tools from the next message — no config files, and the Poof key you paste is stored server-side instead of in your environment. ### How long does it take to connect Poof to OpenClaw? About two minutes. Sign in, click Connect next to Poof in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Poof 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 Poof working from chat. ### OpenClaw installed the Poof skill but can't call the tools The ClawHub skill teaches OpenClaw about Poof, but the calls run through the ClawLink plugin and your connected account. Make sure Poof 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 - [Connect Stripe](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Connect Zoho Books](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [OpenClaw Ramp integration](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts