Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@
- Let a distribution omit selected skill files and drop source lines marked `<!-- omit: <distribution> -->`. Other distributions still copy skills unchanged, and links to unselected skills or omitted files fail the build.
- Remove x402 from the ChatGPT listing copy and keywords, and replace its starter prompt with three prompts for portfolio review, rebalancing, and scaling in with limit orders.
- Describe paid research in the `coinbase-mcp` skill description without naming x402.
- Document Solana in the `wallet-mcp` skill: `get_portfolio`, `get_transaction_history`, `search_tokens`, `chain_rpc_request`, `fund` (Solana Pay), `send` and `swap` accept `chain: solana`, with `fund`, `send` and `swap` gated by server switches; `sign`, `send_calls` and x402 do not, and headless sessions get Solana reads only. Solana sends and swaps are approved in the user's Base Account, which shows the quote and fees; confirm the outcome by matching the transaction in `get_transaction_history` on `chain: solana` after `get_request_status` returns `signed`. Add `solana` to the supported-chains table and note that only sessions approved from a Base auth keys.coinbase.com session carry `baseAccount.solana`, while agent wallets carry their own Solana address.
- Rework the `wallet-mcp` approval flow: in CLI harnesses, auto-open only the Wallet MCP `approvalUrl`, passed as one quoted argument, then poll `get_request_status` on a backoff without waiting for the user. Name the real statuses, keep polling EVM `signed` until `completed` or `failed`, report a signature for `sign`, and add Solana matching and stop rules. Align `tone.md` and the plugins that said to poll only after the user acts.
- Bump every distribution to 0.0.2.

## 0.0.1 — Unreleased
Expand Down
13 changes: 10 additions & 3 deletions skills/wallet-mcp/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Wallet MCP Skill"
description: "Wallet MCP — gives your AI assistant access to a Coinbase Wallet Account via the Wallet MCP server (wallet-mcp.coinbase.com). Wallet, portfolio, sending, swapping, signing, x402 payments, batched contract calls, and transaction history across Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, and Robinhood Chain."
description: "Wallet MCP — gives your AI assistant access to a Coinbase Wallet Account via the Wallet MCP server (wallet-mcp.coinbase.com). Wallet, portfolio, sending, swapping, signing, x402 payments, batched contract calls, and transaction history across Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, and Robinhood Chain, plus balances, transaction history, sending, swapping, and receiving funds on Solana."
name: wallet-mcp
version: 0.1.0
---
Expand All @@ -22,7 +22,7 @@ If Wallet MCP tools are available, load [references/tone.md](references/tone.md)

Keep it short. Do this once per session, before doing real work:

1. **Briefly mention what's available** — one or two sentences. The user has a Coinbase Wallet Account and can do things like check balances, send and swap tokens, sign messages, make x402 payments, and batch contract calls on Base (the default chain) and other supported chains, and (if installed) use third-party plugins for DeFi, swaps, and other onchain actions. Do not enumerate every tool — the agent discovers tools and plugins directly from the MCP.
1. **Briefly mention what's available** — one or two sentences. The user has a Coinbase Wallet Account and can do things like check balances, send and swap tokens, sign messages, make x402 payments, and batch contract calls on Base (the default chain) and other supported chains (on Solana: balances, history, sending, swapping, and receiving), and (if installed) use third-party plugins for DeFi, swaps, and other onchain actions. Do not enumerate every tool — the agent discovers tools and plugins directly from the MCP.

2. **Show this disclaimer verbatim** before proceeding:

Expand All @@ -44,9 +44,16 @@ Wallet MCP tools take a `chain` parameter. **Base is the default chain** — use
| BNB Chain | `bsc` |
| Avalanche | `avalanche` |
| Robinhood Chain | `robinhood-chain` |
| Solana | `solana` |
| Base Sepolia (testnet) | `base-sepolia` |

Not every tool covers every chain: x402 payments run on Base and Base Sepolia only, and `swap` is mainnet-only. The tool descriptions exposed by the MCP remain the source of truth for the current set and per-tool limits. Individual plugins may support only a subset of these chains — check the plugin's notice before acting.
Not every tool covers every chain: x402 payments run on Base and Base Sepolia only, `swap` is mainnet-only, and Solana covers reads, sends, swaps, and receiving only (below). The tool descriptions exposed by the MCP remain the source of truth for the current set and per-tool limits. Individual plugins may support only a subset of these chains — check the plugin's notice before acting.

**Solana.** `get_portfolio`, `get_transaction_history`, `search_tokens`, `chain_rpc_request` (read-only Solana methods), `fund` (a Solana Pay link for USDC or SOL), `send`, and `swap` accept `chain: solana`. `fund` on Solana works only while Solana funding is enabled on the server, and `send` / `swap` only while Solana writes are enabled; the tool descriptions say which. If a call says Solana isn't enabled yet, tell the user and don't retry. Solana addresses are base58 and case-sensitive: pass them exactly as returned. `get_wallets` lists the Base Account's Solana address as `baseAccount.solana`, and each agent wallet's as its `solana` field. The Base Account only has one if the user approved Wallet MCP, after Solana support shipped, from a keys.coinbase.com session that uses Base auth. If it's missing, Base Account Solana calls fail with a "no Solana address" error: ask the user to reconnect Wallet MCP once, then call `get_wallets` again. If it's still missing, Solana isn't available for the Base Account yet; don't keep asking. Reads and `fund` still work for an agent wallet's Solana address, and `search_tokens` and `chain_rpc_request` on Solana work without any address.

- **Send and swap on Solana** work in approval mode on Solana mainnet, from the Base Account's Solana address. Assets are `SOL`, `USDC`, or a base58 SPL mint address. Any other mint needs `decimals` (or `fromDecimals` / `toDecimals` for a swap); SOL and USDC don't, and a conflicting value is rejected. The `send` recipient must be a base58 Solana address: names (ENS, basenames, cb.id) aren't resolved on Solana. The user approves in their Coinbase Wallet Account (tool responses call it the Base Account), which prepares the transaction when they open the link, so the quote, network fees, and final amounts show there, not in the tool response. Don't quote fees or a swap rate the tool didn't return. If it can't be prepared (for example the balance doesn't cover amount and fees, or a swap has no route), the user sees why there.
- **Confirming a Solana send or swap.** After approval, `get_request_status` returns `signed`, which means the user approved and it's being sent, not that it landed. A declined request stays `pending` until it expires. Confirm the outcome by matching the transaction in `get_transaction_history` on `chain: solana`, and never start the same send or swap again while the outcome is unknown. The full polling and matching rules, including what `solanaState` means, are in [references/approval-mode.md](references/approval-mode.md).
- **Not on Solana yet:** `sign` (message signing), `send_calls`, and x402 payments. In headless sessions, Solana reads work for the session's agent wallet, but `send` and `swap` don't. Never route a Solana signature or batched call through them, and tell the user it isn't supported yet.

## Tools

Expand Down
4 changes: 2 additions & 2 deletions skills/wallet-mcp/plugins/aerodrome.md
Original file line number Diff line number Diff line change
Expand Up @@ -214,7 +214,7 @@ A staked position must be unstaked before `claim_fees`. ALM-managed positions ar
6. Normalize `[{from,to,data,value}]` into Wallet MCP `calls` (see [Submission](#submission)).
7. Submit with `send_calls({ "chain": "base", "calls": [...] })`.
8. Show the approval URL when appropriate.
9. Poll `get_request_status` only after the user acts in Coinbase Wallet Account.
9. Poll `get_request_status` until it reaches a final status.

If the CLI exits nonzero, do not try to salvage partial output. Read the error, adjust RPC/flags, and rerun.

Expand Down Expand Up @@ -290,7 +290,7 @@ Sugar CLI output is unsigned transaction JSON. Treat it as transaction preview m
1. `get_wallets` → set `$BASE_MCP_WALLET`; set `SUGAR_RPC_URI_8453`.
2. Run `sugar swap --chain=8453 --wallet=$BASE_MCP_WALLET --from-token=ETH --to-token=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 --amount=0.001 --use-decimals`.
3. Normalize stdout JSON into `calls`.
4. `send_calls(chain="base", calls=[...])`; show the approval URL; poll `get_request_status` after the user acts.
4. `send_calls(chain="base", calls=[...])`; show the approval URL; poll `get_request_status` until it reaches a final status.

**Buy AERO with 1 USDC**
1. `get_wallets` → `$BASE_MCP_WALLET`.
Expand Down
2 changes: 1 addition & 1 deletion skills/wallet-mcp/plugins/balancer.md
Original file line number Diff line number Diff line change
Expand Up @@ -225,7 +225,7 @@ For a **native-ETH** input (`wethIsEth: true`), omit the approval call(s) and pa
- **`value`** — hex wei. The SDK returns a bigint; convert (`"0x" + value.toString(16)`), or `0x0` when zero.
- **`chain`** — map the SDK `chainId` to the Wallet MCP chain string: `8453 → base`, `1 → ethereum`, `42161 → arbitrum`, `10 → optimism`, `43114 → avalanche`.

Then follow the standard approval flow ([../references/approval-mode.md](../references/approval-mode.md)): present the returned URL as **"Approve Transaction"**, auto-open it in the shell harness, then poll `get_request_status` once after the user confirms.
Then follow the standard approval flow ([../references/approval-mode.md](../references/approval-mode.md)): present the returned URL as **"Approve Transaction"**, auto-open it in the shell harness, then poll `get_request_status` until it reaches a final status.

## Example Prompts

Expand Down
6 changes: 3 additions & 3 deletions skills/wallet-mcp/plugins/bankr.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Use this endpoint when the user names a token by **address** (instead of picking
5. get_wallets → address (only if not already cached)
6. swap (Wallet MCP) with fromAsset=ETH (or USDC), toAsset=<tokenAddress>, amount=<human-readable amount>
7. Open the approvalUrl
8. get_request_status only after the user acts
8. Poll get_request_status until it reaches a final status (approval-mode.md)
```

Do not auto-buy. Always require an explicit "buy X amount of `<symbol>`" confirmation from the user before calling `swap` — the launches feed contains low-liquidity and meme tokens, and the swap is irreversible.
Expand Down Expand Up @@ -187,7 +187,7 @@ The actual purchase is a regular Wallet MCP `swap` call. Read the `swap` tool's
- `toAsset`: use the launch token contract address.
- `amount`: human-readable decimal amount of `fromAsset`. For 0.001 ETH pass `"0.001"`; for 5 USDC pass `"5"`.

The `swap` tool returns an `approvalUrl` and `requestId` like any other write call. Surface the URL to the user neutrally ("Approve Swap"), then poll `get_request_status` once they've acted. The full approval/polling pattern is in [`../references/approval-mode.md`](../references/approval-mode.md).
The `swap` tool returns an `approvalUrl` and `requestId` like any other write call. Surface the URL to the user neutrally ("Approve Swap"), then poll `get_request_status` until it reaches a final status (see `approval-mode.md`). The full approval/polling pattern is in [`../references/approval-mode.md`](../references/approval-mode.md).

## Example Prompts

Expand All @@ -202,7 +202,7 @@ The `swap` tool returns an `approvalUrl` and `requestId` like any other write ca
2. Take `launches[0]` (or the first one matching `status="deployed"`).
3. Show: symbol, name, address, deployer. Ask the user to confirm — "Buy 0.001 ETH of `<SYMBOL>` (`<address>`)?".
4. On confirmation: `swap` with `fromAsset=ETH`, `toAsset=<launch.tokenAddress>`, `amount="0.001"`, `chain="base"`.
5. Open the approval URL; poll `get_request_status` once the user has approved.
5. Open the approval URL; poll `get_request_status` until it reaches a final status.

**Buy 5 USDC of $WHOP**
1. `web_request` GET `https://api.bankr.bot/token-launches`.
Expand Down
2 changes: 1 addition & 1 deletion skills/wallet-mcp/plugins/brickken.md
Original file line number Diff line number Diff line change
Expand Up @@ -147,7 +147,7 @@ Ownership transfer is separate from `agentSetWallet`. After transfer, Brickken's
3. Require a scalar `txId` and exactly one transaction. Preserve `to`, `data`, and `value` exactly.
4. Validate that the quote network matches the operation network and that the payer holds the exact quoted asset. On Base Sepolia require Circle USDC `0x036CbD53842c5426634e7929541eC2318f3dCF7e`. Parse the exact decimal from `extra.displayPrice` as `maxPayment`.
5. Call Wallet MCP `initiate_x402_request` with method `POST`, the active Brickken environment's `/send-transactions` resource, the prepared body, and `maxPayment`. Do not switch environments between prepare and send.
6. Show the approval URL. Poll Wallet MCP `get_request_status` only after the user acts, then call `complete_x402_request(requestId)`.
6. Show the approval URL. Poll Wallet MCP `get_request_status` until it completes, then call `complete_x402_request(requestId)`.
7. Report confirmed only when Brickken returns `status: "confirmed"` and a transaction hash.
8. On `status: "pending"`, use Brickken `get_transaction_status` through exposed MCP tools or hosted HTTP API, or `brickken tx status`. Do not resubmit or pay the same `txId` again. Brickken's reconciliation settles after confirmation or releases on revert/authorization expiry.
9. To transfer an identity to the Coinbase Wallet Account, call Wallet MCP `get_wallets`, prepare `agentTransferOwnership` with that address as `newOwner`, and run a separate x402 approval.
Expand Down
6 changes: 3 additions & 3 deletions skills/wallet-mcp/plugins/clawnch.md
Original file line number Diff line number Diff line change
Expand Up @@ -298,7 +298,7 @@ Discovery + buy happy path:
4. get_wallets → address (only if not already cached)
5. swap (Wallet MCP) with fromAsset=ETH (or USDC), toAsset=<address>, amount=<human-readable>
6. Open the approvalUrl
7. get_request_status only after the user acts
7. Poll get_request_status until it reaches a final status (approval-mode.md)
```

Do not auto-buy. Always require an explicit "buy X amount of `<symbol>`"
Expand Down Expand Up @@ -414,7 +414,7 @@ too old", "sender mismatch", etc.).

Three submission shapes, all on `chain: "base"` (the chain string, not the
numeric chainId). Every write returns an `approvalUrl` + `requestId`; surface
the URL neutrally and poll `get_request_status` only after the user acts —
the URL neutrally and poll `get_request_status` until it reaches a final status —
see [approval-mode.md](../references/approval-mode.md).

**Buys → `swap`.** Read the `swap` tool's own parameter descriptions from the
Expand Down Expand Up @@ -470,7 +470,7 @@ dead address, `value: "0x0"`, amount in wei (whole tokens × 10^18).
2. Take `tokens[0]`. Show: symbol, name, address, current price, 24h volume.
3. Ask the user to confirm — "Buy 0.001 ETH of `<SYMBOL>` (`<address>`) at ~$<price>?".
4. On confirmation: `swap` with `fromAsset=ETH`, `toAsset=<token.address>`, `amount="0.001"`, `chain="base"`.
5. Open the approval URL; poll `get_request_status` once the user has approved.
5. Open the approval URL; poll `get_request_status` until it reaches a final status.

**Buy 5 USDC of CLAWNCH**

Expand Down
14 changes: 7 additions & 7 deletions skills/wallet-mcp/plugins/flaunch.md
Original file line number Diff line number Diff line change
Expand Up @@ -258,8 +258,8 @@ Response:
10. Show the transaction summary and ask for explicit confirmation before calling `send_calls`.
11. Call Wallet MCP `send_calls` with the returned `input`.
12. Surface the approval URL as "Approve Transaction".
13. Wait for the user to say they approved or rejected the transaction.
14. Call Wallet MCP `get_request_status` once after the user acts and report the confirmed result.
13. Open the approval link and poll Wallet MCP `get_request_status` without waiting for the user (see `approval-mode.md`).
14. Report the confirmed result once the status is final.

Do not submit launches silently. Do not report success until Wallet MCP request status confirms completion.

Expand All @@ -272,7 +272,7 @@ Do not submit launches silently. Do not report success until Wallet MCP request
5. Warn about low liquidity, slippage, and user-supplied metadata.
6. On explicit confirmation, call Wallet MCP `swap` with `chain: "base"`, a funding asset such as `ETH` or `USDC`, the token contract address, and a human-readable decimal amount.
7. Surface the approval URL as "Approve Transaction".
8. Poll Wallet MCP request status only after the user says they acted.
8. Poll Wallet MCP request status until it reaches a final status.

### Swap a token by contract address

Expand All @@ -284,7 +284,7 @@ Do not submit launches silently. Do not report success until Wallet MCP request
6. Warn about low liquidity and slippage. Require explicit confirmation before calling `swap`.
7. Call Wallet MCP `swap` with `chain: "base"` and the human-readable decimal `amount`.
8. Surface the approval URL as "Approve Transaction".
9. Call `get_request_status` once after the user acts and report the final transaction status.
9. Poll `get_request_status` until it reaches a final status and report it.

## Submission

Expand Down Expand Up @@ -373,7 +373,7 @@ The token contract address can come from Flaunch discovery or direct user input.
5. Call `POST https://mcp.flaunch.gg/v1/base/launch/prepare`.
6. Ask the user to confirm sending the returned transaction.
7. Call Wallet MCP `send_calls` with the returned `input`.
8. Surface the "Approve Transaction" link and poll request status only after the user acts.
8. Surface the "Approve Transaction" link and poll request status until it reaches a final status.

**Show me the newest Flaunch coins**

Expand All @@ -388,7 +388,7 @@ The token contract address can come from Flaunch discovery or direct user input.
3. Warn about low liquidity and slippage.
4. Ask the user to confirm: "Buy 0.001 ETH of <symbol> (<address>)?"
5. On confirmation, call Wallet MCP `swap` with `fromAsset="ETH"`, `toAsset="<token contract address>"`, `amount="0.001"`, and `chain="base"`.
6. Surface the "Approve Transaction" link and poll request status only after the user acts.
6. Surface the "Approve Transaction" link and poll request status until it reaches a final status.

**Buy a token by contract address**

Expand All @@ -397,7 +397,7 @@ The token contract address can come from Flaunch discovery or direct user input.
3. Ask the user to confirm the funding asset and amount.
4. Warn about low liquidity and slippage.
5. Call Wallet MCP `swap`.
6. Surface the approval URL and poll only after the user acts.
6. Surface the approval URL and poll until it reaches a final status.

## Risks & Warnings

Expand Down
2 changes: 1 addition & 1 deletion skills/wallet-mcp/plugins/gmgn.md
Original file line number Diff line number Diff line change
Expand Up @@ -285,7 +285,7 @@ If `data.tx.approve_txs` is empty (native ETH input), omit the approval call and
}
```

Call `send_calls("base", calls)`, then `get_request_status` only after the user acts on the approval link.
Call `send_calls("base", calls)`, then poll `get_request_status` until it reaches a final status (see `approval-mode.md`).

---

Expand Down
2 changes: 1 addition & 1 deletion skills/wallet-mcp/plugins/kyberswap.md
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@ Chain IDs: base=8453, ethereum=1, arbitrum=42161, optimism=10, polygon=137, bsc=
- **ERC-20 tokenIn** → `[approval_call, swap_call]` — always include approval, no allowance check needed.
- **USDT on Ethereum** — if existing allowance is non-zero, prepend a zero-approval call before the real approval.
8. `send_calls(chain, calls)` → `approvalUrl`, `requestId`.
9. Present `approvalUrl` to the user. Do not auto-approve. Call `get_request_status(requestId)` only after the user acts.
9. Present `approvalUrl` to the user. Do not auto-approve. Poll `get_request_status(requestId)` until it reaches a final status (see `approval-mode.md`).

## Submission

Expand Down
2 changes: 1 addition & 1 deletion skills/wallet-mcp/plugins/o1-exchange.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ Extract fields by position:
5. [RLP-decode](#rlp-decoding) each `transactions[].unsigned` hex string to extract `to`, `data`, and `value`. Map `networkId` to chain string (`8453` → `"base"`, `56` → `"bsc"`).
6. `send_calls(chain, calls)` → `approvalUrl` + `requestId`.
7. Present the approval URL as an "Approve Transaction" link to the returned `approvalUrl`. In CLI harnesses, also auto-open the link. Do not approve on the user's behalf.
8. After the user confirms approval, call `get_request_status(requestId)` once.
8. Poll `get_request_status(requestId)` until it reaches a final status (see `approval-mode.md`).

### Permit2 swap (Base only)

Expand Down
Loading
Loading