MCP Server

Active

MIT

io.github.codespar/mcp-cielo MCP Server

io.github.codespar/mcp-cielo

MCP access to Cielo's Brazilian payment gateway: credit card, debit, boleto, and recurring charges.

What is the io.github.codespar/mcp-cielo MCP server?

The Cielo MCP server (io.github.codespar/mcp-cielo) is an MCP server that exposes Cielo's payment processing API — credit card, debit card, boleto, and recurring payments — as tools for AI agents. It's part of the MCP Dev LATAM catalog, a collection of 110 MCP servers covering payments, banking, fiscal, logistics, messaging, and ERP services across Latin America. It requires an API Key for authentication and provides 22 tools.

mcp-cielo is one of 110 MCP servers in the MCP Dev LATAM catalog, purpose-built to let AI agents operate real business workflows in Latin America. It wraps Cielo, a major Brazilian payment processor, exposing 22 tools for handling credit card, debit card, boleto, and recurrent payment operations via API key authentication. It fits into larger agent-driven commerce loops alongside fiscal (NFe), logistics, messaging, ERP, and banking servers in the same catalog, letting an agent charge a customer, issue an invoice, ship a product, and reconcile a balance without human intervention.

How to install io.github.codespar/mcp-cielo

Copy-paste configuration for popular MCP clients.

transport: stdio

Config generated by PluginBench — verify against the source before use.

Environment / auth

CIELO_API_KEY
required
secret
API key for cielo

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-cielo": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-cielo"
      ],
      "env": {
        "CIELO_API_KEY": "<YOUR_CIELO_API_KEY>"
      }
    }
  }
}

Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-cielo": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-cielo"
      ],
      "env": {
        "CIELO_API_KEY": "<YOUR_CIELO_API_KEY>"
      }
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-cielo": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-cielo"
      ],
      "env": {
        "CIELO_API_KEY": "<YOUR_CIELO_API_KEY>"
      }
    }
  }
}

VS Code

.vscode/mcp.json

{
  "servers": {
    "mcp-cielo": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-cielo"
      ],
      "env": {
        "CIELO_API_KEY": "<YOUR_CIELO_API_KEY>"
      }
    }
  }
}

Claude Code

claude mcp add mcp-cielo --env CIELO_API_KEY=<YOUR_CIELO_API_KEY> -- npx -y @codespar/mcp-cielo

Use cases

Process a credit or debit card charge through Cielo from an AI agent workflow
Generate and manage boleto payments for Brazilian customers
Set up and manage recurring/subscription payments via Cielo
Integrate Cielo payment confirmation into a larger agentic commerce loop (payment -> fiscal invoice -> shipping -> ERP)

io.github.codespar/mcp-cielo MCP server FAQ

What does the Cielo MCP server do?

It exposes Cielo's Brazilian payment gateway API as MCP tools, allowing an AI agent to process credit card, debit card, boleto, and recurring payments.

Is the Cielo MCP server free to use?

The server code is MIT licensed and free to install via npm, but using it requires a Cielo merchant account and API key, which may involve Cielo's own account/contract fees.

How do I install mcp-cielo in Claude Desktop or Cursor?

Add it to your MCP client config to run via npx, e.g. `npx -y @codespar/mcp-cielo`, and supply the required Cielo API Key as an environment variable, similar to other servers in the catalog (e.g. `{"command": "npx", "args": ["-y", "@codespar/mcp-cielo"], "env": {"API_KEY": "your-key"}}`).

What authentication does mcp-cielo require?

It requires an API Key issued by Cielo for your merchant account.

How many tools does the Cielo server provide?

22 tools, covering credit card, debit card, boleto, and recurrent payment operations.

Is this an official Cielo product?

No, it's a community-built MCP server from the MCP Dev LATAM (codespar) open-source catalog, not an official Cielo integration.

README (reference)

Source of truth, from the repository.

<h1 align="center">MCP Dev LATAM 🌎</h1> 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. 110 MCP servers · 2,300 tools · 6 countries · MIT License <a href="https://codespar.dev/servers">Catalog</a> · <a href="#quick-start">Quick Start</a> · <a href="#agentic-payment-protocols">Agentic Protocols</a> · <a href="#all-servers">All Servers</a> · <a href="docs/CONTRIBUTING.md">Contribute</a> <a href="https://opensource.org/licenses/MIT"><img src="https://img.shields.io/badge/License-MIT-blue.svg" alt="License: MIT"></a> <img src="https://img.shields.io/badge/servers-110-green" alt="110 servers"> <img src="https://img.shields.io/badge/tools-2,300-orange" alt="2300 tools"> <img src="https://img.shields.io/badge/countries-6-blue" alt="6 countries"> <img src="https://img.shields.io/badge/MCP-compatible-purple" alt="MCP compatible">

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` <sub>alpha</sub>	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 <sub>alpha</sub>	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 <sub>alpha</sub>	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 <sub>alpha</sub>	22	`@codespar/mcp-rede`	API Key
Safrapay <sub>alpha</sub>	22	`@codespar/mcp-safrapay`	OAuth2
Worldpay <sub>alpha</sub>	22	`@codespar/mcp-worldpay`	API Key
Khipu <sub>alpha</sub>	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 <sub>alpha</sub>	20	`@codespar/mcp-izipay`	API Key
Picpay <sub>alpha</sub>	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 <sub>alpha</sub>	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 <sub>alpha</sub>	23	`@codespar/mcp-caixa`	OAuth2
Santander <sub>alpha</sub>	23	`@codespar/mcp-santander`	OAuth2
Bradesco <sub>alpha</sub>	22	`@codespar/mcp-bradesco`	OAuth2
Itau <sub>alpha</sub>	22	`@codespar/mcp-itau`	OAuth2
Matera <sub>alpha</sub>	22	`@codespar/mcp-matera`	OAuth2
Dock <sub>alpha</sub>	20	`@codespar/mcp-dock`	OAuth2
Open Finance	18	`@codespar/mcp-open-finance`	API Key
C6 <sub>alpha</sub>	14	`@codespar/mcp-c6`	OAuth2
Banco Do Brasil <sub>alpha</sub>	13	`@codespar/mcp-banco-do-brasil`	OAuth2
Sicoob <sub>alpha</sub>	13	`@codespar/mcp-sicoob`	OAuth2
BTG <sub>alpha</sub>	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 (7 servers)

Server	Tools	npm	Auth
Vtex	33	`@codespar/mcp-vtex`	API Key
Shopify	28	`@codespar/mcp-shopify`	API Key
Amazon <sub>alpha</sub>	24	`@codespar/mcp-amazon`	OAuth2
Shopee <sub>alpha</sub>	22	`@codespar/mcp-shopee`	API Key
Correios <sub>alpha</sub>	21	`@codespar/mcp-correios`	API Key
Melhor Envio	18	`@codespar/mcp-melhor-envio`	API Key
SuperFrete	11	`@codespar/mcp-superfrete`	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 <sub>alpha</sub>	18	`@codespar/mcp-unico`	OAuth2

🛡️ Fraud & Risk (4 servers)

Server	Tools	npm	Auth
Sift <sub>alpha</sub>	20	`@codespar/mcp-sift`	API Key
Clearsale <sub>alpha</sub>	18	`@codespar/mcp-clearsale`	API Key
Konduto <sub>alpha</sub>	18	`@codespar/mcp-konduto`	API Key
Legiti <sub>alpha</sub>	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 <sub>alpha</sub>	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 <sub>alpha</sub>	22	`@codespar/mcp-colppy`	API Key
AFIP <sub>alpha</sub>	20	`@codespar/mcp-afip`	API Key
Andreani <sub>alpha</sub>	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 <sub>alpha</sub>	19	`@codespar/mcp-coordinadora`	API Key
Nequi <sub>alpha</sub>	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 <sub>alpha</sub>	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 (--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.

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

View repository →