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 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).
Open-source MCP servers for Latin American commerce — Pix, NF-e, banking, fiscal, logistics, and messaging across Brazil, Mexico, Argentina, Colombia, Chile, and Peru. MIT, on npm.
STP_API_KEY, STP_COMPANY
Zuletzt geprüft
2026-10-27
Sterne
274
Tools
—
Uptime
—
Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with 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.
The Solution
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.
Four servers for the emerging agentic payment stack. Only Stripe ACP reaches a live service today; the other three are deprecated (see the note under the table):
the same generic 404 page; the sandbox host fails the TLS handshake the same way
@codespar/mcp-x402
api.x402.org
does not resolve in DNS (8.8.8.8 and 1.1.1.1)
A generic 404 by itself does not prove a name has no service behind it: translate.googleapis.com/v1, a registered service asked for a path it does not serve, answers the same page. What the claim rests on is that every path these servers call failed the same way. UCP and AP2 are open specifications, not APIs Google hosts, and x402 has no central API (each seller picks its own facilitator). The three packages are deprecated on npm and kept here for reference; they are out of the quick start and the decision tree below. Eight more servers are deprecated for the same reason (their default host does not resolve): C6, Dock, Matera, Legiti, Caf, Certta, Unico and Nubank.
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
MCP Dev LATAM 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
├── Retail checkout? → Stripe ACP (create_checkout → complete_checkout)
└── LATAM merchant? → Asaas / Mercado Pago / Conekta / Wompi / etc.
All via MCP. Same interface. One agent.
Quick Start
With Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
BrasilAPI and BCRA are public — no key required. Try it in your terminal:
npx @codespar/mcp-brasil-api
Then ask your agent: "What is the address for CEP 01001-000?" or "Look up CNPJ 00.000.000/0001-91".
Pointing a server at another host
Every server reads its provider host from an environment variable, so a proxy, a mock, or an endpoint the provider moved can be used without a new release. The primary API is <PREFIX>_BASE_URL, where <PREFIX> is the one the server's credentials already use (CELCOIN_BASE_URL, STONE_BASE_URL, BB_BASE_URL). A second host gets <PREFIX>_<ROLE>_URL, for example STONE_AUTH_URL for a token endpoint or CIELO_QUERY_URL. When the variable is unset the server uses its documented default.
A weekly CI job (catalog-hosts.yml) resolves every default host in the catalog and completes a TLS handshake with it, and fails when a host does not exist. The only exceptions are deprecated servers and the few sandbox hosts listed, each with its reason, in scripts/catalog-hosts-known-dead.json; the job also fails when one of those comes back, so the list cannot go stale. Run it locally with python3 scripts/check-catalog-hosts.py (Python 3.10+).
The Complete Loop
This is what makes the LATAM catalog different — not individual connectors, but a complete business workflow across verticals:
Step
Vertical
Example providers
What the agent does
1
💳 Payment
Asaas / Mercado Pago / Zoop
Creates Pix charge, splits to sellers
2
📄 Fiscal
Nuvem Fiscal / NFe.io / Focus NFe
Issues NFe/NFSe when payment confirmed
3
📦 Logistics
Melhor Envio / Correios / Skydropx
Quotes shipping, generates label
4
📱 Messaging
Z-API / WhatsApp Cloud / Twilio
Sends tracking via customer's preferred channel
5
📊 ERP
Omie / Bling / Tiny / Conta Azul
Records order, updates inventory
6
🏦 Banking
Stark Bank / Itaú / BTG
Reconciles balance, creates reports
To orchestrate all six steps with governance, approval workflows, and audit trails — use CodeSpar.
All Servers
Browse the full catalog at codespar.dev/servers. Each server has its own README, env-var requirements, and tool reference under packages/<category>/<slug>/.
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, Cursor, VS Code, and more.
AI Agent (Claude, ChatGPT, Cursor)
↕
MCP Server (this repo)
↕
LATAM API / Agentic Protocol (Stripe ACP, x402, Asaas, Mercado Pago, NFe.io, etc.)
Each MCP server in this repo:
Exposes typed tools with input/output schemas
Handles authentication (OAuth, mTLS, API keys, Basic Auth, JWT-RSA, signed requests)
Supports dual transport — stdio (default) and Streamable HTTP (--http flag)
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, 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).
Alpha vs stable
About a third of the catalog ships under the alpha npm 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 with TODO(verify) in source.
npm install @codespar/mcp-itau@alpha
Stable packages (the majority) install with the default tag:
npm install @codespar/mcp-stripe
Status is shown on every package page at codespar.dev/servers and in each package README.
About CodeSpar
CodeSpar builds commerce infrastructure for AI agents in Latin America — an MCP catalog (this repo), a runtime + SDK (@codespar/sdk on npm, codespar on PyPI), and a managed-tier governance product (AgentGate: programmable wallet, policy engine, CFO-grade audit, fiscal-compliance certifications).
Individual MCP servers are useful. Orchestrating many with governance is powerful. That's what CodeSpar does.
Part of a broader ecosystem index: Awesome Agentic Commerce LATAM — a vendor-neutral list of the protocols, rails, providers, and regulation for agents that move money in Latin America.
Want a server for a service not listed?Open a server-request issue — there's a structured form with name, npm package, docs link, auth flow.
License
MIT — use freely in commercial and open source projects.
M
MCP Dev Latam
codespar·274 Sterne·
Open-source MCP servers for Latin American commerce — Pix, NF-e, banking, fiscal, logistics, and messaging across Brazil, Mexico, Argentina, Colombia, Chile, and Peru. MIT, on npm.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich MCP Dev Latam?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt MCP Dev Latam einen API-Schlüssel?
Der Herausgeber nennt diese Umgebungsvariablen: STP_API_KEY, STP_COMPANY.
Welchen Transport verwendet MCP Dev Latam?
MCP Dev Latam läuft lokal über stdio.
Wann wurde MCP Dev Latam zuletzt geprüft?
Zuletzt geprüft: 2026-10-27. Open-source MCP servers for Latin American commerce — Pix, NF-e, banking, fiscal, logistics, and messaging across Brazil, Mexico, Argentina, Colombia, Chile, and Peru. MIT, on npm.