
Mcp Itau
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026
MCP server for Itaú Unibanco — Pix, Cobrança (boleto), Arrecadação, Extrato (OAuth2 + mTLS)
Overview
Local MCP server exposing Itaú Unibanco banking APIs — Pix, boleto, arrecadação and statements — to an assistant via OAuth2 and mTLS.
- What you can do
- Authenticate against the Itaú Developer Portal and obtain a cached OAuth2 bearer token for downstream calls (get_oauth_token). Send, retrieve and refund Pix payments, create immediate and due-date Pix charges, and list charges by date range. Resolve, register, list and delete DICT keys (CPF, CNPJ, email, phone, EVP). Issue, retrieve, cancel and download the PDF of boletos, and pay utility, tax or concessionária bills via Arrecadação. Read account statements, query tariff schedules, list DDA bills, send TED transfers, move funds between Itaú accounts, and schedule future-dated payments.
- When to use it
- For Brazilian merchants or developers already onboarded with Itaú who want an assistant to drive Pix, boleto, arrecadação and cash-management operations. Best suited to sandbox experimentation first, given the alpha status and unverified endpoint paths.
- Requirements
- Runs locally as an npm package over stdio (HTTP transport optional). Requires Node.js, an Itaú Developer Portal contract with OAuth client credentials (ITAU_CLIENT_ID, ITAU_CLIENT_SECRET) and an mTLS certificate and private key from the portal (ITAU_CERT_PATH, ITAU_KEY_PATH). ITAU_ENV selects sandbox (default) or production; network access to Itaú endpoints is needed.
Installation
In SourceWeft
- Open Mcp Itau 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-itau
MCP server for Itaú Unibanco — Brazil's largest private bank.
Itaú operates the largest private-bank API surface in the country. Merchants running high-volume Pix, boleto, and cash-management workloads integrate directly instead of going through a PSP.
Status: alpha (0.1.0-alpha.1)
Itaú'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 endpoint paths in this server are best-guesses based on (a) BACEN Pix v2 standard paths, (b) Itaú's public marketing pages, and (c) conventions shared across Santander / 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 (22)
Install
Environment
Authentication
Two factors are both required on every call:
- OAuth2
client_credentials— the server calls the token endpoint, caches the bearer until ~60s before expiry, and attachesAuthorization: Bearer <token>to downstream calls. - mTLS — BACEN mandates mutual TLS for Pix v2, and Itaú 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 Itaú Developer Portal after your merchant contract is signed. They are distinct from the OAuth credentials.
Run
Caveats
- 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. - Sandbox host is a guess. Itaú issues a sandbox subdomain per merchant; override by editing
BASE_URLif your provisioned sandbox URL differs. - 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/itau/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