Connect Claude — or any MCP-compatible agent — to your WalletPlug account. It can check balances, send payouts and issue refunds through six payment tools, while scoped keys, spending limits and human approval keep you in control of every unit of money.
Free with every merchant account · test mode included · revoke any key any time
MCP is the open standard that lets AI assistants use real tools. Instead of copying numbers into a dashboard, your agent talks to WalletPlug directly — over one endpoint, in a language every MCP client already speaks.
EnglishJSON-RPC 2.0Standard request and response format — initialize, list tools, call tools. No SDK required.
Streamable HTTPPlain HTTPS transport. Works from Claude, server-side agents, and anything that can POST JSON.
OpenAPI includedPrefer REST? The same capabilities are described at api/v1/openapi.json for non-MCP integrations.
Create a scoped key in your dashboard, paste this connector config into your MCP client, and your agent is live. Use a wp_test_ key first to rehearse without touching real funds.
Every tool is gated by its own permission scope on the key — an agent can only do what you ticked.
get_balanceRead wallet balances across every currency on the account.
scope · balance:readcreate_payoutSend money to a saved withdraw account — capped by per-transaction and daily limits.
scope · payouts:createcreate_refundCredit funds back to a customer wallet in one call.
scope · refunds:createlist_withdraw_accountsSee the payout destinations already registered on the account.
scope · payouts:readregister_withdraw_accountAdd a new payout destination for later transfers.
scope · customers:writeget_audit_logsRead the full trail of what the agent has done, straight from the API.
scope · logs:readAutonomy is useful; unbounded autonomy is a liability. Every agent key carries its own safety rails.
Keys start with wp_live_ or wp_test_ and carry only the permissions you tick. Your primary API keys are never exposed to an agent, and any key can be revoked instantly.
Set a per-transaction cap and a daily cap per key. A payout over either limit is refused before any money moves.
Set an approval threshold: anything above it is held as pending until a person approves it in the dashboard.
Every call is logged with key, action, amount, IP and request ID. Signed webhooks (payout.completed, payout.pending_approval, refund.completed) notify your systems in real time.
In Dashboard → AI Agent Payment API, tick the scopes, set limits and an approval threshold.
Add the MCP config to Claude or your agent framework with the key in the headers.
The agent lists the six tools and calls them — each call checked against scopes and limits.
Watch the audit log live, approve large payouts, and receive signed webhooks as things happen.
An agent settles suppliers or creators on schedule — small amounts flow automatically, large ones queue for approval.
Ask Claude for balances across currencies, recent agent activity, or to prepare a batch of payouts for review.
A support agent resolves a dispute and issues the refund in the same conversation — logged and capped.
An agent watches balances and audit logs, flags anomalies, and never needs more than read scopes to do it.
MCP is an open standard that lets AI assistants like Claude call external tools over a simple JSON-RPC connection. WalletPlug runs an MCP server that exposes payment tools, so an agent can act on your account within the limits you set.
Claude and any MCP-compatible client. The server speaks standard JSON-RPC 2.0 over HTTPS at https://walletplug.com/api/v1/mcp — anything that implements the protocol works.
Each agent uses its own scoped API key created from your dashboard, sent in the X-API-Key header along with your X-Merchant-Key. Keys carry only the permissions you tick and can be revoked at any time.
Yes — a per-transaction cap and a daily cap per key, plus an approval threshold that holds larger payouts for human review before any money moves.
Six tools: get_balance, create_payout, create_refund, list_withdraw_accounts, register_withdraw_account and get_audit_logs. Nothing else is exposed.
Every call is written to an audit log with the key used, action, amount, IP and request ID — and signed webhooks notify your systems when payouts complete or wait for approval.
Yes. Create a wp_test_ key and use the same endpoint with X-Environment: test to rehearse flows before an agent touches live funds.
Create a scoped key, paste one config block, and let Claude handle the money ops you shouldn’t be doing by hand.