How to connect Wise to OpenClaw
Connect Wise to OpenClaw with ClawLink: paste your Wise key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine.
WiseAPI KEYMCPAccess supported quotes, balances, transfers, recipients, and account data for PERSONAL or BUSINESS profiles using a personal API token created from a Wise Business account.. Once connected, OpenClaw can read and act on Wise from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Wise 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 Wise setup: install one ClawHub skill, connect Wise in the browser, and OpenClaw can call real Wise actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Wise 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 "Wise" (hith3sh/wise-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/wise-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 Wise.
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 Wise
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Wise?"
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 Wise in the ClawLink dashboard — paste your Wise API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Wise, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Wise is connected in the dashboard, that agent calls the same 9 Wise tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Wise MCP for OpenClaw
Looking for a Wise MCP server for OpenClaw? ClawLink connects Wise to OpenClaw and exposes 9 Wise tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Wise integration works the same way.
What the OpenClaw Wise integration can do
9 Wise tools are ready for OpenClaw once the account is connected.
All 9 Wise tools for OpenClaw
| Tool | What it does |
|---|---|
Get exchange rate wise_get_exchange_rate | Get Wise's latest exchange rate for one source and target currency pair; this is an indicative |
Get quote wise_get_quote | Retrieve a Wise quote by profile and quote ID, including its current status, pricing, payment |
List activities wise_list_activities | List a Wise profile's account activity with optional status, resource-type, and time filters |
List balances wise_list_balances | List standard balances and savings jars for a Wise profile without creating, deleting, or |
List currencies wise_list_currencies | List currencies Wise currently supports for transfers, including their ISO codes and decimal |
List profiles wise_list_profiles | List the connected Wise account's personal or business profiles and return the profile IDs |
List recipients wise_list_recipients | List Wise recipients for a profile, optionally filtering by active status, ownership, currency |
List transfers wise_list_transfers | List and filter existing Wise transfers for a profile, one page at a time; this tool cannot |
Create quote wise_create_quote | Create a transient Wise bank-transfer quote for a personal or business profile |
Try it: find the Wise tool you need
Browse the 9 Wise tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Wise, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wise, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Wise, group them by priority, and recommend what OpenClaw should do next.
List the relevant items in Wise, group them by priority, and recommend what OpenClaw should do next.
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 Wise working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Wise API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Wise 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 Wise. | 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 Wise actions to the runtime in a format your agent can reliably use. | 9 tools for Wise are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Wise 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 Wise in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Wise 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 Wise skill but can't call the tools
The ClawHub skill teaches OpenClaw about Wise, but the calls run through the ClawLink plugin and your connected account. Make sure Wise 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 Wise 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 Wise tools
Wise 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 Wise 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.
Wise 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 Wise 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 Wise integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Wise: link your Wise account once in the browser and OpenClaw can call the Wise API through 9 ready-made tools — no custom code or token handling.
How do I add Wise to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Wise skill from ClawHub, then you click Connect in the dashboard to authorize Wise. OpenClaw calls the tools from the next message — no config files, and the Wise key you paste is stored server-side instead of in your environment.
How long does it take to connect Wise to OpenClaw?
About two minutes. Sign in, click Connect next to Wise in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Wise 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 Wise working from chat.
OpenClaw installed the Wise skill but can't call the tools
The ClawHub skill teaches OpenClaw about Wise, but the calls run through the ClawLink plugin and your connected account. Make sure Wise 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.
