Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Santander Brasil — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS)
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SANTANDER_CLIENT_ID, SANTANDER_CLIENT_SECRET, SANTANDER_CERT_PATH, SANTANDER_KEY_PATH, SANTANDER_ENVValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"santander": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-santander"
],
"env": {
"SANTANDER_CLIENT_ID": "your-value",
"SANTANDER_CLIENT_SECRET": "your-value",
"SANTANDER_CERT_PATH": "your-value",
"SANTANDER_KEY_PATH": "your-value",
"SANTANDER_ENV": "your-value"
}
}
}
}Run this in your terminal
claude mcp add santander --env SANTANDER_CLIENT_ID=your-value --env SANTANDER_CLIENT_SECRET=your-value --env SANTANDER_CERT_PATH=your-value --env SANTANDER_KEY_PATH=your-value --env SANTANDER_ENV=your-value -- npx -y @codespar/mcp-santanderFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"santander": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-santander"
],
"env": {
"SANTANDER_CLIENT_ID": "your-value",
"SANTANDER_CLIENT_SECRET": "your-value",
"SANTANDER_CERT_PATH": "your-value",
"SANTANDER_KEY_PATH": "your-value",
"SANTANDER_ENV": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"santander": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-santander"
],
"env": {
"SANTANDER_CLIENT_ID": "your-value",
"SANTANDER_CLIENT_SECRET": "your-value",
"SANTANDER_CERT_PATH": "your-value",
"SANTANDER_KEY_PATH": "your-value",
"SANTANDER_ENV": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SANTANDER_ENV envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account codespar, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SANTANDER_CLIENT_ID, SANTANDER_CLIENT_SECRET, SANTANDER_CERT_PATH, SANTANDER_KEY_PATH
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0-alpha.3) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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:
https://trust-open.api.santander.com.brhttps://trust-sandbox.api.santander.com.br/auth/oauth/v2/token/collection_bill_management/v2/workspaces/{workspace_id}/bank_slipsRemaining 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.
| Tool | Purpose |
|---|---|
get_oauth_token | Mint or return a cached OAuth2 client_credentials bearer token for the Santander Developer Portal. |
send_pix | Initiate an outbound Pix payment from the merchant's Santander account. |
create_pix_qr | Create a dynamic Pix charge with QR code (cob). |
get_pix | Retrieve a Pix transaction by its BCB endToEndId (E ). |
resolve_dict_key | Resolve a DICT key (CPF, CNPJ, email, phone, EVP) to the owner's account data before sending a Pix. |
refund_pix | Refund (devolução) a previously received Pix. |
create_boleto | Issue a boleto via Santander Cobrança (collection_bill_management v2). |
get_boleto | Retrieve a boleto by its Santander bill_id (SONDA query via collection_bill_management v2). |
cancel_boleto | Cancel (baixa) an outstanding boleto before payment. |
get_statement | Retrieve account statement transactions for a given period. |
create_pix_cobv | Create a Pix charge with due date (cobv — cobrança com vencimento). |
get_pix_cob | Retrieve a Pix immediate charge (cob) by its txid. |
list_pix_cob | List Pix immediate charges (cob) created in a given period. |
update_pix_cob | Update (PATCH) an existing Pix immediate charge. |
list_pix_received | List received Pix (Pix recebidos) in a given period. |
register_dict_key | Register a new DICT key for one of the merchant's Santander accounts. |
delete_dict_key | Remove (unregister) a DICT key previously registered for the merchant. |
download_boleto_pdf | Fetch the PDF (second copy / segunda via) of a registered boleto. |
get_account_balance | Get current available and blocked balance for a Santander merchant account. |
send_ted | Initiate a TED transfer from a Santander merchant account to an account at another bank. |
transfer_internal | Transfer between two Santander accounts (TEF / mesma instituição). |
create_openfinance_consent | Create an Open Finance consent (BACEN-regulated) for data access or payment initiation against a third-part... |
arrecadacao_pay | Pay a utility, tax, or concessionária bill via Santander Arrecadação / Pagamento de Contas. |
npm install @codespar/mcp-santander@0.1.0-alpha.1
SANTANDER_CLIENT_ID="..." # OAuth client_id from Santander's Developer Portal
SANTANDER_CLIENT_SECRET="..." # OAuth client_secret SANTANDER_CERT_PATH="/abs/path/to/client.crt" # mTLS client certificate SANTANDER_KEY_PATH="/abs/path/to/client.key" # mTLS private key SANTANDER_ENV="sandbox" # or "production" (default: sandbox)
Two factors are both required on every call:
/auth/oauth/v2/token on the trust-open (or trust-sandbox) gateway, caches the bearer until ~60s before expiry, and attaches Authorization: Bearer to downstream calls.trust-open gateway enforces it across product families. The server loads the client certificate and private key from the paths you set, builds a Node https.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.
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.
# stdio (default)
npx @codespar/mcp-santander
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-santander
TODO(verify) markers in src/index.ts. Onboarded merchants should validate against their portal-issued OpenAPI spec and open a PR.PATCH with status: "BAIXADO"; the covenant-specific cancellation semantics may differ.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.
MIT