This MCP server provides Model Context Protocol integration for Rapyd, covering global collect and disburse operations. It targets payment flows across 100+ countries and includes support for cash pickup and managed wallets via a single API spanning Asia, Africa, Europe, the Middle East, and LatAm.

🛠️ Key Features

Global collect + disburse across 100+ countries
Cash pickup networks, including OXXO Pay and 7-Eleven, plus country-specific cash options
Managed wallets, where the merchant holds a master

🚀 Use Cases

Collecting and disbursing funds worldwide through Rapyd using one API
Supporting unbanked recipients via cash pickup
Using managed wallets for merchant-controlled payout handling

⚡ Developer Benefits

MCP compatibility for building AI agent tooling around Rapyd
Cross-region payments coverage (Asia, Africa, Europe, Middle East, LatAm) via Rapyd

⚠️ Limitations

The provided documentation excerpt does not list tool names, toolCount, or specific MCP endpoints

@codespar/mcp-rapyd

MCP server for Rapyd — global collect + disburse across 100+ countries.

Rapyd is the global counterpart to dLocal. Where dLocal is LatAm-deep (15+ countries, Pix/OXXO/PSE/SPEI), Rapyd is worldwide-wide: Asia, Africa, Europe, the Middle East, and LatAm via a single API — and crucially covers two categories dLocal doesn't:

Cash pickup — OXXO Pay, 7-Eleven, and country-specific cash networks for unbanked recipients
Managed wallets — the merchant holds a master account and provisions sub-wallets per end user (marketplace balances, creator payouts, cross-border P2P without opening a bank account per user)

Use dLocal when LatAm depth is the requirement. Use Rapyd when global reach, cash pickup, or wallet infrastructure is the requirement.

Tools (22)

Tool	Purpose
`create_checkout_page`	Create a Rapyd hosted checkout page.
`create_payment`	Create a direct payment with a fully-specified payment_method.
`get_payment`	Retrieve a payment by Rapyd payment id (payment_xxx).
`cancel_payment`	Cancel a payment that has not yet been captured/completed.
`create_refund`	Refund a completed payment.
`create_payout`	Create a payout (disbursement) to a beneficiary.
`get_payout`	Retrieve a payout by Rapyd payout id (payout_xxx).
`confirm_payout`	Second step of Rapyd's two-step payout approval.
`list_payment_methods_by_country`	List all inbound (collect) payment methods Rapyd supports for a given country + currency.
`list_payout_methods_by_country`	List all outbound (disburse) payout method types Rapyd supports for a given beneficiary country.
`create_wallet`	Create a Rapyd managed wallet (user) for an end user.
`list_payments`	List payments with optional filters.
`update_payment`	Update metadata / descriptor / receipt details on an existing payment.
`create_payment_method`	Save a reusable payment method (card token, bank account, wallet) against a Rapyd customer.
`delete_payment_method`	Remove a saved payment method from a Rapyd customer.
`list_payouts`	List payouts (disbursements) with optional filters.
`cancel_payout`	Cancel a payout that is still in 'Created' state (before confirm_payout releases funds).
`get_wallet`	Retrieve a Rapyd ewallet (user) by id.
`update_wallet`	Update profile fields on a Rapyd ewallet (user).
`list_wallets`	List Rapyd ewallets under the merchant account.
`wallet_contact_verify`	Submit a verification token (usually received via SMS/email) to verify a wallet contact's identity.
`transfer_between_wallets`	Move funds between two Rapyd ewallets (source_ewallet → destination_ewallet).

Install

bash

npm install @codespar/mcp-rapyd

Environment

bash

RAPYD_ACCESS_KEY="..."   # Public access key (sent in the access_key header)
RAPYD_SECRET_KEY="..."   # Secret key (used to sign requests; never transmitted)
RAPYD_ENV="sandbox"      # Optional. 'sandbox' (default) or 'production'

Base URLs:

sandbox → https://sandboxapi.rapyd.net
production → https://api.rapyd.net

Authentication

Every request is signed with HMAC-SHA256 per Rapyd's signature recipe:

code

toSign    = http_method_lowercase + url_path + salt + timestamp + access_key + secret_key + body_string
hmac_hex  = HMAC-SHA256(secret_key, toSign).digest('hex')
signature = Buffer.from(hmac_hex).toString('base64')   // hex → base64, not raw digest

Required headers on every request:

code

Content-Type: application/json
access_key:   <access_key>
salt:         <random 8-16 char string, unique per request>
timestamp:    <Unix seconds, within 60s of server time>
signature:    <computed per recipe above>
idempotency:  <unique per request>

The server handles salt, timestamp, signature, and idempotency generation automatically — you only configure RAPYD_ACCESS_KEY, RAPYD_SECRET_KEY, and (optionally) RAPYD_ENV.

Gotchas the server handles for you:

body_string is the compact JSON body with no whitespace, or "" when empty — never "{}".
url_path includes the query string when present.
http_method is lowercased in the signature string but UPPERCASE on the wire.

Run

bash

# stdio (default — for Claude Desktop, Cursor, etc)
npx @codespar/mcp-rapyd

# HTTP (for server-to-server testing)
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-rapyd

When to use Rapyd vs dLocal

Requirement	Choose
LatAm depth (Pix, OXXO, PSE, SPEI, Boleto)	dLocal
Global reach (Asia, Africa, Europe + LatAm)	Rapyd
Cash pickup for unbanked recipients	Rapyd
Managed wallet infrastructure	Rapyd
Single-country PSP (BR-only, MX-only)	Per-country server (Mercado Pago, Conekta, etc)

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

io.github.codespar/mcp-rapyd

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

@codespar/mcp-rapyd

Tools (22)

Install

Environment

Authentication

Run

When to use Rapyd vs dLocal

Enterprise

License

Install

Configuration

Related servers