Configuration reference
Every POLYPAY_* environment variable the MCP server reads.
All settings are environment variables, set in whichever config your client uses (see Install).
| Variable | Required | Default | What it does |
|---|---|---|---|
POLYPAY_WALLET_SEED | yes | — | The wallet seed used to sign payments. |
POLYPAY_NETWORK | no | testnet | testnet (free, for trying this out) or mainnet (real funds). |
POLYPAY_API_URL | no | https://api.polymitapay.com | Only relevant if you're running this against your own copy of PolyPay's backend, not the hosted one. |
POLYPAY_MAX_PER_CALL_XRP | no | no limit | Refuses any single call priced above this many XRP. |
POLYPAY_MAX_PER_CALL_RLUSD | no | no limit | Same, in RLUSD. |
POLYPAY_MAX_TOTAL_XRP | no | no limit | Refuses further XRP payments once this many have been spent since the server started. Resets on restart. |
POLYPAY_MAX_TOTAL_RLUSD | no | no limit | Same, in RLUSD. |
Especially on mainnet — without one, your agent can spend without a
ceiling. The interactive setup (npx @polymitapay/mcp) offers to
configure these for you; editing config by hand, just add whichever of
the four you want to the env block.
Choosing an asset per call
If a provider accepts both XRP and RLUSD, your agent can pass an optional
asset argument ("XRP" or "RLUSD") to polymitapay_call to choose which
one to pay with — it defaults to XRP. Paying in RLUSD opens the wallet's
RLUSD trust line automatically the first time it's needed.
Not yet built
POLYPAY_PROVIDERS — restrict which providers your agent can see and pay —
is planned but not implemented yet.