1inch-walletconnect

Files (1)

• SKILL.md

SKILL.md (first lines)

# WalletConnect

Use the MCP tool **`walletconnect`**. The server never holds private keys — the user approves every request in their wallet.

## Actions

- `connect` — returns pairing QR resource + `wc:` URI (+ mobile deeplinks). Set `pairingTarget`: `eth` | `solana` | `both`.
- `status` — poll until connected (pending is success while waiting).
- `sign` / `send_transaction` — after session is active.
- `accept_terms` — when required for anonymous write flows.
- `disconnect` — end session.

## Execute mode for other tools

Once a session is active, `swap`, `orderbook` (build), and `aqua` write actions **default to `execute: true`** — approvals, EIP-712 signing, and transaction sends all go through the connected wallet, and the user just approves each prompt in their wallet app. This is the recommended flow: offer to connect the wallet before any signing task instead of asking for keys or manual signing. Pass `execute: false` on those tools to opt out and receive calldata / typed data instead.

Pairing QR resource template: `file://1inch-mcp/walletconnect/pairing-qr/{token}`.

## Tips

- Do not call `connect` again just to refresh while pending with the same `pairingTarget`.
- Many mobile wallets reject EVM+Solana together — start with one namespace.
- QR expires ~10 minutes.

From 1inch/1inch-ai, MIT.

More from 1inch/1inch-ai