Meanwhile, five categories of agentic payment infrastructure are shipping in parallel — checkout protocols, authorization layers, micropayment rails, identity frameworks, and issuing tools — and none of them compose cleanly.

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

The Solution

MCP Brasil gives AI agents typed tools to interact with Brazilian APIs and agentic payment protocols. Each server wraps a real service — payments, fiscal, logistics, messaging, banking, ERP, crypto, and now agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal)
  → 📦 Agent generates shipping label (Melhor Envio)
  → 📱 Agent sends tracking via WhatsApp (Z-API)
  → 📊 Agent records in ERP (Omie)
  → 🏦 Agent reconciles balance (Stark Bank)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

"The bridge looks more like middleware than a protocol." — The middleware is MCP.

Three new servers that bridge the emerging agentic payment stack:

The Autonomy Spectrum

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

... [View full README on GitHub](https://github.com/codespar/mcp-dev-brasil#readme)