Mcp Cielo

io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026

MCP server for Cielo — credit card, debit, boleto, recurrent payments

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

MCP server for the Cielo payment platform, letting an assistant create and manage card, boleto, Pix, wallet and recurring payments.

What you can do
  • Create and inspect sales: card, debit, 3DS, token-based and wallet payments, plus sale lookup, capture and cancel
  • Manage recurring payments: create, read, change amount or next charge date, deactivate and reactivate
  • Issue and check boleto and Pix payments, including Pix QR codes
  • Tokenize cards and run zero-dollar authorizations to validate a card
  • Create and look up shareable payment links
  • Retrieve anti-fraud analysis details for a payment
When to use it
Useful when an assistant needs to operate a Cielo merchant account directly — creating or cancelling charges, managing subscriptions, issuing Pix or boleto payments, or checking payment and anti-fraud status — and testing against the Cielo sandbox first.
Requirements
Runs locally via npx from the npm package @codespar/mcp-cielo (Node.js). Needs a Cielo developer account with MerchantId and MerchantKey, supplied as CIELO_MERCHANT_ID and CIELO_MERCHANT_KEY; CIELO_SANDBOX=true switches to the sandbox. Network access to Cielo APIs is required. The manifest declares CIELO_API_KEY instead, so check which variables the package actually reads.
Before you install
These tools move real money: creating sales, captures, recurring charges, payment links and reactivations can charge customers, and cancels or deactivations change live payment state. Merchant credentials (CIELO_MERCHANT_ID, CIELO_MERCHANT_KEY) are secrets that grant full account access; keep them out of shared configs and use the sandbox until verified. Card data and payment details are sent to Cielo and, for anti-fraud, to its fraud service.

Installation

In SourceWeft

  1. Open Mcp Cielo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-cielo

MCP server for Cielo — card acquiring, boleto, and recurrent payments

[npm] [License: MIT]

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json
{  "mcpServers": {    "cielo": {      "command": "npx",      "args": ["-y", "@codespar/mcp-cielo"],      "env": {        "CIELO_MERCHANT_ID": "your-merchant-id",        "CIELO_MERCHANT_KEY": "your-merchant-key",        "CIELO_SANDBOX": "true"      }    }  }}

Claude Code

bash
claude mcp add cielo -- npx @codespar/mcp-cielo

Cursor / VS Code

Add to .cursor/mcp.json or .vscode/mcp.json:

json
{  "servers": {    "cielo": {      "command": "npx",      "args": ["-y", "@codespar/mcp-cielo"],      "env": {        "CIELO_MERCHANT_ID": "your-merchant-id",        "CIELO_MERCHANT_KEY": "your-merchant-key",        "CIELO_SANDBOX": "true"      }    }  }}

Tools (22)

ToolPurpose
create_saleCreate a credit/debit card sale in Cielo
get_saleGet sale details by PaymentId
capture_saleCapture a pre-authorized sale
cancel_saleCancel/void a sale (full or partial)
create_recurrentCreate a recurrent (recurring) credit card payment
get_recurrentGet recurrent payment details
tokenize_cardTokenize a credit card for future use
create_boletoCreate a boleto payment in Cielo
create_pixCreate a Pix payment in Cielo (generates QR code)
get_pixGet Pix payment details and QR code by PaymentId
create_debitCreate a debit card sale in Cielo (requires 3DS authentication)
create_ewalletCreate a digital wallet payment (Google Pay, Samsung Pay, Apple Pay)
get_antifraudGet anti-fraud analysis details for a payment
create_sale_with_tokenCreate a credit card sale using a previously stored CardToken (avoids re-entering card data)
update_recurrent_amountUpdate the amount of an existing recurrent payment
update_recurrent_next_dateUpdate the next charge date of an existing recurrent payment
deactivate_recurrentDeactivate (pause) a recurrent payment so it stops charging
reactivate_recurrentReactivate a previously deactivated recurrent payment
create_payment_linkCreate a Cielo Link de Pagamento (shareable checkout URL)
get_payment_linkGet a Cielo Link de Pagamento by its id
zero_authZero-dollar authorization to validate a card without charging (card or CardToken)
create_sale_with_3dsCreate a credit card sale using 3DS 2.0 authentication data (from 3DS flow)

Authentication

Cielo uses MerchantId and MerchantKey headers for authentication.

Sandbox / Testing

Cielo provides a sandbox at apisandbox.cieloecommerce.cielo.com.br. Set CIELO_SANDBOX=true to use it.

Get your credentials

  1. Go to Cielo Developer Portal
  2. Create a developer account
  3. Get your MerchantId and MerchantKey
  4. Set the environment variables

Environment Variables

VariableRequiredDescription
CIELO_MERCHANT_IDYesMerchant ID from Cielo
CIELO_MERCHANT_KEYYesMerchant Key from Cielo
CIELO_SANDBOXNoSet to "true" for sandbox mode

Roadmap

v0.2 (planned)

  • create_pix — Create a Pix payment
  • get_pix — Get Pix payment details
  • create_debit — Create a debit card payment
  • create_ewallet — Create an e-wallet payment (Apple Pay, Google Pay)
  • get_antifraud — Get anti-fraud analysis for a transaction

v0.3 (planned)

  • batch_captures — Capture multiple pre-authorized transactions
  • velocity_rules — Configure velocity/anti-fraud rules

Want to contribute? Open a PR or request a tool.

Links

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Source: packages/payments/cielo/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts