mcp-dev-latam

Dev Latam MCP Server

LATAM commerce developers can use mcp-dev-latam for agent checkout, payments, and regional provider integrations. Its listed tools cover Brazilian company, banking, tax, vehicle, and location data.

Server facts

mcp-dev-latam

Project

Author
codespar
License
Not specified

Tech

Runtime / language
Not specified
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
273
Last commit
Data as of

Tags

  • Whatsapp
  • agentic commerce
  • argentina
  • brazil
  • colombia
  • fintech
  • latam
  • mcp
  • mexico
  • nfe
  • open source
  • payments
  • pix
  • stripe

Overview

Commerce agents can use mcp-dev-latam's collection for payment and checkout workflows across Brazil, Mexico, Argentina, Colombia, Chile, and Peru. Stripe ACP addresses checkout and delegated payments, AP2 covers agent authorization and audit trails, and Google UCP spans shopping through orders and delivery. The x402 integration targets HTTP micropayments using USDC on Base or Solana. Regional providers include Asaas and Mercado Pago, Mexico's Conekta, Colombia's Wompi, Chile's Transbank, and Peru's Culqi, alongside fiscal, banking, logistics, identity, and ERP integrations.

The listed tools focus on Brazilian reference data. CEP and CNPJ queries retrieve addresses and company details; banking tools list bank identifiers, Pix institutions, and CVM-registered brokerages. Other calls return NCM classifications, Selic/CDI/IPCA rates, and FIPE vehicle brands, models, prices, and reference tables. Geographic and environmental queries cover IBGE states and municipalities, DDD coverage, and CPTEC weather, with separate tools for national holidays, book metadata, and .br registration details. The listed interface uses stdio.

mcp-dev-latam setup notes

  • mcp-dev-latam records stdio only; confirm a network transport upstream before planning remote access.
  • mcp-dev-latam has no recorded license; confirm reuse terms in its repository.

Related MCP servers