The agent is the interface

What an MCP server is

The Model Context Protocol is an open standard through which an AI agent calls tools. A program exposes its capabilities as named tools, the agent calls them, and it gets structured answers back. No screen scraping, no guessing at form fields.

The difference from a chat window inside accounting software is where the capability sits. A chat window is a feature in a product. An MCP server is the product, callable from outside, by whichever agent you choose.

In TILL the MCP server was not added afterwards. It is the interface the Studio itself speaks through. What you can do in the Studio, an agent can do too, and the other way round. There is no second, poorer path for machines.

The Swiss market does not have this yet

As of July 2026

No Swiss or German-speaking SME accounting vendor has shipped an official MCP server. That is a claim about official, vendor-maintained servers, and it is meant narrowly.

Community-built wrappers do exist, among others for Lexoffice, sevDesk, DATEV and bexio. They are real work and often useful. But they sit on top of the REST interface the vendor built for something else, and they can only pass through what that interface already offers.

This is not a complaint about those vendors. It is an observation about when a piece of software was built and what for. Anyone building a GUI in 2015 was not building tools for agents that did not exist.

A flat wrapper is not enough

As of July 2026

Every official MCP server from the large accounting vendors is currently a flat wrapper around the existing REST interface. QuickBooks ships 144 tools. That sounds like richness and is the opposite.

An agent asked to write an invoice has to work out, from those 144, which seven it needs and in what order, and hold every intermediate state together itself. Each step is a chance to do something halfway. In bookkeeping, a half-finished operation is precisely what nobody wants.

TILL cuts its tools along the operations a human would name anyway. One operation is one call, it applies whole or not at all, and it is idempotent: the same call twice does not post twice. The number of tools is not the point. The cut is the point.

What this means day to day

You tell your agent what happened and it records it. It reads the bank statement in camt.053 format, proposes the matching and posts it once you approve. It prepares the MWST return and shows you which entries every figure came from.

You keep the ledger itself, not just a log of it. Every entry an agent makes sits in the same file as your own, with the same provenance and the same audit trail.

And you keep control of the agent. TILL does not ship one. You connect the one you trust, and you decide what it may do.

The human stays in it

Agent first does not mean nobody looks any more. TILL ships the Studio, a GUI for exactly the moments a human has to decide: review, approve, correct, look at the closing.

Posted entries stay immutable. A correction is a reversing entry, never a silent overwrite. That holds for you and for the agent, and it is the reason you can trust an entry a machine made at all.