# How to connect Coinbase Wallet to OpenClaw (no API keys)

> Connect Coinbase Wallet to OpenClaw with ClawLink in one click — 6 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.

Web version: https://claw-link.dev/openclaw/coinbase-wallet

The usual route to Coinbase Wallet 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 Coinbase Wallet setup: install one ClawHub skill, connect Coinbase Wallet in the browser, and OpenClaw can call real Coinbase Wallet 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 Coinbase Wallet.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Coinbase Wallet** — 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 coinbase-wallet  # connect Coinbase Wallet (browser OAuth)
npx -y @useclawlink/cli actions coinbase-wallet  # list available actions
npx -y @useclawlink/cli run coinbase-wallet <action> --input '<json>'  # 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 Coinbase Wallet in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys.

Verify the connection by asking OpenClaw:

> Use Coinbase Wallet to mcp get portfolio 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 Coinbase Wallet is connected in the dashboard, that agent calls the same 6 Coinbase Wallet 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).

## Coinbase Wallet MCP for OpenClaw

Looking for a Coinbase Wallet MCP server for OpenClaw? ClawLink connects Coinbase Wallet to OpenClaw and exposes 6 Coinbase Wallet 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 Coinbase Wallet integration](https://claw-link.dev/hermes/coinbase-wallet) works the same way.

## What the OpenClaw Coinbase Wallet integration can do

6 Coinbase Wallet tools are ready for OpenClaw once the account is connected.

### All 6 Coinbase Wallet tools for OpenClaw

| Tool | What it does |
|---|---|
| **Mcp get portfolio** `coinbase_wallet_mcp_get_portfolio` | Returns total portfolio value and per-asset breakdown for a wallet address |
| **Mcp get request status** `coinbase_wallet_mcp_get_request_status` | Poll the status of an approval request by requestId (returned by send, sign, swap, or |
| **Mcp get transaction history** `coinbase_wallet_mcp_get_transaction_history` | Returns paginated transaction history in reverse chronological order for a single chain |
| **Mcp get wallets** `coinbase_wallet_mcp_get_wallets` | Returns the user's Base Account and all agent wallets with delegation status, spend policy, and |
| **Mcp help** `coinbase_wallet_mcp_help` | Returns guidance for helping the user with protocol-specific tasks that aren't directly |
| **Mcp search tokens** `coinbase_wallet_mcp_search_tokens` | Search for tokens by symbol or name on a single chain |

## Example prompts

**Mcp Get Portfolio**

> Use Coinbase Wallet to mcp get portfolio and walk me through the result in plain English.

**Mcp Get Request Status**

> Use Coinbase Wallet to mcp get request status and walk me through the result in plain English.

**Mcp Get Transaction History**

> Use Coinbase Wallet to mcp get transaction history and walk me through the result in plain English.

**Mcp Get Wallets**

> Use Coinbase Wallet to mcp get wallets and walk me through the result in plain English.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual OAuth app 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 Coinbase Wallet working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Connection flow** | Register a Coinbase Wallet app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Coinbase Wallet through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Coinbase Wallet. | 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 Coinbase Wallet actions to the runtime in a format your agent can reliably use. | 6 tools for Coinbase Wallet are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Coinbase Wallet 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 Coinbase Wallet in the browser, and the 6 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### OpenClaw installed the Coinbase Wallet skill but can't call the tools
The ClawHub skill teaches OpenClaw about Coinbase Wallet, but the calls run through the ClawLink plugin and your connected account. Make sure Coinbase Wallet 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 Coinbase Wallet 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 Coinbase Wallet tools
Coinbase Wallet 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 Coinbase Wallet 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.

### Coinbase Wallet 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.

### OAuth finished in the browser but the account is still missing
Try reconnecting Coinbase Wallet and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

### Is there a OpenClaw Coinbase Wallet integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Coinbase Wallet: link your Coinbase Wallet account once in the browser and OpenClaw can call the Coinbase Wallet API through 6 ready-made tools — no custom code or token handling.

### How do I add Coinbase Wallet to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Coinbase Wallet skill from ClawHub, then you click Connect in the dashboard to authorize Coinbase Wallet. OpenClaw calls the tools from the next message — no config files or API keys to manage.

### How long does it take to connect Coinbase Wallet to OpenClaw?
About two minutes. Sign in, click Connect next to Coinbase Wallet in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Coinbase Wallet up myself?
The alternative to ClawLink is usually manual OAuth app 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 Coinbase Wallet working from chat.

### OpenClaw installed the Coinbase Wallet skill but can't call the tools
The ClawHub skill teaches OpenClaw about Coinbase Wallet, but the calls run through the ClawLink plugin and your connected account. Make sure Coinbase Wallet 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

- [Stripe](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices
- [OpenClaw Zoho Books integration](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting
- [Connect Ramp](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts
