Charging via Pix, issuing an NFe, generating a shipping label, sending tracking over WhatsApp and recording it in an ERP are five different vendors with five different auth patterns — and this makes them five MCP servers with one interface. Start with @codespar/mcp-brasil-api if you want to see the shape of it without signing up for anything: CEP and CNPJ lookups work with no key.
A catalog of MCP servers wrapping real Latin American providers, plus four agentic payment protocols, each published as its own npm package.
- 127 MCP servers for LATAM commerce across Brazil, Mexico, Argentina, Colombia, Chile and Peru, live in the official MCP Registry
- Payments — @codespar/mcp-asaas for Brazilian billing and Pix, @codespar/mcp-mercado-pago for LATAM payments, and more
- Fiscal — @codespar/mcp-nuvem-fiscal for NFe and NFSe
- Logistics — @codespar/mcp-melhor-envio for multi-carrier shipping
- Messaging and ERP — @codespar/mcp-z-api for WhatsApp, @codespar/mcp-omie for ERP
- Banking — @codespar/mcp-stark-bank, plus contract-gated providers such as Itaú and BTG published under an alpha tag
- Agentic payment protocols — @codespar/mcp-stripe-acp with 24 tools, @codespar/mcp-ucp with 20, @codespar/mcp-ap2 with 22 in alpha, and @codespar/mcp-x402 with 10 for HTTP micropayments in USDC
- @codespar/mcp-brasil-api for CEP and CNPJ lookups, which needs no key at all
Npx and a client config entry per server you want — each provider is its own package with its own credentials, for example STRIPE_API_KEY for the Stripe ACP server or ASAAS_API_KEY with ASAAS_SANDBOX for Asaas. Contract-gated bank providers install with an @alpha tag. BrasilAPI and BCRA are public and need no key.
One command plus a key — npx @codespar/mcp-brasil-api, then supply credentials