The platform you build on
— and that grows with you

No. Many MCP servers are delivered as a local package that you start, configure and keep up to date yourself — and that only runs as long as your machine runs. The COMMITLY MCP Server is hosted and run by COMMITLY, permanently reachable, monitored and updated. You connect your AI tool once and get going. There is nothing to install, nothing to deploy and nothing to maintain.

No — it sees exactly what the access it is connected to allows. The MCP Server hangs off a COMMITLY account with a role and permissions down to category level. If someone connects who is not allowed to see personnel costs, their language model does not get to see personnel costs either. Every query runs through the same rights and approvals as working in the application. With a spreadsheet or a self-built app that layer does not exist: there the model sees everything in the file.

Yes, through roles and permissions in COMMITLY — the same ones that apply to people. For each access you decide which clients, accounts and categories are visible; the MCP Server sticks to that. Write actions additionally run through the usual approvals. Access can be withdrawn at any time — unlike a shared file, which is a copy once it has been shared.

All models that support the MCP Server protocol — Claude, ChatGPT, Gemini, Mistral and models of your own, local or hosted. The MCP Server is model-independent.

The REST API follows OpenAPI 3.1. You will find the documentation here.

Open banking means regulated access to bank data and payment functions through standardised interfaces — in Europe governed by the PSD2 directive. At the account holder's request, banks make the data available through a secured interface. COMMITLY uses open banking to connect your accounts: balances and transactions flow into your cash flow planning automatically, updated up to four times a day.

A banking API is a programming interface through which software accesses bank data — balances, transactions and, depending on the provider, payment initiation as well. A pure banking API only delivers the data: forecast logic, planning, interface and the compliance chain are things you have to build and run yourself. COMMITLY offers the API on top of the finished platform — you get the planning layer as well and can still access it programmatically.

EBICS (Electronic Banking Internet Communication Standard) is the established standard for communication between companies and banks in German-speaking countries. It is built for corporate customers and is robust where the PSD2 interface reaches its limits — for instance with higher volumes or certain types of account. COMMITLY supports both routes: PSD2 for a fast open banking connection, EBICS for professional corporate banking processes.

Pay by bank means payments triggered straight from the bank account — with no card or payment service provider in between. Usually it refers to paying in e-commerce. COMMITLY uses the same principle somewhere else: when paying your incoming invoices. With COMMITLY Bills you approve invoices and trigger the payment straight from your bank account — inside your approval workflows, with the four-eyes principle and a full audit trail. One point of clarification: COMMITLY is not a payment service provider and does not offer pay by bank as an interface for third parties. The payment is part of the invoice and approval process, not a payment product in its own right.

A pure API (e.g. Nevlo) delivers bank data — everything else you build and run yourself: forecast logic, database, UI, compliance, hosting, security, the ongoing maintenance of the PSD2 interfaces, bug fixing, scaling. And running it is the expensive, permanent part, not the initial build. COMMITLY delivers the finished planning layer AND runs the regulated banking, data and compliance stack. You get the API/MCP on top, to dock your own logic on — without maintaining the infrastructure underneath yourself.

More than 5,000 banks across Europe, through PSD2 (open banking) and EBICS (professional corporate banking). COMMITLY uses several regulated aggregators for this rather than just one — if one aggregator's connection to a bank fails, another can step in. That is not a numbers record, it is a question of day-to-day reliability.

No. You start with the cash flow platform as the core and only add on when your process calls for it — for instance Bills for incoming invoices and payments, Card & Account for company cards or AI Connect for MCP/API access. You can extend at any time but do not have to decide anything in advance.

Access is part of the COMMITLY editions or can be booked as an add-on. Details on the prices page.

Us. COMMITLY runs the entire stack — bank connection, data, compliance, forecast, API and MCP Server. You have one contract and one contact. With an in-house build you depend on several providers at once (banking aggregator, hosting, database, OCR …) and, when something breaks, first have to work out who is responsible — while the providers point at each other.

Yes — that is exactly the hybrid model. COMMITLY serves as the backbone for banking, forecast and compliance, and your own logic docks on via API/MCP.

Yes. COMMITLY supports multiple clients, client data is kept separate, and reporting across all clients can be built through the REST API. Instead of maintaining one Excel file per client, you set it up once and serve many with it.

Nothing — that is exactly why COMMITLY is a shared application and not a file. Several people work on the same state of the data, with roles and approvals, every change is traceable in the audit trail, and backup and restore are managed. With a self-built model, by contrast, the planning depends on the person who built it: if they drop out, the planning drops out.

No, and that is deliberate. COMMITLY is not an enterprise TMS, not an ERP replacement and not a pure API workshop. It adds the cash flow layer to DATEV, lexoffice, sevDesk and your ERP and pulls the data from there — through ready-made integrations, the API or MCP.

Technically yes, and bank access is not the obstacle: regulated aggregators sell PSD2 account access as a service, so you do not need a licence of your own. COMMITLY connects banks the same way. What you buy along with it, though, is a provider contract with onboarding, a data processing agreement, running costs from the very first account and dependence on one provider. And what you get is account data — forecast, plan vs. actual, scenarios and consolidation are things you build yourself. On top of that comes running it: encryption, key management, roles and permissions, audit trail, backup with a tested restore, patching when vulnerabilities appear, GDPR documentation, the 72-hour notification deadline for data breaches and the retention obligations under commercial and tax law. Every one of those is solvable. Together they are not a building job, they are a permanent one.