
Open Banking (open-banking.io)
io.github.open-banking-ioPublished by GitHub account open-banking-iov0.1.0Updated Oct 27, 2026
Read-only MCP server for the open-banking.io PSD2 bank API — accounts, balances, transactions.
Overview
Read-only MCP server for the open-banking.io PSD2 bank API, letting an assistant list your accounts, balances, transactions and bank connections.
- What you can do
- List bank accounts with bank, country, IBAN, owner, currency, balances and a reconnect flag
- Read ISO 20022 booked and available balances for a single account
- Fetch statement lines newest first, with optional date range, limit and offset, including counterparty and remittance details
- List bank connections and consents with status, validity date, last sync time and account count
- When to use it
- Useful when you want an assistant to answer questions about your own bank accounts, such as current balances, spending summaries for a period, or which consents expire soon, without giving it any ability to move money.
- Requirements
- Runs locally over stdio as a Python package launched with uv (uvx or from source). Needs credentials exported from the open-banking.io app, supplied via OBI_CREDENTIALS (path or inline JSON bundle) or the split OBI_API_KEY, OBI_PRIVATE_KEY and OBI_BASE_URL variables. Network access to the open-banking.io API is required.
Installation
In SourceWeft
- Open Open Banking (open-banking.io) 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
open-banking.io MCP server
A thin, read-only Model Context Protocol server for the open-banking.io PSD2 API. It lets AI agents (Claude Desktop, Cursor, any MCP client) answer questions like “What's my balance?” and “Summarise last month's transactions” over your own bank accounts.
It wraps the official open-banking-io Python SDK
and inherits its zero-knowledge property: the service only ever returns ciphertext, and every
sensitive field (IBAN, owner name, amounts, counterparties) is decrypted in-process with your
exported private key. No plaintext ever touches a third party — including the LLM only sees what
your MCP client sends it.
Tools
All tools are read-only. There are intentionally no sync, payment-initiation or consent-management tools — see Limitations.
Configuration
Export credentials in the app → Settings → Credentials to get the bundle file.
Claude Desktop
claude_desktop_config.json (Claude → Settings → Developer → Edit Config):
Cursor
.cursor/mcp.json:
Requires uv (curl -LsSf https://astral.sh/uv/install.sh | sh).
Once published to PyPI the --from git+… argument can be dropped.
Run locally / from source
Example questions for your agent
- “Show the booked balance of every account.”
- “How much did I spend on groceries in July?” (
get_transactions+ grouping) - “Which of my bank connections expire soon?” (
list_connections)
Design notes
- Read-only by construction. Only the SDK's
get_*methods are exposed.sync/sync_allexist in the SDK but are deliberately not offered; agents cannot move money or alter consents through this server. - Exact money. Amounts are returned as exact decimal strings (
"1234.56"), never floats. - Clean errors. Missing credentials, bad dates, unknown account ids and upstream HTTP errors are surfaced as actionable tool errors (e.g. listing valid account ids on a miss).
- Context-friendly.
get_transactionsdefaults to 50 items and clamps at 500 to protect agent context windows; useoffsetto paginate.
Limitations (honest list)
- No write tools: no sync, no payment initiation, no consent creation/renewal. Consent renewal always happens in the open-banking.io app (PSD2 SCA).
- No bank/institution directory tool: the upstream API (SDK v1.0.0) does not expose a public ASPSP-search endpoint — TODO if/when the API adds one.
- Not yet on PyPI — install via
uvx --from git+…(above) or from source. Publishing to PyPI asopen-banking-io-mcpis planned. - Data minimisation is your responsibility: transactions include counterparties and remittance text; only point this server at MCP clients you trust, and prefer local MCP clients (Claude Desktop / Cursor) over hosted ones for privacy.
API surface wrapped
Auth: X-Api-Key header. Responses carry zero-knowledge envelopes
(ECDH P-256 → HKDF-SHA256 → AES-256-GCM) decrypted locally by the SDK.
Full wire format: clients repo ·
THREAT_MODEL.md.
License
MIT — same as the clients SDK repos.
Source: README.md at commit aa18c9c
Tools
0Version history
1- v0.1.0LatestSep 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