Wiring CAI into OpenClaw, Hermes, Codex, and Cursor: the exact MCP config for each host The general install is one command, , and the contract lives at .
This post is the host-specific deep-dive: the exact config block for OpenClaw, Hermes, Codex, and Cursor, with the path to the config file, the env var handling, and the restart command.
Before you start You need: A CAI account ().
The signup is four steps, about 2 minutes.
An API key from the account dashboard.
The key has a scope.
Start with the read scopes and add when you need transfers.
The MCP server installed ().
The MCP host of your choice installed and running.
OpenClaw OpenClaw's MCP config lives at .
Add the CAI server to the object: Restart OpenClaw.
The CAI tools appear in the agent's tool surface.
Verify with .
The server should show as running.
If the server doesn't appear: check the binary is on the PATH ().
If the binary is missing, re-run the install.
If the binary is on the PATH but the server still doesn't start, check the API key is valid with .
Hermes Hermes uses a CLI to add MCP servers: The env var is stored in the Hermes MCP config.
Restart Hermes with .
Verify with .
The server should show as running with the env var set.
Hermes-specific note: Hermes reads MCP env vars at startup, not at request time.
If you rotate your CAI API key, you need to update the env var and restart Hermes.
Codex Codex reads MCP config from .
The format is the standard MCP config: Restart Codex.
The CAI tools appear in the agent's tool surface.
Verify by running a test request. should return a successful handshake.
Codex-specific note: Codex's MCP support is newer than OpenClaw's.
If you see "MCP server not found" on startup, check the Codex version is up to date.
The CAI MCP server requires Codex ≥ 0.x.y (the specific version is in ).
Cursor Cursor's MCP settings are in the UI: .
The form fields: Name: Command: Env: Click "Add" and Cursor restarts the MCP server.
The CAI tools appear in the agent's tool surface.
Verify with .
The test should return a successful handshake.
Cursor-specific note: Cursor stores the env var in its own keychain, not in a config file.
If you rotate your CAI API key, update the env var in the MCP settings UI and click "Save." A generic host (any MCP-compatible framework) If the host isn't on the list, the config is the same shape: The MCP server is generic.
The contract is in .
The tool names are stable.
Any host that supports MCP can use the server.
Verifying the install Once the server is running in your host, run a quick test: Identity check - should return your address, your wallet bindings, and your linked subwallets.
Balance check - should return your balances (or an empty list with a if you haven't deposited yet).
Transfer test - with a tiny amount (0.01 USDC) should return a hosted-action URL.
Open the URL, tap once, and the transfer completes.
A few things to keep in mind about the wallet.
There is a $200/day auto-limit while the security audit completes.
New recipients and new devices always require confirmation.
Think of it like cash in your pocket.
It works for daily spending without exposing a private key in chat.
The vault product (multi-sig, time-locks) is coming for larger balances.
The hosted-action flow The part of CAI that the user sees most often is the hosted-action flow.
When the agent calls , the API returns a hosted-action URL.
The user opens it, confirms with one tap, and the payment goes through.
The agent polls for the receipt.
No private key in chat, no signature to copy, no browser extension to connect.
That single-tap confirmation page is the user's control point for every agent-initiated payment.
If any step fails, the comment section below is the right place to file the bug.
The contract is .
The install command is .
The dashboard is at .
If you wired CAI into OpenClaw / Hermes / Codex / Cursor and the tool surface didn't appear Comment below with: What you ran - the install command, the request, the MCP host config.
Copy the actual command or request.
What you expected - one sentence.
What you got - the error message, the empty response, the unexpected behavior.
Paste it verbatim.
Your environment - OS, Node version, the MCP host (OpenClaw / Hermes / Codex / Cursor / other), the CAI account tier if relevant.
Every comment on this article gets read.
Bug reports will be replied to within 24 hours.
Friction points shape what we document next.
Documentation: · · to sign up.