MCP Dev Brasil — 37 Servers for Agentic Commerce

AI agents can write code, analyze data, and chat. But they can'toperate a business— collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — andnone of them compose cleanlywith each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps.Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop) → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io) → 📦 Agent generates shipping label (Melhor Envio / Skydropx) → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud) → 📊 Agent records in ERP (Omie / Bling / Tiny) → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Four servers that bridge the emerging agentic payment stack:

Each protocol sits at a different level of agent autonomy:

Human-in-loop ◄──────────────────────────────► Fully autonomous ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ ACP │ │ UCP │ │ AP2 │ │ x402 │ │ Stripe │ │ Google │ │ Google │ │Coinbase │ └─────────┘ └─────────┘ └─────────┘ └─────────┘ User confirms Commerce User sets No user. every purchase lifecycle rules, agent Machine-to- in-chat managed acts within machine at by agent budget/scope HTTP layer

┌─────────────────────────────────────────────┐ │ Application Layer ACP / UCP │ Chat UX, product discovery ├─────────────────────────────────────────────┤ │ Authorization Layer AP2 / Mandates │ Spend limits, audit trails ├─────────────────────────────────────────────┤ │ Tool Layer MCP ◄── WE ARE │ Standardized agent tools ├─────────────────────────────────────────────┤ │ Settlement Layer x402 / Pix / Card │ On-chain or traditional rails └─────────────────────────────────────────────┘

MCP Dev LATAM sits at the Tool Layer— the middleware that connects every application, authorization, and settlement protocol through one interface.

Agent needs to buy something ├── Full commerce? → Google UCP (search → cart → checkout → delivery) ├── Retail checkout? → Stripe ACP (create_checkout → complete_checkout) ├── API micropayment? → x402 (pay_request → USDC $0.001 → data returned) ├── Agent-to-agent? → AP2 (authorize_payment → execute_payment) └── LATAM merchant? → Asaas / Mercado Pago / Conekta / Wompi / etc. All via MCP. Same interface. One agent.

Add to~/.config/claude/claude_desktop_config.json:

Then ask your agent:"What is the address for CEP 01001-000?"or"Look up CNPJ 00.000.000/0001-91".

This is what makes the LATAM catalog different — not individual connectors, but acomplete business workflowacross verticals:

AI Agent (Claude, ChatGPT, Cursor) ↕ MCP Server (this repo) ↕ LATAM API / Agentic Protocol (Stripe ACP, x402, Asaas, Mercado Pago, NFe.io, etc.)

- Exposestyped toolswith input/output schemas
- Handlesauthentication(OAuth, mTLS, API keys, Basic Auth, JWT-RSA, signed requests)
- Supportsdual transport— stdio (default) andStreamable HTTP(--httpflag)
- Compatible withClaude Managed Agentsvia MCP Connector
- Supportssandbox modefor safe testing
- Returnsstructured JSONresponses

Any server can run as an HTTP server for remote/cloud use:

# stdio (default — local, Claude Desktop, Cursor, Claude Code) npx @codespar/mcp-asaas # HTTP (remote — Managed Agents, cloud deployments) npx @codespar/mcp-asaas --http # or MCP_HTTP=true npx @codespar/mcp-asaas

HTTP mode exposes/mcp(Streamable HTTP) and/health(status check).

About a third of the catalog ships under thealphanpm dist-tag. These packages have correct tool schemas and auth flow, but the endpoint paths are best-guesses — typically because the provider's developer portal is contract-gated (BR public banks, AR central authority APIs, MX bank-transfer providers). They're flagged withTODO(verify)in source.

Stable packages (the majority) install with the default tag:

Individual MCP servers are useful. Orchestrating many with governance is powerful.That's what CodeSpar does.

MIT — use freely in commercial and open source projects.

Transaction-complete hotel booking over MCP — 300K+ properties, real hotel confirmation numbers, loyalty points, secure checkout. Hotels are merchant of record. Builders set their own booking fee via Stripe Connect. Built on proven distribution infrastructure.

Static MCP discovery card for x402 spend-policy, paid MCP launch guidance, seller checkout repair, and agent-payment safety APIs.

Fully autonomous AI agent commerce — USA-built, 1.75% fee (11x cheaper than ACP). 15 tools for escrow, reputation, spending limits, collateral staking, referrals. ERC-8004 on 4 chains. $1K insurance. Stripe fiat + crypto. npx @synmerco/mcp-server

AI agent commerce marketplace — register, list services, buy and sell capabilities with real payments via Stripe.

Mercado Pago's official MCP server, offering tools to interact with our API, simplifying tasks and product integration.

The PayPal Model Context Protocol server allows you to integrate with PayPal APIs through function calling. This protocol supports various tools to interact with different PayPal services.

A Model Context Protocol (MCP) server for square

Integrate AI tools and agents with Cashfree's Payment Gateway, Payouts, and SecureID APIs.

A read-only MCP server for querying live data from Square using the CData JDBC Driver.