Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Caixa Econômica Federal — Pix, Cobrança (SICOB boleto), 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.
CAIXA_CLIENT_ID, CAIXA_CLIENT_SECRET, CAIXA_CERT_PATH, CAIXA_KEY_PATH, CAIXA_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": {
"caixa": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-caixa"
],
"env": {
"CAIXA_CLIENT_ID": "your-value",
"CAIXA_CLIENT_SECRET": "your-value",
"CAIXA_CERT_PATH": "your-value",
"CAIXA_KEY_PATH": "your-value",
"CAIXA_ENV": "your-value"
}
}
}
}Run this in your terminal
claude mcp add caixa --env CAIXA_CLIENT_ID=your-value --env CAIXA_CLIENT_SECRET=your-value --env CAIXA_CERT_PATH=your-value --env CAIXA_KEY_PATH=your-value --env CAIXA_ENV=your-value -- npx -y @codespar/mcp-caixaFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"caixa": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-caixa"
],
"env": {
"CAIXA_CLIENT_ID": "your-value",
"CAIXA_CLIENT_SECRET": "your-value",
"CAIXA_CERT_PATH": "your-value",
"CAIXA_KEY_PATH": "your-value",
"CAIXA_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": {
"caixa": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-caixa"
],
"env": {
"CAIXA_CLIENT_ID": "your-value",
"CAIXA_CLIENT_SECRET": "your-value",
"CAIXA_CERT_PATH": "your-value",
"CAIXA_KEY_PATH": "your-value",
"CAIXA_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.
CAIXA_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: CAIXA_CLIENT_ID, CAIXA_CLIENT_SECRET, CAIXA_CERT_PATH, CAIXA_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 Caixa Econômica Federal — Brazil's largest state-owned bank.
Caixa occupies a segment none of the private tier-1 banks (Itaú, Bradesco, Santander, BB) can cover: it runs federal social programs (PIS/PASEP, FGTS, Bolsa Família / Auxílio Brasil), operates the national lottery (Loterias Caixa), and is the preferred bank for merchants that value state-bank credibility or serve beneficiaries of federal transfer programs. For the payment surface that matters to merchants — Pix, boleto (Cobrança / SICOB), and extrato — Caixa follows the BACEN Pix v2 standard shared across every tier-1 bank, so the integration shape mirrors its private-sector peers.
0.1.0-alpha.1)Caixa's Developer Portal is contract-gated, and as a state-owned institution the onboarding is additionally bureaucratic: vendor registration and credenciamento are required on top of the commercial merchant contract. Full OpenAPI specs for Pix, Cobrança (SICOB), and Extrato are only visible to onboarded merchants. The endpoint paths in this server are best-guesses based on (a) BACEN Pix v2 standard paths, (b) Caixa's public SICOB / Cobrança integration guides, and (c) conventions shared with 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 Caixa Developer Portal. |
send_pix | Initiate an outbound Pix payment from the merchant's Caixa 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 Caixa Cobrança (SICOB). |
get_boleto | Retrieve a boleto by its Caixa identifier (id or nosso_numero). |
cancel_boleto | Cancel (baixa) an outstanding boleto before payment. |
get_statement | Retrieve account statement transactions for a given period. |
get_pix_charge | Retrieve a Pix immediate charge (cob) by its BCB txid. |
update_pix_charge | Update (PATCH) a Pix immediate charge (cob) — e.g. |
list_pix_charges | List Pix immediate charges (cob) filtered by date range and optional status / CPF / CNPJ. |
create_pix_due_charge | Create a Pix due-date charge (cobv) with mandatory payer data and due date. |
get_pix_due_charge | Retrieve a Pix due-date charge (cobv) by its BCB txid. |
list_pix_received | List received Pix transactions (pix recebidos) by date range. |
register_dict_key | Register a DICT key (CPF, CNPJ, email, phone, or EVP) to an account owned by the merchant. |
delete_dict_key | Delete (unregister) a DICT key owned by the merchant. |
download_boleto_pdf | Fetch the rendered boleto PDF for an issued boleto. |
get_account_balance | Return the current balance for a Caixa merchant account, including available, blocked, and overdraft limit... |
transfer_ted | Initiate an outbound TED transfer from a Caixa merchant account to an external bank account. |
consult_fgts | Query FGTS balance / extrato. |
pay_tribute | Pay a federal tribute (DARF, GPS, GRU) or other guia de arrecadação via Caixa. |
npm install @codespar/mcp-caixa@0.1.0-alpha.1
CAIXA_CLIENT_ID="..." # OAuth client_id from Caixa's Developer Portal
CAIXA_CLIENT_SECRET="..." # OAuth client_secret CAIXA_CERT_PATH="/abs/path/to/client.crt" # mTLS client certificate CAIXA_KEY_PATH="/abs/path/to/client.key" # mTLS private key CAIXA_ENV="sandbox" # or "production" (default: sandbox)
Two factors are both required on every call:
Authorization: Bearer to downstream calls.https.Agent, and routes every request through it.You obtain the cert + key bundle from the Caixa Developer Portal after your merchant contract and credenciamento are approved. They are distinct from the OAuth credentials.
# stdio (default)
npx @codespar/mcp-caixa
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-caixa
TODO(verify) markers in src/index.ts. Onboarded merchants should validate against their portal-issued OpenAPI spec and open a PR.BASE_URL if your provisioned sandbox URL differs.create_boleto / get_boleto / cancel_boleto tools target Cobrança v2; if your contract predates it, paths will 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