io.github.codespar/mcp-shopify

MCP Dev LATAM 🌎

Every commerce API your AI agent needs to run a business in Latin America.

Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols.

MCP servers for LATAM commerce · live in the official MCP Registry · MIT License

Machine-readable catalog: codespar.dev/api/servers

Catalog ·

Quick Start ·

Agentic Protocols ·

All Servers ·

Contribute

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 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) — 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.

🛒 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.

Agentic Payment Protocols

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):

> UCP, AP2 and x402 are deprecated: no live endpoint. Measured on 2026-09-27:

>

> | Server | Default host | What that host answered |

> |---|---|---|

> | @codespar/mcp-ucp | commerce.googleapis.com (sandbox: sandbox.commerce.googleapis.com) | HTTP 404 with Google's generic Error 404 (Not Found) page; the sandbox host fails the TLS handshake (certificate is for *.googleapis.com) |

> | @codespar/mcp-ap2 | ap2.googleapis.com (sandbox: sandbox.ap2.googleapis.com) | 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

The Convergence Stack

┌─────────────────────────────────────────────┐
│  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.

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:

{
  "mcpServers": {
    "stripe-acp": {
      "command": "npx",
      "args": ["-y", "@codespar/mcp-stripe-acp"],
      "env": {
        "STRIPE_API_KEY": "sk_test_..."
      }
    },
    "asaas": {
      "command": "npx",
      "args": ["-y", "@codespar/mcp-asaas"],
      "env": {
        "ASAAS_API_KEY": "your-api-key",
        "ASAAS_SANDBOX": "true"
      }
    }
  }
}

For alpha packages (contract-gated providers like Itaú, Bradesco, Santander, Caixa, BB, BTG, Sicoob), add @alpha to the install:

npx -y @codespar/mcp-itau@alpha

With any MCP client

npx @codespar/mcp-stripe-acp        # Agentic Commerce Protocol

npx @codespar/mcp-asaas              # BR billing + Pix
npx @codespar/mcp-mercado-pago       # LATAM payments
npx @codespar/mcp-nuvem-fiscal       # NFe / NFSe
npx @codespar/mcp-melhor-envio       # Multi-carrier shipping
npx @codespar/mcp-z-api              # WhatsApp messaging
npx @codespar/mcp-omie               # ERP
npx @codespar/mcp-stark-bank         # Banking
npx @codespar/mcp-brasil-api         # CEP, CNPJ (no key needed!)

Try it now (no API key)

[BrasilAPI](packages/identity/brasil-api) and [BCRA](packages/argentina/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 _BASE_URL, where ` is the one the server's credentials already use (CELCOIN_BASE_URL, STONE_BASE_URL, BB_BASE_URL). A second host gets _<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](.github/workflows/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](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:

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>/.

💳 Payments (46 servers)

🏦 Banking (16 servers)

📄 Fiscal (Brasil) (4 servers)

📱 Communication (8 servers)

📦 E-commerce / Logistics (7 servers)

📊 ERP / Accounting (5 servers)

🪪 Identity & KYC (8 servers)

🛡️ Fraud & Risk (4 servers)

🪙 Crypto / Stablecoins (10 servers)

🇦🇷 Argentina (6 servers)

🇨🇴 Colombia (8 servers)

🇲🇽 Mexico (7 servers)

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, 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.

Contributing

We welcome contributions. See [CONTRIBUTING.md](docs/CONTRIBUTING.md).

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.