
MCP server integration
Lets an AI agent create deposit addresses, read payment logs and estimate fees over the public API.
Read the API quick startRequirements
- An MCP client that can start a stdio server, the Suawave MCP executable and a reachable gateway base URL.
- A payout wallet and public callback URL for creating a deposit address. Public tools need no API key.
Install and configure
- Install the Suawave MCP executable and configure your MCP client to start it over stdio.
- Pass the gateway URL with -base-url. Optionally pass -docs-dir to expose the API documentation as read-only resources.
- Use create_payment_address with a ticker, payout address and callback URL. Use payment_logs to inspect deposits for that callback URL.
- Use ticker_info, fee_estimate, convert, ticker_convert and qr_code for payment preparation. payment_status is hidden without a configured merchant credential.
What the buyer sees
The server returns structured tool results to your agent. Your application decides how to show the returned deposit address, amount and QR code to the buyer; the MCP server does not provide a checkout page.
Payment behavior
- Transport is newline-delimited JSON-RPC over stdio. HTTP transport, subscriptions and prompts are not implemented.
- The server does not expose administrative operations or create merchant payments. It reports rate-limit hints and never retries tool requests itself.