Mercado Pago
🌎 LATAMPayments
Checkout Pro, Pix, boleto, card. Marketplace split. The LatAm-wide payments gateway that actually works across borders.
Developers · Servers
Explore integrations for payments, banking, invoicing, logistics and more in Latin America.
132 servers · 2,536 tools · 8 regionsMIT-licensed packages on npm
🌎 LATAMPayments
Checkout Pro, Pix, boleto, card. Marketplace split. The LatAm-wide payments gateway that actually works across borders.
🇧🇷 BRBanking
Official Pix API from Banco Central do Brasil. Instant transfers, QR codes, DICT key lookup, and devolution flows.
🌐 GLOBALProtocols
Agentic Commerce Protocol by Stripe. AI agent checkout, payment delegation, product discovery, and cart management.
🇧🇷 BRFiscal
NF-e/NFS-e emission as a service — no cert installation, no XML assembly. Companies, webhooks, and CC-e (Carta de Correção) included. Full doc URL access for DANFE, PDFs, and XMLs.
🇧🇷 BRLogistics
Multi-carrier shipping: quote Correios, Jadlog, Loggi, and 10+ carriers. Generate labels, track packages, and manage agencies.
🇧🇷 BRPayments
Brazilian payments infrastructure: Pix, boleto, card and native split of receivables. Your agent creates charges, reconciles settlements, and splits payouts across partners — in a single MCP call.
🇧🇷 BRPayments
Billing automation, Pix, boleto, credit card, and subscriptions. Your agent manages customers, creates recurring charges, and tracks payment status.
🇧🇷 BRPayments
Payment gateway with card, Pix, and boleto. Receivables anticipation and risk management built for Brazilian marketplaces.
🇧🇷 BRPayments
Full payment stack: orders, Pix, boleto, and credit card. Your agent creates charges and manages the complete payment lifecycle.
🇧🇷 BRPayments
Brazil's largest card acquirer — authorization, capture, boleto, and recurrent payments on Cielo's rails. For enterprise orchestration, tokenization vault, and marketplace onboarding, use Braspag (Cielo's orchestration arm) separately.
🇧🇷 BRPayments
Open banking, Pix, and card acquiring. TON integration, partner tags, and real-time settlement for Brazilian commerce.
🇧🇷 BRPayments
Direct Pix via BCB, charges, and carnets. One of the first fintechs authorized as a PSP by the Brazilian Central Bank.
🇧🇷 BRPayments
Subscription billing with Pix, boleto, and credit card. Your agent creates invoices, manages customers, and handles recurring charges.
🇧🇷 BRPayments
Recurring billing engine with dunning, retry logic, and multi-gateway. Your agent manages subscription lifecycles and reduces churn.
🇧🇷 BRPayments
Pix, boleto, TED, bill payments, and mobile top-ups. Your agent processes utility payments and moves funds across Brazilian banks.
🇧🇷 BRPayments
Cross-border payments for LatAm: local payment methods, FX conversion, and mass payouts. Your agent sells globally and settles locally.
🇲🇽 MXPayments
Mexican payment gateway: cards, OXXO cash deposits, and SPEI bank transfers. Your agent charges in MXN with local payment methods.
🇨🇴 COPayments
Colombian payment gateway by Bancolombia: cards, PSE bank transfers, and Nequi wallet. Your agent accepts COP with local checkout.
🌎 LATAMPayments
LatAm cross-border payments through a single API. 15+ countries, local methods (Pix, OXXO, PSE, SPEI, boleto) + cards. The one call, multi-country abstraction per-country PSPs can't provide on their own.
🇧🇷 BRPayments
Santander-owned Brazilian acquirer — #3 BR and #1 BR ecommerce. Credit, debit, Pix, boleto + marketplace seller onboarding and split. Closes the big-four BR acquirer quadrant.
live, beta, alpha: the stage CodeSpar gives each server in its catalog, the same label its page and /api/servers show. It is not an uptime or certification signal, and a package on npm does not prove an integration in production.
prerelease: the npm version the server page installs is a prerelease.
deprecated on npm: npm marks the package deprecated; its page shows the notice and no install command.
Logos identify the provider each server calls. They do not imply partnership or endorsement.
Every server is an npm package. Run it with npx, or add it to your MCP client config.
Works with any MCP-compatible client
Each server calls its provider with your own credentials, set as environment variables. The MIT license covers the package, not the provider's service. The example is Pix BCB v0.2.2. Its page lists the 4 variables it reads and the config for each client.
Pix, NF-e, PSE in Colombia, SPEI in Mexico, Chilean eInvoicing - the regulatory infrastructure here doesn't exist on Stripe or QuickBooks. We cover the systems that actually power the local economy.
Stripe ACP has a current MCP server. x402 payments go through the spend route of a consumer mandate, called from the SDK with cs.api, which pays an x402-priced URL in USDC within the mandate's per-transaction cap. The MCP packages for UCP, AP2 and x402 are deprecated on npm and stay listed for reference only, with no install recommended. The protocols themselves are not deprecated.