Connect an MCP client
Use the API-key connection for clients that support custom authorization headers.
Connection details
Endpointhttps://payloadpier.com/api/mcp
Authorization headerAuthorization: Bearer YOUR_API_KEY
Create a scoped API key and store it in your client’s secret settings. Keep it out of tool arguments and public configuration.
Available tools
| Tool | Scope | Usage charge |
|---|---|---|
compare_supplier_prices | supplier-price | One included unit or $0.25 prepaid |
get_account_balance | account-read | None |
get_referral_link, claim_referral | referrals | None |
Test safely
Start with get_account_balance. Before a paid comparison, check your funding and key cap. Keep a durable operation_id; a recorded repeat returns a usage reference without a second charge, but does not replay the result.
OAuth clients and request limits
OAuth client discovery is still being verified. Use API-key MCP when supported. Existing provider accounts can manage explicit tool delegations in MCP authorization settings.
The MCP endpoint allows 60 attempts per source IP per fixed UTC minute; the account-wide limit also applies. HTTP 429 includes Retry-After. Included subscription units and prepaid spending caps apply across REST and MCP.