Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

MCP Caixa

by codesparversion 0.2.0-alpha.3i★ –iRuns on your computer
Registry nameio.github.codespar/mcp-caixa

Install

Overview

Description from the maker (original English)

MCP server for Caixa Econômica Federal — Pix, Cobrança (SICOB boleto), Extrato (OAuth2 + mTLS)

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: CAIXA_CLIENT_ID, CAIXA_CLIENT_SECRET, CAIXA_CERT_PATH, CAIXA_KEY_PATH

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: CAIXA_CLIENT_ID, CAIXA_CLIENT_SECRET, CAIXA_CERT_PATH, CAIXA_KEY_PATH, CAIXA_ENV

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

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-caixa

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • CAIXA_CLIENT_ID required env
    Caixa OAuth client_id issued via the Developer Portal after contract onboarding.
  • CAIXA_CLIENT_SECRET secret required env
    Caixa OAuth client_secret.
  • CAIXA_CERT_PATH required env
    Absolute path to the mTLS client certificate (.crt or .pem). BACEN mandates mTLS for Pix v2.
  • CAIXA_KEY_PATH secret required env
    Absolute path to the mTLS private key (.key or .pem).
  • CAIXA_ENV env
    Environment: 'sandbox' or 'production'. Defaults to 'sandbox'.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account codespar, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32497 servers in this category
  • Published to the registry more recently than 14% of the other 32497 servers in this category
  • Basic checks equal to or better than 100% of the other 32497 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Caixa safe?

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.

What keys or codes does it need?

You need to fill in: CAIXA_CLIENT_ID, CAIXA_CLIENT_SECRET, CAIXA_CERT_PATH, CAIXA_KEY_PATH

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0-alpha.3) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Zoo MCP

by KittyCAD

An MCP server that provides access to the Zoo API for various CAD operations and tools.

Runs on your computerUpdated today
Install

README from the maker

Open the README

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.

@codespar/mcp-caixa

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.

Status: alpha (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.

Tools (23)

ToolPurpose
get_oauth_tokenMint or return a cached OAuth2 client_credentials bearer token for the Caixa Developer Portal.
send_pixInitiate an outbound Pix payment from the merchant's Caixa account.
create_pix_qrCreate a dynamic Pix charge with QR code (cob).
get_pixRetrieve a Pix transaction by its BCB endToEndId (E ).
resolve_dict_keyResolve a DICT key (CPF, CNPJ, email, phone, EVP) to the owner's account data before sending a Pix.
refund_pixRefund (devolução) a previously received Pix.
create_boletoIssue a boleto via Caixa Cobrança (SICOB).
get_boletoRetrieve a boleto by its Caixa identifier (id or nosso_numero).
cancel_boletoCancel (baixa) an outstanding boleto before payment.
get_statementRetrieve account statement transactions for a given period.
get_pix_chargeRetrieve a Pix immediate charge (cob) by its BCB txid.
update_pix_chargeUpdate (PATCH) a Pix immediate charge (cob) — e.g.
list_pix_chargesList Pix immediate charges (cob) filtered by date range and optional status / CPF / CNPJ.
create_pix_due_chargeCreate a Pix due-date charge (cobv) with mandatory payer data and due date.
get_pix_due_chargeRetrieve a Pix due-date charge (cobv) by its BCB txid.
list_pix_receivedList received Pix transactions (pix recebidos) by date range.
register_dict_keyRegister a DICT key (CPF, CNPJ, email, phone, or EVP) to an account owned by the merchant.
delete_dict_keyDelete (unregister) a DICT key owned by the merchant.
download_boleto_pdfFetch the rendered boleto PDF for an issued boleto.
get_account_balanceReturn the current balance for a Caixa merchant account, including available, blocked, and overdraft limit...
transfer_tedInitiate an outbound TED transfer from a Caixa merchant account to an external bank account.
consult_fgtsQuery FGTS balance / extrato.
pay_tributePay a federal tribute (DARF, GPS, GRU) or other guia de arrecadação via Caixa.

Why Caixa (vs. a private bank)

  • Social-program beneficiaries. If a meaningful slice of your customer base receives federal transfers, Caixa is where the money lands first.
  • State-bank credibility. Government-adjacent merchants, concessionárias, and regulated verticals often prefer — or are required — to hold accounts at a state-owned bank.
  • Lottery / Loterias Caixa corridor. Retailers in the lotérica network settle through Caixa.
  • Same Pix / boleto rails as the private banks. No technical tradeoff — the BACEN Pix v2 standard is identical.

Install

npm install @codespar/mcp-caixa@0.1.0-alpha.1

Environment

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)

Authentication

Two factors are both required on every call:

  1. OAuth2 `client_credentials` — the server calls the token endpoint, caches the bearer until ~60s before expiry, and attaches Authorization: Bearer to downstream calls.
  2. mTLS — BACEN mandates mutual TLS for Pix v2, and Caixa 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 Caixa Developer Portal after your merchant contract and credenciamento are approved. They are distinct from the OAuth credentials.

Run

# stdio (default)

npx @codespar/mcp-caixa

HTTP transport

MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-caixa

Caveats

  • Paths are unverified. See the TODO(verify) markers in src/index.ts. Onboarded merchants should validate against their portal-issued OpenAPI spec and open a PR.
  • Sandbox host is a guess. Caixa issues a homologação subdomain per merchant; override by editing BASE_URL if your provisioned sandbox URL differs.
  • SICOB legacy. Older boleto contracts may still route through the legacy SIGCB surface. The create_boleto / get_boleto / cancel_boleto tools target Cobrança v2; if your contract predates it, paths will differ.
  • Onboarding timeline. Factor weeks, not days. State-owned vendor registration is the critical path — start it before you start coding.

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

Ask PopNx