mcp-dev-brasil
37 MCP servers for agentic commerce and Brazilian services. Covers Stripe ACP, x402 (Coinbase), AP2 (Google), Google UCP, plus 14 traditional Brazilian payment rails, fiscal, banking, communication, logistics, ERP, identity, and crypto APIs. ~480 tools. Supports stdio and Streamable HTTP.
README
<p align="center"> <h1 align="center">MCP Dev LATAM 🌎</h1> <p align="center"> <strong>Every API your AI agent needs to run a business in Latin America.</strong><br> <em>Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 — plus 4 agentic payment protocols.</em> </p> <p align="center"> 57 MCP servers · 453 tools · 4 countries · MIT License </p> <p align="center"> <a href="https://codespar.dev/mcp">Landing Page</a> · <a href="#quick-start">Quick Start</a> · <a href="#agentic-payment-protocols">Agentic Protocols</a> · <a href="#countries">Countries</a> · <a href="#servers">All Servers</a> · <a href="docs/CONTRIBUTING.md">Contribute</a> </p> <p align="center"> <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a> <img src="https://img.shields.io/badge/servers-57-green" alt="57 servers"> <img src="https://img.shields.io/badge/tools-453-orange" alt="453 tools"> <img src="https://img.shields.io/badge/countries-4-blue" alt="4 countries"> <img src="https://img.shields.io/badge/MCP-compatible-purple" alt="MCP compatible"> </p> </p>
The Problem
AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Brazil, where every service has its own API, auth pattern, and quirks.
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:
| Protocol | Server | Tools | What it does |
|---|---|---|---|
| Google UCP | @codespar/mcp-ucp |
21 | Universal Commerce Protocol — agentic shopping, cart, checkout, orders, delivery, identity. Google's full commerce stack for AI agents. |
| Stripe ACP | @codespar/mcp-stripe-acp |
16 | Agentic Commerce Protocol — AI agent checkout, payment delegation, products, invoices. Live in ChatGPT with 1M+ Shopify merchants. |
| x402 | @codespar/mcp-x402 |
10 | HTTP-native micropayments by Coinbase — when an agent hits a 402, it pays USDC on Base/Solana and retries. Pure HTTP, no checkout UI. |
| AP2 | @codespar/mcp-ap2 |
13 | Google's Agent-to-Agent Payment Protocol — authorization, audit trails, scoped spend limits. 60+ partners including Visa, Mastercard, Stripe, PayPal. |
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 Machine-to-
in-chat managed acts within machine at
by agent budget/scope HTTP layer
The Convergence Stack
These protocols aren't competing — they're converging into layers:
┌─────────────────────────────────────────────┐
│ 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
└─────────────────────────────────────────────┘
CodeSpar sits at the Tool Layer — the middleware that connects every application, authorization, and settlement protocol through one interface.
Why this matters
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)
└── Brazilian merchant? → Asaas / Zoop / PagSeguro (traditional rails)
All via MCP. Same interface. One agent.
Quick Start — Agentic Protocols
# Google UCP — full agentic commerce (early access)
npx @codespar/mcp-ucp
# Stripe ACP — agentic checkout (test mode, free)
npx @codespar/mcp-stripe-acp
# x402 — HTTP micropayments (testnet, free)
npx @codespar/mcp-x402
# AP2 — agent authorization (early access)
npx @codespar/mcp-ap2
Quick Start
With Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": {
"stripe-acp": {
"command": "npx",
"args": ["-y", "@codespar/mcp-stripe-acp"],
"env": {
"STRIPE_API_KEY": "sk_test_..."
}
},
"zoop": {
"command": "npx",
"args": ["-y", "@codespar/mcp-zoop"],
"env": {
"ZOOP_API_KEY": "your-api-key",
"ZOOP_MARKETPLACE_ID": "your-marketplace-id"
}
}
}
}
With any MCP client
npx @codespar/mcp-stripe-acp # Agentic Commerce Protocol
npx @codespar/mcp-x402 # HTTP micropayments
npx @codespar/mcp-ap2 # Agent authorization
npx @codespar/mcp-zoop # Payments (marketplace, split)
npx @codespar/mcp-nuvem-fiscal # Fiscal
npx @codespar/mcp-melhor-envio # Logistics
npx @codespar/mcp-z-api # WhatsApp
npx @codespar/mcp-omie # ERP
npx @codespar/mcp-stark-bank # Banking
npx @codespar/mcp-dev-brasil-api # CEP, CNPJ (no key needed!)
Try it now (no API key)
BrasilAPI is free and public. Try it in your terminal:
npx @codespar/mcp-dev-brasil-api
Then ask your agent: "What is the address for CEP 01001-000?" or "Look up CNPJ 00.000.000/0001-91"
The Complete Loop
This is what makes MCP Brasil different — not individual connectors, but a complete business workflow across verticals:
| Step | Vertical | Server | What the agent does |
|---|---|---|---|
| 1 | 💳 Payment | Zoop | Creates Pix charge, splits to sellers |
| 2 | 📄 Fiscal | Nuvem Fiscal | Issues NFe/NFSe when payment confirmed |
| 3 | 📦 Logistics | Melhor Envio | Quotes shipping, generates label |
| 4 | 📱 Messaging | Z-API | Sends tracking code via WhatsApp |
| 5 | 📊 ERP | Omie | Records order, updates inventory |
| 6 | 🏦 Banking | Stark Bank | Reconciles balance, creates reports |
To orchestrate all 6 steps with governance, approval workflows, and audit trails — use CodeSpar.
Servers
⚡ Agentic Protocols (4 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Google UCP | 20 | Universal Commerce Protocol — shopping, cart, checkout, orders, delivery, identity | UCP API Key |
| Stripe ACP | 16 | Agentic Commerce Protocol — checkout sessions, payment delegation, products, invoices | Stripe API Key |
| x402 | 10 | HTTP micropayments — USDC on Base/Solana, paywalls, machine-to-machine | Facilitator Key |
| AP2 | 13 | Agent authorization, audit trails, scoped spend limits | AP2 API Key |
💳 Payments (13 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Asaas | 24 | Billing, Pix, boleto, subscriptions, transfers, refunds, notifications | API Key |
| PagSeguro | 13 | Orders, charges, Pix QR, refunds, subscriptions, splits | Bearer Token |
| iugu | 8 | Invoices, subscriptions, payment methods | Basic Auth |
| Pix BCB | 8 | Official Central Bank Pix API (cob, DICT) | OAuth2 + mTLS |
| Zoop | 28 | Marketplace payments, split rules, sellers, subscriptions, disputes, Pix | Basic Auth |
| Pagar.me | 10 | Orders, charges, recipients, transfers | Basic Auth |
| EBANX | 7 | Cross-border payments, payouts, FX rates | Integration Key |
| EFÍ/Gerencianet | 8 | Pix, boleto, carnet, open finance | OAuth2 |
| Vindi | 10 | Recurring billing, subscriptions, invoices | API Key |
| Cielo | 13 | Credit card, debit, boleto, Pix, recurrent payments | Merchant Key |
| Stone | 8 | Open banking, payments, Pix, transfers | OAuth2 |
| Celcoin | 8 | Pix, boleto, transfers, bill payments, top-ups | OAuth2 |
| AP2 | 13 | Google's Agent-to-Agent Payment Protocol | AP2 API Key |
📄 Fiscal (3 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Focus NFe | 8 | NFe/NFSe/NFCe emission and management | Basic Auth |
| Nuvem Fiscal | 15 | NFe/NFSe/NFCe/CTe/MDFe, CNPJ/CEP lookup | OAuth2 |
| Conta Azul | 10 | Accounting, invoicing, customers, products | OAuth2 |
📱 Communication (5 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Evolution API | 15 | WhatsApp automation (Baileys) | API Key |
| Z-API | 20 | WhatsApp messaging, contacts, groups, labels | Instance + Token |
| Zenvia | 8 | Multichannel (SMS, WhatsApp, RCS) | API Token |
| RD Station | 8 | Marketing automation, CRM, leads | Bearer Token |
| Take Blip | 8 | Chatbots, messaging, contacts, broadcasts | Access Key |
🇧🇷 Identity (1 server)
| Server | Tools | Description | Auth |
|---|---|---|---|
| BrasilAPI | 15 | CEP, CNPJ, banks, holidays, FIPE, DDD, IBGE, SELIC, weather | None (free) |
🏦 Banking (2 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Stark Bank | 15 | Transfers, boleto, invoices, Pix, balance, brcode, deposits | Access Token |
| Open Finance | 8 | Open Finance Brasil — accounts, transactions, consents, investments | OAuth2 |
📦 E-commerce / Logistics (3 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Melhor Envio | 18 | Shipping quotes, tracking, labels, cart, agencies | Bearer Token |
| Correios | 11 | Tracking, shipping, collections, reverse logistics | OAuth |
| VTEX | 15 | E-commerce, orders, products, inventory, categories, shipping | App Key + Token |
📊 ERP (3 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Omie | 15 | Customers, products, orders, invoices, services, purchases | App Key + Secret |
| Bling | 10 | ERP, products, orders, invoices, stock management | OAuth2 |
| Tiny | 10 | ERP, products, orders, invoices, stock, accounts payable | API Token |
🪙 Crypto / Stablecoins (5 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| x402 | 10 | HTTP micropayments — USDC on Base/Solana | Facilitator Key |
| UnblockPay | 10 | Fiat-to-stablecoin onramp/offramp, wallets, transfers | API Key |
| Circle | 10 | USDC payments, wallets, payouts, transfers | API Key |
| Mercado Bitcoin | 10 | Brazilian crypto exchange, trading, orderbook, withdrawals | API Key + Secret |
| Bitso | 10 | Latin American crypto exchange, trading, funding, withdrawals | API Key + Secret |
🌎 LATAM-Wide (4 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Mercado Libre | 14 | LATAM marketplace (18 countries) — products, orders, sellers, shipments | OAuth2 |
| Mercado Pago | 12 | LATAM payments — cards, PIX, checkout, refunds | Bearer Token |
| Nubank | 10 | Brazilian neobank via Open Finance — accounts, PIX, transactions | OAuth2 |
| Banco Inter | 12 | Brazilian digital bank — boleto, PIX, statements, transfers | OAuth2 |
🇲🇽 Mexico (6 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Conekta | 10 | Payment gateway — cards, OXXO cash, SPEI | Basic Auth |
| FacturAPI | 10 | CFDI e-invoicing (Mexican NFe) | Bearer Token |
| STP/SPEI | 8 | Instant bank transfers (Mexico's PIX) | API Key |
| Skydropx | 10 | Multi-carrier shipping (Estafeta, DHL, FedEx) | Bearer Token |
| Bind ERP | 10 | Cloud ERP | API Key |
| Belvo | 10 | Open Finance aggregator (MX/AR/CO) | Basic Auth |
🇦🇷 Argentina (5 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| AFIP | 8 | Electronic invoicing (Factura Electrónica) | Certificate |
| Andreani | 8 | Logistics/courier (largest in Argentina) | JWT |
| Colppy | 8 | Cloud accounting + AFIP invoicing | API Key |
| Tienda Nube | 10 | E-commerce platform (LATAM Shopify) | Bearer Token |
| BCRA | 6 | Central Bank public data (exchange rates, free) | None (free) |
🇨🇴 Colombia (5 servers)
| Server | Tools | Description | Auth |
|---|---|---|---|
| Wompi | 10 | Payment gateway by Bancolombia (cards, PSE, Nequi) | Bearer Token |
| Siigo | 10 | Accounting + DIAN e-invoicing | Bearer Token |
| Nequi | 6 | Digital wallet (50M+ users) | OAuth2 |
| Coordinadora | 8 | Logistics/courier | API Key |
| Alegra | 10 | Cloud accounting (cross-LATAM) | Basic Auth |
🔜 Coming Soon
Foxbit · BRLA · Coinbase · Transak · PagBrasil · Juno · NFe.io · PlugNotas · Movidesk · Infobip · Frenet · Loggi · Kangu · ReceitaWS · BigDataCorp · Sankhya · Totvs · Clip (MX) · Contpaqi (MX) · Ualá (AR) · Naranja X (AR) · Transbank (CL) · Nequi (CO expanded) · Rappi (CO)
Why MCP?
Model Context Protocol is the open standard for connecting AI agents to external tools. Instead of each agent building its own integrations, MCP provides a typed, discoverable interface that works with Claude, ChatGPT, Copilot, Cursor, and more.
AI Agent (Claude, ChatGPT, Cursor)
↕
MCP Server (this repo)
↕
Brazilian API / Agentic Protocol (Stripe ACP, x402, Zoop, etc.)
Each MCP server in this repo:
- Exposes typed tools with input/output schemas
- Handles authentication (OAuth, API keys, Basic Auth)
- Supports dual transport — stdio (default) and Streamable HTTP (
--httpflag) - Compatible with Claude Managed Agents via MCP Connector
- Supports sandbox mode for safe testing
- Returns structured JSON responses
Running in HTTP mode
Any server can run as an HTTP server for remote/cloud use:
# stdio (default — local, Claude Desktop, Cursor)
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 CodeSpar
CodeSpar is an open source multi-agent platform that deploys autonomous AI coding agents to WhatsApp, Slack, Telegram, and Discord.
The MCP Generator in CodeSpar Enterprise can automatically generate MCP servers from API specifications — that's how this repo was bootstrapped.
Individual MCP servers are useful. Orchestrating many with governance is powerful. That's what CodeSpar does — including a Payment Gateway that integrates policy engine, payment routing, and mandate authorization across all rails.
Contributing
We welcome contributions! See CONTRIBUTING.md.
Want a server for a service not listed? Open an issue with the "server request" label.
License
MIT — use freely in commercial and open source projects.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.