
Mcp Santander
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026
MCP server for Santander Brasil — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS)
Overview
Alpha MCP server for Santander Brasil banking: Pix, boletos, Arrecadação, statements and transfers via OAuth2 plus mTLS.
- What you can do
- Mint and cache OAuth2 tokens for the Santander gateway
- Send Pix, create Pix charges and QR codes, look up transactions, resolve DICT keys, refund Pix, register or delete DICT keys
- Issue, retrieve, cancel and download PDFs of boletos, and create Pix charges with due date
- Read account statements and balances
- Send TED transfers, move money between Santander accounts, pay utility or tax bills, and create Open Finance consents
- When to use it
- For merchants with a signed Santander Brasil contract who want an assistant to handle Pix, boleto and cash-management operations directly rather than through a PSP. Best tried in sandbox first, since the package is an early alpha.
- Requirements
- Runs locally as an npm package (Node.js) over stdio, or over HTTP when MCP_HTTP and MCP_PORT are set. Needs a Santander Developer Portal contract, SANTANDER_CLIENT_ID, SANTANDER_CLIENT_SECRET, an mTLS certificate and key via SANTANDER_CERT_PATH and SANTANDER_KEY_PATH, and SANTANDER_ENV (sandbox by default). Network access to Santander's trust-open or trust-sandbox gateway.
Installation
In SourceWeft
- Open Mcp Santander 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-santander
MCP server for Santander Brasil — 3rd largest private bank in Brazil.
Completes the top-3 BR private-bank trio: Itaú + Bradesco + Santander. Same OAuth2 + mTLS shape as its peers; different merchant contract.
Merchants with meaningful Pix, boleto, and cash-management volume integrate directly with Santander instead of going through a PSP.
Status: alpha (0.1.0-alpha.1)
Santander's Developer Portal is contract-gated — the full OpenAPI specs for Pix, Cobrança, Arrecadação, and Extrato are only visible to onboarded merchants. The following pieces are verified against Santander's public integration guides:
- Production host:
https://trust-open.api.santander.com.br - Sandbox host:
https://trust-sandbox.api.santander.com.br - OAuth2 token:
/auth/oauth/v2/token - Cobrança v2 base:
/collection_bill_management/v2/workspaces/{workspace_id}/bank_slips
Remaining paths (Pix, Arrecadação, Extrato) are best-guesses based on (a) BACEN Pix v2 standard paths, (b) Santander public marketing, and (c) conventions shared across Itaú / Bradesco / BB. Every unverified path is flagged TODO(verify) in the source.
Pin to exact versions during 0.1.x; paths will be corrected to match the portal spec once an onboarded merchant can validate.
Tools (23)
Install
Environment
Authentication
Two factors are both required on every call:
- OAuth2
client_credentials— the server POSTs to/auth/oauth/v2/tokenon thetrust-open(ortrust-sandbox) gateway, caches the bearer until ~60s before expiry, and attachesAuthorization: Bearer <token>to downstream calls. - mTLS — BACEN mandates mutual TLS for Pix v2, and Santander's
trust-opengateway enforces it across product families. The server loads the client certificate and private key from the paths you set, builds a Nodehttps.Agent, and routes every request through it.
You obtain the cert + key bundle from the Santander Developer Portal after your merchant contract is signed. They are distinct from the OAuth credentials.
Cobrança: workspace model
Santander's Cobrança v2 is workspace-scoped. Before registering boletos you provision one or more workspace_ids via the Developer Portal — each binds a convênio, boleto/Pix billing mode, and webhook URL. The create_boleto, get_boleto, and cancel_boleto tools all take a workspace_id argument.
Run
Caveats
- Pix / Arrecadação / Extrato paths are unverified. See the
TODO(verify)markers insrc/index.ts. Onboarded merchants should validate against their portal-issued OpenAPI spec and open a PR. - Cobrança cancel is modelled as a
PATCHwithstatus: "BAIXADO"; the covenant-specific cancellation semantics may differ. - Arrecadação barcode validation is server-side in this alpha — no client-side mod-10 / mod-11 check yet.
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/banking/santander/README.md at commit d0a519a
Tools
0Version history
1- v0.2.0-alpha.3LatestSep 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