mcpField
M
mcp-braspag

mcp-braspag

Local
github.com/codesparFinance275Updated 4w ago

About mcp-braspag

mcp-braspag is an MCP server for Braspag, the enterprise orchestration layer of Cielo Group, offering multi-acquirer routing, a card token vault (Cartão Protegido), recurring payments, and marketplace split. It is intended for large Brazilian retailers that keep their own acquiring contract. It differs from the direct-acquiring mcp-cielo server.

Key features

  1. 01Sale creation and capture across acquirers
  2. 02Cartão Protegido card tokenization and deletion
  3. 03Recurring payment schedule management
  4. 04Marketplace split sales and split capture
  5. 05Wrappers for boleto, Pix, and 3DS sales

Use cases

  1. 01Reusing stored card tokens across multiple acquirers
  2. 02Managing recurring charges for subscription billing
  3. 03Splitting marketplace payments among sub-merchants

MCP support

The project is an MCP server that exposes 22 tools to MCP clients for calling the Braspag Transaction and Query APIs.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"codespar-mcp-braspag": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-braspag"
],
"env": {
"BRASPAG_MERCHANT_ID": "<BRASPAG_MERCHANT_ID>",
"BRASPAG_MERCHANT_KEY": "<BRASPAG_MERCHANT_KEY>",
"BRASPAG_ENV": "<BRASPAG_ENV>"
}
}
}
}
Run commandnpx -y @codespar/mcp-braspag
Environment variables to set
BRASPAG_MERCHANT_IDSecretBraspag MerchantId (UUID)
BRASPAG_MERCHANT_KEYSecretBraspag MerchantKey (secret)
BRASPAG_ENVEnvironment: 'sandbox' or 'production'. Defaults to 'sandbox'.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@codespar/mcp-braspag0.2.2

Tools

22

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
PaymentobjectYesBraspag Payment object. Shape depends on Type. For CreditCard/DebitCard pass a CreditCard/DebitCard sub-object. For Boleto pass Provider/ExpirationDate. For Pix, Amount is enough. For EletronicTransfer (TEF), pass Provider.
Payment.TypeenumYesPayment method typeCreditCard | DebitCard | Boleto | Pix | EletronicTransfer
Payment.AmountnumberYesAmount in cents (e.g. 15700 = R$157.00)
CustomerobjectYesCustomer identification (Braspag shape)
Customer.NamestringYesCustomer full name
MerchantOrderIdstringYesMerchant-side order id (appears in reports)

Details

From the project README

@codespar/mcp-braspag

MCP server for Braspag — Cielo Group's enterprise orchestration layer: multi-acquirer routing, token vault (Cartão Protegido), recurrence, marketplace split, antifraud orchestration.

npm License: MIT

Braspag vs. Cielo (Acquirer)

CodeSpar ships two Cielo Group servers with different business contracts:

ServerProductWhat it isWho uses it
@codespar/mcp-cieloCielo AcquirerDirect card acquiring rails (credit, debit, boleto, Pix)Any merchant taking cards through Cielo
@codespar/mcp-braspag (this)Braspag / PagadorEnterprise orchestration on top of any acquirerEnterprise BR retail (Magalu-tier): multi-acquirer routing, token vault, marketplace split

Braspag orchestrates across acquirers. You keep your Cielo (or Rede, or Stone) acquiring contract and layer Braspag on top for: smart routing, failover, vaulting cards once and reusing across acquirers (Cartão Protegido), driving recurrence, and splitting marketplace capture across sub-merchants.

Quick Start

Claude Desktop

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

{
  "mcpServers": {
    "braspag": {
      "command": "npx",
      "args": ["-y", "@codespar/mcp-braspag"],
      "env": {
        "BRASPAG_MERCHANT_ID": "your-merchant-uuid",
        "BRASPAG_MERCHANT_KEY": "your-merchant-key",
        "BRASPAG_ENV": "sandbox"
      }
    }
  }
}
Claude Code
claude mcp add braspag -- npx @codespar/mcp-braspag
Cursor / VS Code

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

{
  "servers": {
    "braspag": {
      "command": "npx",
      "args": ["-y", "@codespar/mcp-braspag"],
      "env": {
        "BRASPAG_MERCHANT_ID": "your-merchant-uuid",
        "BRASPAG_MERCHANT_KEY": "your-merchant-key",
        "BRASPAG_ENV": "sandbox"
      }
    }
  }
}

Tools (22)

ToolPurpose
create_saleCreate a sale on the Braspag Transaction API (POST /sales).
capture_saleCapture a pre-authorized sale (PUT /sales/{paymentId}/capture).
void_saleVoid / cancel a sale (PUT /sales/{paymentId}/void).
create_recurrentCreate a recurrent payment schedule (POST /recurrentPayments).
disable_recurrentDeactivate a recurrent payment (PUT /recurrentPayments/{recurrentPaymentId}/Deactivate).
update_recurrent_amountUpdate the charged amount on a recurrent payment (PUT /recurrentPayments/{recurrentPaymentId}/Amount).
get_saleGet sale detail by PaymentId (GET /sales/{paymentId} — Query API).
get_sale_by_order_idLook up sale(s) by MerchantOrderId (GET /sales?merchantOrderId=X — Query API).
get_recurrentGet a recurrent payment's configuration and history (GET /recurrentPayments/{recurrentPaymentId} — Query API).
tokenize_cardTokenize a card into the Braspag vault / Cartão Protegido (POST /card).
get_card_tokenRetrieve the stored card data associated with a Cartão Protegido token (GET /card/{token}).
create_split_saleCreate a sale with marketplace split rules (POST /sales with Payment.SplitPayments).
create_sale_3dsCreate a 3DS-authenticated credit sale (POST /sales).
create_zero_authZero-dollar authorization / card validation (POST /zeroauth).
create_boleto_saleConvenience wrapper to create a Boleto sale (POST /sales with Payment.Type=Boleto).
create_pix_saleConvenience wrapper to create a Pix sale (POST /sales with Payment.Type=Pix).
reactivate_recurrentReactivate a previously deactivated recurrent payment (PUT /recurrentPayments/{recurrentPaymentId}/Reactiva...
update_recurrent_next_paymentUpdate the NextPaymentDate on a recurrent payment (PUT /recurrentPayments/{recurrentPaymentId}/NextPaymentD...
update_recurrent_paymentUpdate the Payment (CreditCard + Customer) on a recurrent schedule (PUT /recurrentPayments/{recurrentPaymen...
create_antifraud_analysisSubmit a standalone Antifraud analysis (POST /fraudanalysis) through Braspag's antifraud orchestration (Cyb...
delete_card_tokenDelete a Cartão Protegido vault token (DELETE /card/{token}).
create_split_captureCapture a previously authorized split sale with overridden per-sub-merchant amounts (PUT /sales/{paymentId}...

Authentication

Braspag uses MerchantId (UUID) and MerchantKey (secret) headers on both the Transaction API and the Query API.

Environments

EnvTransaction APIQuery API
sandbox (default)https://apisandbox.braspag.com.br/v2https://apiquerysandbox.braspag.com.br/v2
productionhttps://api.braspag.com.br/v2https://apiquery.braspag.com.br/v2

Set via BRASPAG_ENV=production to switch.

Get your credentials
  1. Reach out to your Cielo / Braspag account team to enable Braspag Pagador on your merchant contract.
  2. Receive your MerchantId (UUID) and MerchantKey.
  3. Set the environment variables below.

Environment Variables

VariableRequiredDescription
BRASPAG_MERCHANT_IDYesMerchant UUID
BRASPAG_MERCHANT_KEYYesMerchant secret key
BRASPAG_ENVNosandbox (default) or production

Roadmap

v0.2 (planned)
  • create_sale_with_card_token — convenience wrapper that uses a Cartão Protegido token
  • delete_card_token — revoke a vault token
  • get_sale_antifraud — Query API antifraud detail
  • update_recurrent_payment — update non-amount fields on a recurrent
  • create_zero_auth — zero-dollar auth for card validation
v0.3 (planned)
  • Marketplace: sub-merchant onboarding endpoints
  • Bank slip (boleto) registered-only helpers
  • Webhook verification helper

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

Links

Enterprise

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

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.