Name: MCP Dev LATAM
Author: codespar

LABSCO SUMMARY

The point is the chain, not any single connector.

Charging via Pix, issuing an NFe, generating a shipping label, sending tracking over WhatsApp and recording it in an ERP are five different vendors with five different auth patterns — and this makes them five MCP servers with one interface. Start with @codespar/mcp-brasil-api if you want to see the shape of it without signing up for anything: CEP and CNPJ lookups work with no key.

What it is

A catalog of MCP servers wrapping real Latin American providers, plus four agentic payment protocols, each published as its own npm package.

What you get

127 MCP servers for LATAM commerce across Brazil, Mexico, Argentina, Colombia, Chile and Peru, live in the official MCP Registry
Payments — @codespar/mcp-asaas for Brazilian billing and Pix, @codespar/mcp-mercado-pago for LATAM payments, and more
Fiscal — @codespar/mcp-nuvem-fiscal for NFe and NFSe
Logistics — @codespar/mcp-melhor-envio for multi-carrier shipping
Messaging and ERP — @codespar/mcp-z-api for WhatsApp, @codespar/mcp-omie for ERP
Banking — @codespar/mcp-stark-bank, plus contract-gated providers such as Itaú and BTG published under an alpha tag
Agentic payment protocols — @codespar/mcp-stripe-acp with 24 tools, @codespar/mcp-ucp with 20, @codespar/mcp-ap2 with 22 in alpha, and @codespar/mcp-x402 with 10 for HTTP micropayments in USDC
@codespar/mcp-brasil-api for CEP and CNPJ lookups, which needs no key at all

Requirements

npx and a client config entry per server you want — each provider is its own package with its own credentials, for example STRIPE_API_KEY for the Stripe ACP server or ASAAS_API_KEY with ASAAS_SANDBOX for Asaas. Contract-gated bank providers install with an @alpha tag. BrasilAPI and BCRA are public and need no key.

Setup effort

One command — npx @codespar/mcp-brasil-api

See installation options

USE CASES

01

Taking a payment and issuing the invoice

Charge through a Brazilian payment provider, then issue the NFe once the payment confirms.

02

Getting the order to the customer

Quote shipping, generate the label, and send tracking over WhatsApp.

03

Trying it before you sign up for anything

Run the BrasilAPI server and look up a CEP or a CNPJ with no key.

04

Letting an agent pay for an API call

Use the x402 server so a 402 response becomes a USDC payment and a retry.

BEFORE YOU INSTALL

What to know first

Requires

npx on PATH
A key for each paid provider package you add (for example STRIPE_API_KEY for Stripe ACP, ASAAS_API_KEY for Asaas); BrasilAPI and BCRA need none

INSTALLATION

Connect your client

Server setup

TERMINAL

npx @codespar/mcp-brasil-api

MCP Clients

Claude Desktop

Start with BrasilAPI, which needs no key. Add to claude_desktop_config.json, which Claude Desktop keeps in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows (Settings → Developer → Edit Config opens it):

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "brasil-api": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-brasil-api"
      ]
    }
  }
}

Claude Code

CLAUDE CODE · TERMINAL

claude mcp add brasil-api -- npx @codespar/mcp-brasil-api

VS Code

Add to .vscode/mcp.json:

VS CODE · JSON

{
  "servers": {
    "brasil-api": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-brasil-api"
      ]
    }
  }
}

Claude Desktop — API Key

Each provider is its own package with its own key. This is the project's example for Stripe ACP and Asaas; the other packages and the variables each one needs are listed under packages/<category>/<slug>/ in the repository.

CLAUDE DESKTOP — API KEY · JSON

{
  "mcpServers": {
    "stripe-acp": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-stripe-acp"
      ],
      "env": {
        "STRIPE_API_KEY": "<YOUR_STRIPE_API_KEY>"
      }
    },
    "asaas": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-asaas"
      ],
      "env": {
        "ASAAS_API_KEY": "<YOUR_ASAAS_API_KEY>",
        "ASAAS_SANDBOX": "true"
      }
    }
  }
}

MCP Dev LATAM