Lexware Office MCP server: connect AI agents to lexoffice from the EU

Lexware Office is the cloud accounting product of Haufe-Lexware in Freiburg, Germany, used by small businesses and freelancers for quotes, invoices, receipts and bookkeeping. It was called lexoffice until its rename and offers a public REST API, but no MCP server.

The community server JannikWempe/mcp-lexware-office covers that API in Code Mode. Instead of dozens of endpoint tools, it offers search and execute, which run sandboxed JavaScript against the API. This keeps the tool list short while still covering pagination, aggregation and reports. It is MIT licensed and runs as a stdio process.

A typical request is a receivables overview: the agent pages through all open invoices, groups them by customer and age, and writes a short list for the weekly finance meeting. Another is month-end preparation: compare vouchers with bank payments from another connector and list receipts that are still missing.

With writes allowed, an agent can create a new customer contact from an email signature, prepare a quotation as a draft, or upload a receipt PDF so it is ready for booking in Lexware Office.

Create an API key in Lexware Office under the public API add-on at app.lexoffice.de/addons/public-api. On inference.eu, add the Lexware Office connector to an agent and paste the key; it is stored encrypted in the EU and never shown again in full.

Keep LEXWARE_OFFICE_READ_ONLY=true at first. The key carries the rights of the account that created it, so read-only is the safest start. When you need drafts or uploads, set LEXWARE_OFFICE_ALLOW_WRITES=true and remove the read-only flag.

The server sends requests straight to the Lexware Office API, so your accounting data goes to Haufe-Lexware, a German company, just as it does when you use the web app. No extra service sits between the agent and Lexware.

On inference.eu the model reads the results in EU data centres, and your API key is stored encrypted in the EU. Invoices and contacts include personal data of customers, so check that your agreement with Haufe-Lexware covers processing through an API integration.

Read-only is the default, and the server's scripts run in a sandbox that can only call relative Lexware API paths. Finalised invoices cannot be changed afterwards under German bookkeeping rules, so keep agents to drafts.

On inference.eu you can require a person to approve each execute call that writes, such as creating a contact or uploading a file, before it runs. Pair this with the server's audit logs, so you can see which requests the agent sent and why.