Finom launches read-only MCP connection for Claude and ChatGPT

External

This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.

Finom MCP is built on the open Model Context Protocol (MCP) and works with Claude and ChatGPT. The new Finom MCP connection is included in every Finom plan across Europe.

Finom MCP in brief
• What it is: a connection that lets a Finom customer query their own account from inside Claude or ChatGPT.
• What you can ask: questions about your transactions, wallets, invoices, cards and accounting, plus a morning briefing of recent business activity.
• What it does not do: it does not move money, issue cards or change your account, and it does not give financial, tax, legal, investment or insurance advice.
• Who controls it: the customer, who connects it with their own Finom login, keeps access scoped to their existing role, and can disconnect at any time.
• Availability: included in all Finom plans, rolling out pan-EU from today.

Why this matters now

The daily work of running a business has moved into the AI assistant. Founders and finance teams draft, plan and analyse inside Claude and ChatGPT every day. Checking a number from the business account, though, still means leaving that assistant, signing in to a separate app and reading a table. Finom MCP removes that step. A customer can ask to "analyse all my spendings for 2026" or "list transactions over €500 last month" from inside the assistant they already have open, and get an answer drawn from their live Finom account.

Finom MCP is built on the Model Context Protocol, the open standard that is fast becoming the common way AI assistants connect to the business tools people use. Finom is adopting that standard rather than building a closed integration of its own.

You connect it, and you control it

The customer starts the connection from inside their own assistant, for example in the connector settings of Claude or the plugin section of ChatGPT, and is redirected to a Finom-hosted screen to sign in with their own Finom login and give consent. Access is scoped to the Finom role the customer already holds. No Finom credentials are shared with the AI provider, and the connection can be revoked at any time.

"Every serious conversation about AI and business finance is now happening inside an assistant, where founders already draft, plan and analyse. Their account should be reachable from there. We are not the first to public MCP and we will not pretend to be. We’re starting with a first set of read-only access, with write capabilities to follow, all built on an open standard rather than a walled garden." Kristjan Kaar, CPO of Finom

Starting with read access with more to follow

At launch, Finom MCP reads the account and answers questions. It does not act on the account. This is a deliberate first step. The answers a customer sees are generated by their own AI assistant, so the Finom app remains the authoritative record for official statements and reporting. Data retrieved through MCP is processed by the customer’s chosen AI provider under the customer’s own agreement with that provider.

"MCP is becoming the way assistants talk to the tools people already use, and we adopted it rather than inventing our own. The engineering that matters here is not the model, it is the boundaries around it: your own login, access scoped to the role you already have, nothing shared beyond what you ask, and the ability to switch it off." Ivo Dimitrov, CAIO and co-founder of Finom.

The direction

Finom is describing what comes next in phases rather than dated promises:

• Today: read questions across transactions, invoices, cards, wallets and accounting, and a morning briefing, from inside your assistant.
• Next: a first set of everyday actions your assistant can prepare for you to confirm, with secure authentication, so nothing moves until you approve it.
• Later: more product areas plug into the same connection over time.