Mcp Dev Latam
Open-source MCP servers for Pix, boleto, NF-e, SPEI and WhatsApp so AI agents can move money and issue fiscal documents across Latin
The mandate/guardrail/receipt stack is the reason to care here — a generic payouts API gives you a charge endpoint and nothing else, while CodeSpar refuses off-mission spend before the provider is ever called and prices on settled money, not attempts. Regional depth is the other half: Pix BCB, Open Finance Brasil, NF-e, SPEI and PSE are not things Stripe or QuickBooks expose. Just check the stage label on any server before you put it in front of production traffic.
Verified 3d ago · liveness 74/100 · cite: rightaichoice.com/tools/mcp-dev-latam
- AI engineers building commerce agents that need to spend, charge or settle in Brazil, Mexico or Colombia
- Marketplaces wiring Pix, boleto, NF-e and split payouts behind a single MCP interface instead of six vendor integrations
- SaaS teams expanding into LatAm that would rather not write and maintain regional API glue
- Developers who want MIT-licensed, self-hostable MCP servers for Pix BCB, Open Finance Brasil and SPEI
- US-only businesses with no Latin American customers, currency exposure or fiscal obligations
- Teams that want a conventional REST payments gateway rather than MCP tooling designed for agents
- Anyone requiring air-gapped on-premise deployment or a fully self-contained hosted environment
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip CodeSpar if you have no Latin American customers or currency exposure and want a conventional REST gateway with a dashboard you log into, rather than MCP servers and 14 meta-tools you point an autonomous agent at.
Rail fees for Pix, boleto, card and USDC are passed through at the provider's price on a separate invoice line — your all-in cost of a Pix is the CodeSpar fee plus Zoop's or Efi's charge, not just 10 bps.
Priced for teams whose agents actually settle money rather than for seat count. Build is genuinely R$0 with no usage cap, which undercuts per-seat agent platforms. The 10 bps Move rate with a R$0.05 floor and R$2.00 cap, and 1% Get paid with a R$2.00 cap, are cheap against a generic cross-border processor's 1–3% plus FX spread, and the first R$1,000 settled per lane per month is free. Above R$5M/month out, Enterprise drops to 8 bps; above R$50M/month, 6 bps. Cheap for a LatAm-commerce agent;
In short
Mcp Dev Latam — Open-source MCP servers for Pix, boleto, NF-e, SPEI and WhatsApp so AI agents can move money and issue fiscal documents across Latin. Best for AI engineers building commerce agents that need to spend, charge or settle in Brazil, Mexico or Colombia, Marketplaces wiring Pix, boleto, NF-e and split payouts behind a single MCP interface instead of six vendor integrations, SaaS teams expanding into LatAm that would rather not write and maintain regional API glue. Free to start; it also has paid plans, priced in a currency we have not confirmed — see the pricing table for the vendor’s own figures.
What's new in Mcp Dev Latam
Checked 6 days agoAcross the latest 1 update: 1 changelog entry.
What people actually say about Mcp Dev Latam — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
6 mentions across 1 source (GitHub) · researched Sep 23, 2026.
Weighted by the 6 posts each of 1 source contributed.
- +133 MIT-licensed MCP servers covering Pix, NF-e, SPEI, CFDI, WhatsApp, and LatAm logistics in one repo
- +Self-hostable core means you can fork, patch, and audit instead of trusting a hosted black box
- +Genuinely wide integration list: Mercado Pago, Asaas, Stripe, VTEX, Omie, Bling, Z-API, Adyen
- +Meta-tools like codespar_checkout, codespar_ledger, and codespar_issue make agent commerce composable
- +Policy engine with HMAC mandates and caps addresses a real agent-spend governance gap
- −Public catalog lists npm packages and hosts that don't resolve — live-measured as HIGH severity
- −@codespar/mcp-x402 points at an NXDOMAIN domain, killing all ten tools in that package
- −Nine servers have no resolvable host; eight more silently fall back to a default host
- −Pix devolution and v5 merchant tools diverged from the homologated enterprise catalog
- −Zero visible Reddit, HN, YouTube, or Product Hunt discussion — hard to gauge real-world uptime
- • Engineering time to verify which catalog entries actually resolve before shipping
- • Fork-and-patch maintenance burden if you self-host the fast-moving catalog
- • Metered post-paid billing on the managed layer can surprise teams that don't set caps
- • Potential reconciliation work when enterprise and open-source surfaces diverge (celcoin)
Viability Score
How well maintained and how widely used is Mcp Dev Latam? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- 132 MIT-licensed MCP servers exposing 2,536 tools across LatAm payment, fiscal, banking and messaging rails
- Install per-server from npm with npx, or connect to the hosted remote MCP endpoint at connect.codespar.dev
- Hosted remote MCP over Streamable HTTP with Bearer or OAuth 2.1 authentication
- Signed mandates setting spend cap, scope and expiry — anything outside the mandate is refused
- Guardrails engine enforcing spend budgets, rate limits and human approval server-side, never in the model
- Hash-chained agentic receipts binding permission, settlement and proof, verifiable offline
- Append-only tamper-evident audit ledger exportable for compliance
- Agent identity via did:web plus Ed25519 keys with register, rotate and revoke lifecycle
- Agent wallet with multi-slot BRL and USDC under one mandate, no silent FX
- Pix charges with live agent checkout through codespar_checkout (Pix only)
- NF-e and NFS-e emission via NFe.io and Nuvem Fiscal without certificate install or XML assembly
- codespar_pay method enum limited to pix, card, boleto and wire
- Gate paywall returning HTTP 402 on unpaid calls, settling USDC on Base mainnet
- One hosted MCP URL or plain REST — 340 OpenAPI operations, no SDK required
- CLI with 134 commands over the same surface
About Mcp Dev Latam
CodeSpar's server catalog is aimed at AI engineers who need their agent to transact in Latin America, not just talk about it. The vendor page lists 132 MIT-licensed MCP servers carrying 2,536 tools, spanning Pix, boleto, card acquiring, fiscal emission, logistics and messaging — Mercado Pago (30 tools), Zoop (28), Asaas (24), PagSeguro (24), NFe.io (22), Melhor Envio (18) and a long tail of Brazilian, Mexican, Colombian and Chilean providers, plus global rails like Stripe's Agentic Commerce Protocol. Install one package at a time from npm — claude mcp add pix-bcb -- npx -y @codespar/mcp-pix-bcb@0.2.2 — or point a Streamable HTTP client at connect.codespar.dev, where a single hosted interface exposes meta-tools instead of raw provider keys. The layer that separates this from a payments API with an MCP wrapper is governance. A signed mandate fixes spend cap, scope and expiry; the guardrails engine refuses off-mission spend server-side before any provider is called; agent identity runs on did:web with Ed25519 keys and register/rotate/revoke lifecycle; settlements close with hash-chained receipts that can be verified offline; and an append-only audit ledger exports for compliance. Fiscal work is handled without certificate installation or XML assembly — NFe.io and Nuvem Fiscal emit NF-e and NFS-e through codespar_issue. Fall 2026 catalog corrections trimmed the surface: the stablecoin-payout rail is gone, the codespar_pay method enum now reads pix, card, boleto, wire, and codespar_checkout routes Pix only. Pricing is unusually legible for agent infrastructure. Build is free — hosted MCP, SDK, CLI, sandbox, catalog. Money out under mandate costs 10 bps with a R$0.05 floor and R$2.00 cap; money in settled costs 1% with the same cap; the first R$1,000 settled each month is free per lane, per organization. Accounts signing up before general availability lock those rates for 24 months. Move and Collect are included until GA, and test keys are free while production needs
Behind the Verdict
Where this earns its keep is the moment your agent needs to do something a US payments stack cannot express. Emitting an NF-e, charging a Pix QR that expires in 30 minutes, splitting receivables across marketplace partners, collecting OXXO cash in Mexico — each of those is its own regional vendor, its own credential dance and its own error taxonomy. CodeSpar collapses them behind one install command or one hosted MCP URL, and the meta-tool set (codespar_checkout, codespar_shop, codespar_ledger, codespar_issue) keeps the model from drowning in 2,536 individual tools. We'd reach for it when the agent's job is money movement under limits. The signed mandate plus server-side guardrails is the right shape for anything that spends on your behalf: budget enforcement lives outside the model, so a prompt injection cannot talk its way past a spend cap. The hash-chained receipt trail and audit ledger are what a finance team will ask for six months in, and it is much easier to answer that question now than to retrofit it. Where it bites: the catalog's stage labels mean what they say. Live servers are the ones to build on; beta (Conekta, Wompi, dLocal, Getnet) and alpha are fine for evaluation, risky for revenue. The September 2026 changelog is a good reminder that this surface still moves — the stablecoin-payout rail was removed and codespar_pay dropped sepa and usdc, so anything you built against those enum values needs rechecking. Pin your npm version, as the docs themselves do at @0.2.2. Pricing is the pleasant surprise. 10 bps out with a R$2.00 cap means a R$100 Pix settlement costs R$0.10, and the cap does more work than the rate for high-ticket flows. Failures, retries, declined attempts and webhooks carry no fee — you pay when money settles. First R$1,000 per lane per
Researching Mcp Dev Latam? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Mcp Dev Latam actually fits — and what changes day-one when you adopt it.
Your checkout agent needs to take a Pix charge and immediately emit the matching NF-e. You add the pix-bcb or Zoop server over MCP, sign a mandate that caps the agent's charge authority, and call codespar_checkout followed by the NFe.io issue meta-tool.
Outcome: A settled Pix and a DANFE-ready NF-e from one session, with a hash-chained receipt and an audit-ledger entry the finance team can export.
You onboard vendors and split receivables across partners. Instead of building four acquirer integrations, you route through Zoop, Mercado Pago, Asaas and Stark Bank behind one meta-tool and reconcile settlements against the append-only ledger.
Outcome: One integration surface instead of four, with per-vendor mandate scopes so a rogue seller account cannot move money outside its signed cap.
You put a Gate paywall in front of your own endpoint. An unpaid call gets HTTP 402; a paid call settles USDC on Base mainnet and is proxied upstream with a sealed receipt.
Outcome: You take a paid agent call without writing payment plumbing, and can verify the receipt offline.
Use Cases
- Accept a Pix payment and issue the matching NF-e invoice from one agent session, without handling certificates
- Give a coding agent a governed wallet so it can shop a real store and pay the payable Pix inside a signed cap
- Route payouts across Mercado Pago, Zoop, Asaas and Stark Bank and reconcile settlements against one ledger
- Put an x402 paywall in front of your own API or MCP server and take the first paid USDC call on Base
- Onboard marketplace vendors, split receivables across partners, and track disputes through the Rinne or Asaas servers
- Manage Omie or Bling back-office — sales orders, accounts payable, inventory, NF-e — without opening the ERP
- Send receipts, confirmations and support replies to Brazilian customers over WhatsApp via Z-API or Evolution API
- Reconcile VTEX or Shopify daily sales against Stark Bank statements, with the audit ledger as the evidence trail
Limitations
- Pricing is split into lanes: money out under mandate at 10 bps (floor R$0.05, cap R$2.00) and money in at 1% (cap R$2.00), with the first R$1,000 settled per lane per month free.
- Move and Collect are included until general availability, so the published transaction fees are not yet fully live; payment method costs pass through on a separate line and taxes are excluded.
- The catalog is large but variable — 132 servers across 8 regions, and the September 2026 change removed the standalone stablecoin-payout rail and dropped sepa and usdc from the codespar_pay enum, so server surfaces can change under you.
as of 2026-10-09
Verification history
We have re-verified Mcp Dev Latam 8 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 8 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Mcp Dev Latam tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Build
R$0
Ideal for
Solo developer or small team evaluating the catalog before any money moves; you need hosted MCP, the SDK, CLI and sandbox and you are happy to self-host the MIT-licensed servers.
What this tier adds
Starting tier — R$0 with no usage cap on building, measuring and testing; there is no paid build tier above it.
Move
10 bps · floor R$0.05 · cap R$2.00 per transaction
Ideal for
Teams sending money out under agent authority — supplier payments, payouts through Pay, transfers out of the Wallet — starting with volumes under R$5M/month.
What this tier adds
Adds a settling fee of 10 bps on money leaving your org under a signed mandate, floor R$0.05 and cap R$2.00 per transaction.
Get paid
1% · no floor · cap R$2.00 per transaction
Ideal for
Anyone collecting — an x402-paywalled API taking paid agent calls through Gate, or a merchant using Collect payment links and live Pix checkout through Shop.
What this tier adds
Adds 1% on money arriving at settlement with no floor and a R$2.00 cap, priced on what settles rather than on the attempt.
Account governance
R$4.90 per eligible account · month
Ideal for
Organizations running many governed counterparties — payers under Embed, agent counterparties, paywall customers — who need the mandate, identity, guardrail and receipt state stored per account.
What this tier adds
Adds R$4.90 per governed account active in the month, published now and not yet charged; accounts with no outcome in the month cost R$0.
Cross-border FX
0.5% self-serve · 0.3% with committed volume
Ideal for
Sellers converting between currencies — Brazil to Mexico or Colombia collections, or LatAm to global settlements — at self-serve volumes or with committed volume.
What this tier adds
Adds a separate 0.5% self-serve FX line, dropping to 0.3% with committed volume, stacking on top of the lane fee rather than replacing it.
Enterprise
Custom
Where the pricing makes sense
The company stage and team size where Mcp Dev Latam's pricing actually pencils out — and where peers do it cheaper.
Priced for teams whose agents actually settle money rather than for seat count. Build is genuinely R$0 with no usage cap, which undercuts per-seat agent platforms. The 10 bps Move rate with a R$0.05 floor and R$2.00 cap, and 1% Get paid with a R$2.00 cap, are cheap against a generic cross-border processor's 1–3% plus FX spread, and the first R$1,000 settled per lane per month is free. Above R$5M/month out, Enterprise drops to 8 bps; above R$50M/month, 6 bps. Cheap for a LatAm-commerce agent;
Setup time & first value
How long it actually takes to get something useful out of Mcp Dev Latam — broken out by persona, not the marketing-page minute.
With the hosted URL it is one command — claude mcp add --transport http codespar https://connect.codespar.dev/mcp — and a first tool call; test keys are free and take minutes. Self-hosting a single npm server (npx -y @codespar/mcp-pix-bcb) plus your own provider credentials is perhaps 30 minutes. Full production use adds KYC/KYB before production keys, plus mandate design and provider credential
Switching to or from Mcp Dev Latam
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From raw provider SDKs: replace per-acquirer integration code with the matching CodeSpar MCP server plus a signed mandate, keeping your own provider credentials injected server-side.
- →From a generic payouts processor: keep Build running in parallel — test keys are free — and move one settlement lane across before cutting over.
- →From self-hosted MCP servers: point your MCP client at connect.codespar.dev with Bearer or OAuth 2.1 and keep the same 14 meta-tools.
- →From an internal agent wallet: export existing spend limits into a mandate with the same cap, scope and expiry, so the guardrail engine enforces them server-side.
- ↗To Stripe Global plus a local acquirer: rewire your charge and payout calls onto Stripe's REST API, and reimplement spend caps in your own orchestration layer since Stripe has no mandate primitive.
- ↗To a regional PSP directly (Zoop, Asaas, Mercado Pago): take your credentials and call the provider's own API, replacing codespar_checkout and codespar_crypto_pay with provider SDKs and building your own receipt and
- ↗To a plain REST workflow: CodeSpar's 340 operations are served from its OpenAPI document, so you can call the same endpoints without the MCP layer — though mandate signing stays server-side.
Integrations
Resources & Guides
- Documentationcodespar.dev
Docs · Mcp Dev Latam
Full product docs from codespar.dev
- Documentationcodespar.dev
Cookbooks · Mcp Dev Latam
Full product docs from codespar.dev
- API Referencecodespar.dev
Reference · Mcp Dev Latam
Methods, params, types from codespar.dev
- Resourcecodespar.dev
Servers · Mcp Dev Latam
Helpful link from codespar.dev
- Resourcecodespar.dev
Pricing · Mcp Dev Latam
Helpful link from codespar.dev
Tutorials & Learning
YouTube returned 6 videos for “Mcp Dev Latam”, and we withheld 5: 5 did not mention Mcp Dev Latam. Showing the 1 we can prove is about Mcp Dev Latam.
Featured Head-to-Head Comparisons
Mcp Dev Latam vs Spider Cloud
Spider Cloud is for AI agents that need real-time web data for RAG; Mcp Dev Latam (CodeSpar) is for commerce agents operating in LatAm. If your need is scraping and crawling any website globally, choose Spider Cloud. If you're building an AI agent that must process payments, issue invoices, or handle logistics in countries like Brazil or Mexico, Mcp Dev Latam is the clear winner. They solve different problems—pick based on your data source.
Mcp Dev Latam vs Presto Voice
Presto Voice is the clear choice for QSRs seeking drive-thru voice automation with proven upselling ROI, especially after its Dairy Queen win. Mcp Dev Latam is indispensable for AI engineers building commerce agents for Latin America — it's open-source, rapidly expanding, and unlike Presto, serves a developer audience. Buy Presto if you run a drive-thru chain; adopt MCP Dev Latam if you're coding agents for LatAm payments and logistics.
Mcp Dev Latam vs Temporal Ai
Choose Temporal AI if you need a battle-tested durable execution engine for mission-critical workflows across any industry, with automatic retries, state persistence, and deep observability. Choose MCP Dev Latam if you're building AI agents specifically for Latin American commerce and need ready-made integrations for Pix, NF-e, banking, and logistics. They complement each other: Temporal provides reliability; MCP Dev Latam provides regional commerce tools.
Popular in MCP Servers & Agent Tooling
Smithery
Smithery is an MCP server marketplace and connection layer that handles OAuth, credentials, and session state for your AI agent.
Arcade AI
Arcade AI is the MCP authorization runtime that enforces per-user permissions and logs every action your AI agents take.
Chrome DevTools MCP
Open-source MCP server that gives coding agents live Chrome DevTools for debugging, traces, and browser automation.
Frequently Asked Questions
Categories
Used Mcp Dev Latam? Help shape our editorial sentiment research.