
Mcp Braspag
io.github.codesparPublished by GitHub account codesparv0.2.2Updated Oct 24, 2026
MCP server for Braspag — Cielo orchestration, token vault (Cartão Protegido), recurrence, split
Overview
Local MCP server for Braspag (Cielo Group) that lets an assistant create, capture, void and query payments, manage recurrence, vault cards and split…
- What you can do
- Create, capture and void sales, including boleto, Pix, 3DS and zero-dollar card validation
- Look up sales by payment ID or merchant order ID
- Tokenize, retrieve and delete cards in the Cartão Protegido vault
- Create, deactivate, reactivate and update recurrent payment schedules, amounts and next payment dates
- Create split sales and capture split sales with per-sub-merchant amounts
- Submit standalone antifraud analyses
- When to use it
- Meant for merchants and teams already running Braspag Pagador who want an assistant to drive payment operations: charging, capturing, refunding, recurring billing, card vaulting, marketplace splits and antifraud checks, typically first in the sandbox environment.
- Requirements
- Runs locally via npx from the npm package @codespar/mcp-braspag (Node.js). Requires a Braspag merchant contract enabled by the Cielo/Braspag account team, with BRASPAG_MERCHANT_ID and BRASPAG_MERCHANT_KEY set as environment variables; BRASPAG_ENV selects sandbox (default) or production. Network access to Braspag APIs.
Installation
In SourceWeft
- Open Mcp Braspag in the dashboard and add it to a workspace.
- 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-braspag
MCP server for Braspag — Cielo Group's enterprise orchestration layer: multi-acquirer routing, token vault (Cartão Protegido), recurrence, marketplace split, antifraud orchestration.
Braspag vs. Cielo (Acquirer)
CodeSpar ships two Cielo Group servers with different business contracts:
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:
Claude Code
Cursor / VS Code
Add to .cursor/mcp.json or .vscode/mcp.json:
Tools (22)
Authentication
Braspag uses MerchantId (UUID) and MerchantKey (secret) headers on both the Transaction API and the Query API.
Environments
Set via BRASPAG_ENV=production to switch.
Get your credentials
- Reach out to your Cielo / Braspag account team to enable Braspag Pagador on your merchant contract.
- Receive your MerchantId (UUID) and MerchantKey.
- Set the environment variables below.
Environment Variables
Roadmap
v0.2 (planned)
create_sale_with_card_token— convenience wrapper that uses a Cartão Protegido tokendelete_card_token— revoke a vault tokenget_sale_antifraud— Query API antifraud detailupdate_recurrent_payment— update non-amount fields on a recurrentcreate_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
Source: packages/payments/braspag/README.md at commit d0a519a
Tools
0Version history
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