Check execution mode first
These protocol recipes describe approval-based execution unless a current tool explicitly supports the operation in your autonomous session. A plugin returning unsigned calldata does not establish that its contracts, assets, approvals, or chain satisfy autonomous spending policy. In approval mode, show the approval link and wait before checking status. In eligible autonomous mode, use only supported bounded actions, provide required idempotency keys, and inspect returned status without inventing an approval step. Refusal is not automatic fallback. See agent spending controls and retry guidance.Custom plugins
A plugin is a markdown spec that teaches your assistant how to call an external API, run a CLI, or call another MCP server, translate the response into a Wallet MCP action, and execute it through tools likesend_calls, swap, or sign. The calldata-based native plugins follow the same shape. This page shows how to write your own send_calls-based plugin.
When you need one
Write a plugin when your protocol has an HTTP tx-builder, a CLI/SDK that can produce unsigned transactions, or its own MCP server. CLI/SDK-only plugins require a harness with shell access; hybrid plugins can prefer a CLI in coding harnesses and fall back to an MCP server in chat-only Claude or ChatGPT consumer apps.Anatomy of a plugin
Asend_calls-based plugin file contains four sections:
1
Onboarding Gate
A
STOP notice that forces the assistant to complete Wallet MCP onboarding and execution-mode checks before doing anything else. Fetch the executing wallet address only when preparation requires it.2
Read Endpoints
Document the GET endpoints or CLI commands that return state — balances, positions, market data — and the units they use.
POST endpoints are not supported in Claude and ChatGPT consumer apps.
3
Prepare Endpoints
Document the endpoints, CLI commands, or MCP tools that return unsigned calldata. State the exact response shape so the assistant knows which fields map to
to, value, and data.4
send_calls Mapping
Show the assistant how to convert the prepare response into the
calls array passed to send_calls.Wallet MCP’s
web_request tool can make GET and POST requests only to allowlisted partner APIs. Native plugins that rely on HTTP hosts may be allowlisted for the hosted MCP, while CLI-only plugins require shell access unless they document an MCP fallback. Custom plugin hosts usually are not allowlisted, so custom plugins should expose GET endpoints only if they need to remain usable in Claude and ChatGPT consumer apps.How it works
Build it
1. Pick a response shape
Your prepare endpoint should return a single object with the fieldssend_calls needs. Two common shapes:
Envelope (Avantis-style):
Envelope Response
Ordered Batch Response
send_calls executes them atomically in one approval.
2. Write the plugin spec
Use this template asplugins/my-protocol.md in your skill, or as an .mdx page if you’re publishing docs.
plugins/my-protocol.md
3. Wire it into send_calls
The contract between your prepare endpoint and Wallet MCP is exactly this object:
send_calls Payload
base, base-sepolia (only if explicitly enabled), ethereum, optimism, polygon, arbitrum, bsc, or avalanche) when calling send_calls. If a prepare endpoint returns a numeric or hex chainId, map it to the corresponding chain name before calling Wallet MCP. value defaults to 0x0 if omitted. The assistant calls send_calls once with the full batch — the user approves once, and all calls execute atomically.