About openfinance-br-mcp
openfinance-br-mcp is an experimental MCP server for Open Finance Brasil, aimed at clients that need to access simulated financial data or explore evolving FAPI-BR integrations. Its credential-free mock mode simulates multiple banks; real institution integrations are not validated.
Key features
- 0118 typed financial tools
- 02In-memory bank simulations
- 03Account, card, and investment data
- 04Consent and PIX payment flows
- 05Bank resource and spending prompt
Use cases
- 01Test financial-data workflows without credentials
- 02Inspect simulated account and card information
- 03Explore consent and PIX payment flows
MCP support
Exposes 18 tools, an `openfinance://banks/` resource, and an `analyze_monthly_spending` prompt over stdio or Streamable HTTP. Optional URL elicitation supports bank authorization flows.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx openfinance-br-mcpENVIRONMENT'mock' (default, no credentials needed - runs entirely in-memory), 'sandbox', or 'production'CLIENT_IDClient ID registered with the participating institution. Required unless ENVIRONMENT=mockPRIVATE_KEY_PATHSecretPath to the RSA private key used for private_key_jwt and JAR signing outside mock modePRIVATE_KEY_KIDSecretKey ID matching the registered client JWKS entry outside mock modeMTLS_CERT_PATHPath to the client mTLS certificate used outside mock modeMTLS_KEY_PATHSecretPath to the client mTLS private key used outside mock modeREDIS_URLSecretOptional Redis connection URL for persistent consent and token stateANTHROPIC_API_KEYSecretRequired only when calling list_transactions with categorize=true (DSPy transaction categorization)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEEnglish · Português
openfinance-br-mcp
Experimental MCP server for Open Finance Brasil, with a complete mock environment and evolving FAPI-BR integration. It is not certified or validated against real institutions; see VALIDATION.md before using it outside
environment=mock.
What it is
An MCP Server that abstracts away the complexity of Open Finance Brasil (FAPI 1.0 Advanced, OAuth2, consent, mTLS) and exposes simple tools to Claude:
Claude → "how much did I spend on food in March?"
Claude uses list_transactions(bank=nubank, categorize=true, date_from=2024-03-01)
Claude → "You spent R$ 847.30 on food in March..."
Supported banks
The mock environment simulates Nubank, Sicoob, Caixa, Banco do Brasil, Bradesco, Itaú, Santander, XP, PicPay, and BTG Pactual with in-memory data and no network access. These are simulations, not certified integrations.
Real adapters and the Payments API journey are experimental and unvalidated.
Payments use the v5 payments-consents/payments-pix Directory families,
dedicated per-consent tokens, verified response JWS, PAR/JAR, consent-payload
binding, and persistent idempotency.
list_pix_keys is a demonstration extension rather than a standardized Open
Finance Brasil endpoint. See VALIDATION.md
for the exact scope.
Available MCP tools
The server exposes 18 tools grouped by journey:
- Accounts:
list_accounts,get_balance,list_transactions - Cards:
list_credit_cards,get_credit_card_bills - Investments:
list_investments,list_funds,list_variable_incomes,list_treasure_titles - PIX:
list_pix_keys,initiate_pix - Data consent:
start_consent,complete_consent,check_consent_status,revoke_consent - Payment consent:
start_payment_consent,complete_payment_consent,check_payment_consent_status
It also exposes the openfinance://banks/ resource, the
analyze_monthly_spending prompt, and optional URL elicitation when starting
an authorization flow.
Quick start
Prerequisites
- Python 3.12 or 3.13
- uv installed
# Run the published release in credential-free mock mode
uvx --from openfinance-br-mcp==0.2.0 openfinance-mcp
From source
git clone https://github.com/brunovicco/openfinance-br-mcp.git
cd openfinance-br-mcp
# Optional: needed only for sandbox/production or DSPy categorization
cp .env.example .env
# Install dependencies
uv sync
# Run the server
uv run openfinance-mcp
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"openfinance-br": {
"command": "uvx",
"args": ["--from", "openfinance-br-mcp==0.2.0", "openfinance-mcp"]
}
}
}
Development
# Install with dev-dependencies
uv sync
# Run the tests
uv run pytest tests/ -v
# Lint and formatting
uv run ruff check src/ tests/
uv run black src/ tests/
# Type check
uv run mypy src/
Containers and Kubernetes
docker compose up openfinance-mcp
docker compose --profile test up
The k8s/ directory contains a two-replica Streamable HTTP example with
Redis-backed state. Replace every credential, signing-key, OAuth issuer,
resource-server, and domain placeholder before applying it. The server fails
closed when HTTP is exposed outside loopback without MCP client OAuth.
Architecture
Claude (MCP Client)
│ stdio or streamable-http
▼
openfinance-br-mcp (MCP Server)
├── Auth + Consent (FAPI-BR 2.2.0: private_key_jwt, PAR/JAR, PKCE, mTLS)
├── MCP Primitives (18 tools + 1 resource + 1 prompt)
│ ├── Pydantic v2 input/output schemas
│ ├── Optional URL elicitation for bank authorization
│ └── Categorizer (DSPy + Claude for transaction classification)
├── Bank Adapters (10 banks - extensible)
└── Directory Client (resolves real bank endpoints from the BCB
Directory of Participants)
│ HTTPS/mTLS
▼
Open Finance BR (BCB) - Directory of Participants
│
▼
Nubank · Sicoob · Caixa · + 100 participating institutions
Environment variables
| Variable | Required | Description |
|---|---|---|
ENVIRONMENT | ❌ | mock (default, no credentials needed), sandbox, or production |
CLIENT_ID | ⚠️ non-mock | Client ID registered with the institution |
PRIVATE_KEY_PATH | ⚠️ non-mock | RSA private key for private_key_jwt/JAR signing |
PRIVATE_KEY_KID | ⚠️ non-mock | kid matching the registered client JWKS |
MTLS_CERT_PATH | ⚠️ prod | Path to the mTLS certificate |
MTLS_KEY_PATH | ⚠️ prod | mTLS private key |
ANTHROPIC_API_KEY | ⚠️ DSPy | Required for categorize=true |
REDIS_URL | ❌ | Shares TokenStore/ConsentManager state across replicas |
MCP_TRANSPORT | ❌ | stdio (default) or streamable-http |
MCP_HTTP_ALLOWED_ORIGINS | ⚠️ remote HTTP | Required allowlist for any non-loopback bind |
LANGFUSE_OTLP_ENDPOINT | ❌ | Enables tracing to Langfuse (with LANGFUSE_PUBLIC_KEY/LANGFUSE_SECRET_KEY) |
LOG_LEVEL | ❌ | INFO, DEBUG, WARNING (default: INFO) |
LOG_FORMAT | ❌ | json or console (default: json) |
See .env.example
for the full list.
Documentation
- Authorization - the two token universes and why they can never cross
- Contributing - dev setup, CI checks, and adding an adapter
- Security - scope, disclaimer, and vulnerability reporting
- Sources - specifications and RFCs followed by the implementation
- Validation - what has and has not been validated
- Changelog - release history
- Releasing - maintainer release procedure
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.