Mcp Rapyd

io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026

MCP server for Rapyd — global collect + disburse across 100+ countries, cash pickup, wallets

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server for Rapyd that lets an assistant create and manage global payments, payouts, and managed wallets across 100+ countries.

What you can do
Create, retrieve, list, update and cancel payments, including hosted checkout pages and refunds, and manage saved payment methods on customers. Create, retrieve, list, confirm and cancel payouts (disbursements) to beneficiaries. Create, retrieve, list and update managed wallets, verify wallet contacts, and transfer funds between wallets. Look up supported collect and payout methods by country and currency.
When to use it
Useful when an assistant needs to work with Rapyd's global payment rails: cross-border collection and disbursement, cash pickup for unbanked recipients, or managed sub-wallets for marketplaces and creator payouts. Prefer a LatAm-focused provider when deep local coverage in Latin America is the main requirement.
Requirements
Runs locally via npx as a stdio process (Node.js required); an HTTP mode is available for server-to-server testing. Needs a Rapyd account with RAPYD_ACCESS_KEY and RAPYD_SECRET_KEY set, and optionally RAPYD_ENV to choose sandbox (default) or production. Network access to the Rapyd API endpoints.
Before you install
The server moves real money: payments, refunds, payouts, wallet transfers and confirmations are live financial actions, and production mode uses the live Rapyd API. RAPYD_SECRET_KEY is a signing secret and should be kept private; the access key is sent in request headers. Test in sandbox first, and note that the README mentions a separate enterprise offering for governance and budget limits.

Installation

In SourceWeft

  1. Open Mcp Rapyd in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@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)

ToolPurpose
create_checkout_pageCreate a Rapyd hosted checkout page.
create_paymentCreate a direct payment with a fully-specified payment_method.
get_paymentRetrieve a payment by Rapyd payment id (payment_xxx).
cancel_paymentCancel a payment that has not yet been captured/completed.
create_refundRefund a completed payment.
create_payoutCreate a payout (disbursement) to a beneficiary.
get_payoutRetrieve a payout by Rapyd payout id (payout_xxx).
confirm_payoutSecond step of Rapyd's two-step payout approval.
list_payment_methods_by_countryList all inbound (collect) payment methods Rapyd supports for a given country + currency.
list_payout_methods_by_countryList all outbound (disburse) payout method types Rapyd supports for a given beneficiary country.
create_walletCreate a Rapyd managed wallet (user) for an end user.
list_paymentsList payments with optional filters.
update_paymentUpdate metadata / descriptor / receipt details on an existing payment.
create_payment_methodSave a reusable payment method (card token, bank account, wallet) against a Rapyd customer.
delete_payment_methodRemove a saved payment method from a Rapyd customer.
list_payoutsList payouts (disbursements) with optional filters.
cancel_payoutCancel a payout that is still in 'Created' state (before confirm_payout releases funds).
get_walletRetrieve a Rapyd ewallet (user) by id.
update_walletUpdate profile fields on a Rapyd ewallet (user).
list_walletsList Rapyd ewallets under the merchant account.
wallet_contact_verifySubmit a verification token (usually received via SMS/email) to verify a wallet contact's identity.
transfer_between_walletsMove 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:

toSign    = http_method_lowercase + url_path + salt + timestamp + access_key + secret_key + body_stringhmac_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:

Content-Type: application/jsonaccess_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

RequirementChoose
LatAm depth (Pix, OXXO, PSE, SPEI, Boleto)dLocal
Global reach (Asia, Africa, Europe + LatAm)Rapyd
Cash pickup for unbanked recipientsRapyd
Managed wallet infrastructureRapyd
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

Source: packages/payments/rapyd/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts