
Mcp Stone
- 265 repo stars
- Updated July 16, 2026
- codespar/mcp-dev-brasil
io.github.codespar/mcp-stone is a MCP server that connects agents to Stone open banking, payments, Pix, and transfers.
About
io.github.codespar/mcp-stone is a stdio Model Context Protocol server that lets AI coding agents interact with Stone’s Brazilian open banking, payment, Pix, and transfer APIs. Developers who already process cards or Pix through Stone can add @codespar/mcp-stone, configure STONE_CLIENT_SECRET, and accelerate integration work—generating payment flows, debugging webhooks, or drafting transfer logic—without leaving the agent session. It is a credentials-bound financial connector, not a compliance consultant; you remain responsible for OAuth/client secret handling and production guardrails. Version 0.1.2 from the mcp-dev-brasil monorepo positions it clearly on Skillselion’s Build → Integrations shelf for LATAM payments, distinct from generic developer utilities or security audit skills.
- Open banking, payments, Pix, and transfers per Stone MCP description
- @codespar/mcp-stone npm v0.1.2 with stdio transport
- STONE_CLIENT_SECRET required secret for API authentication
- Published from codespar/mcp-dev-brasil (packages/payments/stone)
- Pairs conceptually with mcp-stark-bank for multi-provider Brazil stacks
Mcp Stone by the numbers
- Data as of Jul 24, 2026 (Skillselion catalog sync)
claude mcp add --env STONE_CLIENT_SECRET=YOUR_STONE_CLIENT_SECRET mcp-stone -- npx -y @codespar/mcp-stoneAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 265 |
|---|---|
| Package | @codespar/mcp-stone |
| Transport | STDIO |
| Auth | Required |
| Last updated | July 16, 2026 |
| Repository | codespar/mcp-dev-brasil ↗ |
What it does
Connect your coding agent to Stone for open banking, Pix, payments, and transfers while you ship Brazil payment features.
Who is it for?
Best when you use Stone acquirer/banking APIs and want agent-assisted Pix, payment, and transfer implementation.
Skip if: Merchants not on Stone, global-only Stripe stacks, or teams that need accounting (Siigo) rather than payment acquiring.
What you get
With STONE_CLIENT_SECRET set, your agent can call Stone-backed MCP tools while you build and refine Brazil payment integrations.
- Configured Stone MCP stdio server in agent settings
- Agent tools for open banking, payments, Pix, and transfers
- Secret STONE_CLIENT_SECRET stored outside committed config
By the numbers
- Package version 0.1.2 (@codespar/mcp-stone)
- 4 capability areas in description: open banking, payments, Pix, transfers
- 1 required secret env var: STONE_CLIENT_SECRET
README.md
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.
109 MCP servers · 2,289 tools · 6 countries · MIT License
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 that bridge the emerging agentic payment stack:
| Protocol | Server | Tools | What it does |
|---|---|---|---|
| Google UCP | @codespar/mcp-ucp |
20 | Universal Commerce Protocol — agentic shopping, cart, checkout, orders, delivery, identity. Google's full commerce stack for AI agents. |
| Stripe ACP | @codespar/mcp-stripe-acp |
24 | Agentic Commerce Protocol — AI agent checkout, payment delegation, products, invoices. Live in ChatGPT with 1M+ Shopify merchants. |
| x402 | @codespar/mcp-x402 |
10 | HTTP-native micropayments by Coinbase — when an agent hits a 402, it pays USDC on Base/Solana and retries. Pure HTTP, no checkout UI. |
| AP2 | @codespar/mcp-ap2 alpha |
22 | Google's Agent-to-Agent Payment Protocol — authorization, audit trails, scoped spend limits. 60+ partners including Visa, Mastercard, Stripe, PayPal. |
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
├── Full commerce? → Google UCP (search → cart → checkout → delivery)
├── Retail checkout? → Stripe ACP (create_checkout → complete_checkout)
├── API micropayment? → x402 (pay_request → USDC $0.001 → data returned)
├── Agent-to-agent? → AP2 (authorize_payment → execute_payment)
└── 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, C6, Sicoob, Bradesco, Matera), 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-ucp # Google Universal Commerce Protocol
npx @codespar/mcp-x402 # HTTP micropayments (Coinbase)
npx @codespar/mcp-ap2@alpha # Agent-to-Agent payment authorization
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 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".
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>/.
💳 Payments (40 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Mercado Pago | 30 | @codespar/mcp-mercado-pago |
API Key |
| Stripe | 30 | @codespar/mcp-stripe |
API Key |
| Zoop | 28 | @codespar/mcp-zoop |
API Key |
| Adyen | 25 | @codespar/mcp-adyen |
API Key |
| Asaas | 24 | @codespar/mcp-asaas |
API Key |
| Pagseguro | 24 | @codespar/mcp-pagseguro |
API Key |
| Stripe ACP | 24 | @codespar/mcp-stripe-acp |
API Key |
| Iugu | 23 | @codespar/mcp-iugu |
API Key |
| Openpay | 23 | @codespar/mcp-openpay |
API Key |
| AP2 alpha | 22 | @codespar/mcp-ap2 |
API Key |
| Braintree | 22 | @codespar/mcp-braintree |
API Key |
| Braspag | 22 | @codespar/mcp-braspag |
API Key |
| Cielo | 22 | @codespar/mcp-cielo |
API Key |
| Inter Bank | 22 | @codespar/mcp-inter-bank |
OAuth2 |
| Mercado Libre | 22 | @codespar/mcp-mercado-libre |
API Key |
| Nubank alpha | 22 | @codespar/mcp-nubank |
OAuth2 |
| Nupay | 22 | @codespar/mcp-nupay |
OAuth2 |
| Pagar Me | 22 | @codespar/mcp-pagar-me |
API Key |
| Rapyd | 22 | @codespar/mcp-rapyd |
API Key |
| Rede alpha | 22 | @codespar/mcp-rede |
API Key |
| Safrapay alpha | 22 | @codespar/mcp-safrapay |
OAuth2 |
| Worldpay alpha | 22 | @codespar/mcp-worldpay |
API Key |
| Khipu alpha | 21 | @codespar/mcp-khipu |
API Key |
| Stone | 21 | @codespar/mcp-stone |
API Key |
| Wise | 21 | @codespar/mcp-wise |
API Key |
| Airwallex | 20 | @codespar/mcp-airwallex |
OAuth2 |
| Culqi | 20 | @codespar/mcp-culqi |
API Key |
| Getnet | 20 | @codespar/mcp-getnet |
OAuth2 |
| Izipay alpha | 20 | @codespar/mcp-izipay |
API Key |
| Picpay alpha | 20 | @codespar/mcp-picpay |
API Key |
| UCP | 20 | @codespar/mcp-ucp |
API Key |
| Vindi | 20 | @codespar/mcp-vindi |
API Key |
| Paypal | 19 | @codespar/mcp-paypal |
OAuth2 |
| Transbank alpha | 19 | @codespar/mcp-transbank |
API Key |
| Celcoin | 18 | @codespar/mcp-celcoin |
API Key |
| dLocal | 18 | @codespar/mcp-dlocal |
API Key |
| Ebanx | 18 | @codespar/mcp-ebanx |
API Key |
| Efi | 18 | @codespar/mcp-efi |
API Key |
| Pix BCB | 18 | @codespar/mcp-pix-bcb |
API Key |
| Chargebee | 15 | @codespar/mcp-chargebee |
API Key |
🏦 Banking (12 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Stark Bank | 27 | @codespar/mcp-stark-bank |
API Key |
| Caixa alpha | 23 | @codespar/mcp-caixa |
OAuth2 |
| Santander alpha | 23 | @codespar/mcp-santander |
OAuth2 |
| Bradesco alpha | 22 | @codespar/mcp-bradesco |
OAuth2 |
| Itau alpha | 22 | @codespar/mcp-itau |
OAuth2 |
| Matera alpha | 22 | @codespar/mcp-matera |
OAuth2 |
| Dock alpha | 20 | @codespar/mcp-dock |
OAuth2 |
| Open Finance | 18 | @codespar/mcp-open-finance |
API Key |
| C6 alpha | 14 | @codespar/mcp-c6 |
OAuth2 |
| Banco Do Brasil alpha | 13 | @codespar/mcp-banco-do-brasil |
OAuth2 |
| Sicoob alpha | 13 | @codespar/mcp-sicoob |
OAuth2 |
| BTG alpha | 12 | @codespar/mcp-btg |
OAuth2 |
📄 Fiscal (Brasil) (4 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Nuvem Fiscal | 24 | @codespar/mcp-nuvem-fiscal |
API Key |
| Nfe Io | 22 | @codespar/mcp-nfe-io |
API Key |
| Conta Azul | 20 | @codespar/mcp-conta-azul |
API Key |
| Focus Nfe | 19 | @codespar/mcp-focus-nfe |
API Key |
📱 Communication (8 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Z API | 27 | @codespar/mcp-z-api |
API Key |
| Evolution API | 25 | @codespar/mcp-evolution-api |
API Key |
| Twilio | 22 | @codespar/mcp-twilio |
API Key |
| Whatsapp Cloud | 22 | @codespar/mcp-whatsapp-cloud |
API Key |
| Sendgrid | 20 | @codespar/mcp-sendgrid |
API Key |
| Rd Station | 18 | @codespar/mcp-rd-station |
API Key |
| Take Blip | 18 | @codespar/mcp-take-blip |
API Key |
| Zenvia | 18 | @codespar/mcp-zenvia |
API Key |
📦 E-commerce / Logistics (6 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Vtex | 33 | @codespar/mcp-vtex |
API Key |
| Shopify | 28 | @codespar/mcp-shopify |
API Key |
| Amazon alpha | 24 | @codespar/mcp-amazon |
OAuth2 |
| Shopee alpha | 22 | @codespar/mcp-shopee |
API Key |
| Correios alpha | 21 | @codespar/mcp-correios |
API Key |
| Melhor Envio | 18 | @codespar/mcp-melhor-envio |
API Key |
📊 ERP / Accounting (5 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Omie | 30 | @codespar/mcp-omie |
API Key |
| Bling | 28 | @codespar/mcp-bling |
API Key |
| Xero | 24 | @codespar/mcp-xero |
API Key |
| Quickbooks | 22 | @codespar/mcp-quickbooks |
API Key |
| Tiny | 21 | @codespar/mcp-tiny |
API Key |
🪪 Identity & KYC (5 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Brasil API | 24 | @codespar/mcp-brasil-api |
No auth |
| Jumio | 20 | @codespar/mcp-jumio |
API Key |
| Onfido | 20 | @codespar/mcp-onfido |
API Key |
| Persona | 20 | @codespar/mcp-persona |
API Key |
| Unico alpha | 18 | @codespar/mcp-unico |
OAuth2 |
🛡️ Fraud & Risk (4 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Sift alpha | 20 | @codespar/mcp-sift |
API Key |
| Clearsale alpha | 18 | @codespar/mcp-clearsale |
API Key |
| Konduto alpha | 18 | @codespar/mcp-konduto |
API Key |
| Legiti alpha | 18 | @codespar/mcp-legiti |
API Key |
🪙 Crypto / Stablecoins (9 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Circle | 23 | @codespar/mcp-circle |
API Key |
| Foxbit | 21 | @codespar/mcp-foxbit |
API Key |
| Bitso | 20 | @codespar/mcp-bitso |
API Key |
| Mercado Bitcoin | 20 | @codespar/mcp-mercado-bitcoin |
API Key |
| Moonpay | 20 | @codespar/mcp-moonpay |
API Key |
| Unblockpay | 13 | @codespar/mcp-unblockpay |
API Key |
| Coinbase Commerce | 18 | @codespar/mcp-coinbase-commerce |
API Key |
| Transak alpha | 18 | @codespar/mcp-transak |
API Key |
| x402 | 10 | @codespar/mcp-x402 |
API Key |
🇦🇷 Argentina (5 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Tienda Nube | 24 | @codespar/mcp-tienda-nube |
API Key |
| Colppy alpha | 22 | @codespar/mcp-colppy |
API Key |
| AFIP alpha | 20 | @codespar/mcp-afip |
API Key |
| Andreani alpha | 18 | @codespar/mcp-andreani |
API Key |
| BCRA | 16 | @codespar/mcp-bcra |
No auth |
🇨🇴 Colombia (5 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Siigo | 22 | @codespar/mcp-siigo |
API Key |
| Wompi | 22 | @codespar/mcp-wompi |
API Key |
| Alegra | 20 | @codespar/mcp-alegra |
API Key |
| Coordinadora alpha | 19 | @codespar/mcp-coordinadora |
API Key |
| Nequi alpha | 16 | @codespar/mcp-nequi |
OAuth2 |
🇲🇽 Mexico (6 servers)
| Server | Tools | npm | Auth |
|---|---|---|---|
| Belvo | 24 | @codespar/mcp-belvo |
API Key |
| Skydropx | 23 | @codespar/mcp-skydropx |
API Key |
| Conekta | 21 | @codespar/mcp-conekta |
API Key |
| Bind ERP | 20 | @codespar/mcp-bind-erp |
API Key |
| Facturapi | 20 | @codespar/mcp-facturapi |
API Key |
| STP/SPEI alpha | 18 | @codespar/mcp-stp-spei |
API Key |
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 (
--httpflag) - 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.
Contributing
We welcome contributions. See 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.
Recommended MCP Servers
How it compares
Stone payments MCP integration, not Stark Bank’s banking API set—choose by your existing processor contract.
FAQ
Who is io.github.codespar/mcp-stone for?
Brazil-focused developers and tiny teams on Stone who want Cursor, Claude Code, or Codex to invoke payment and Pix APIs through MCP.
When should I use io.github.codespar/mcp-stone?
Use it during build when integrating open banking, card or Pix payments, or transfers that Stone already powers for your business.
How do I add io.github.codespar/mcp-stone to my agent?
Register @codespar/mcp-stone with stdio MCP, add STONE_CLIENT_SECRET as a required secret env var, and restart your agent client.