--- title: "lexoffice MCP server · Connect AI agents to Lexware Office" description: "Connect inference.eu agents to Lexware Office, formerly lexoffice, through an open-source MCP server. Query contacts, invoices and vouchers, read-only by default." canonical: "https://inference.eu/connect/lexoffice/" language: "en" --- MCP servers · Accounting # Lexware Office MCP server: connect AI agents to lexoffice from the EU Lexware Office, known as lexoffice until its rename, has no MCP server of its own. The open-source Lexware Office MCP server covers its public API with just two tools and blocks writes unless you allow them. inference.eu agents use it with your Lexware API key to answer questions about invoices, vouchers and contacts. [Contact sales](https://inference.eu/contact/)[What agents can do with it](#tools) 1. 01Authentication: API key 2. 02Community server 3. 03EU data centres ## What agents can do with it - 1 ### Search the API catalogue \`search\` runs a small sandboxed script against a curated catalogue of the Lexware Office API, so the agent finds the right endpoint and fields for contacts, sales documents, vouchers, payments or files. - 2 ### Execute API workflows \`execute\` runs a sandboxed script with one capability, \`lexware.request\`, for relative \`/v1/...\` calls, so a single tool call can page through results, aggregate totals and build a multi-step report. - 3 ### Guarded writes and uploads With \`LEXWARE\_OFFICE\_ALLOW\_WRITES=true\` the agent can create contacts, draft sales documents, upload receipt files and manage webhooks. \`LEXWARE\_OFFICE\_READ\_ONLY=true\` blocks all of this, whatever else is set. ## What Lexware Office and this MCP server are 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. ## What agents can do with Lexware Office 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. ## Setup and authentication 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. ## Data protection and where the data goes 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. ## Approvals and safe use 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. ## Lexware Office (lexoffice) Vendor Haufe-Lexware GmbH & Co. KG Vendor based in Germany Category Accounting Authentication API key Transport Local (stdio) Server [Community server](https://github.com/JannikWempe/mcp-lexware-office) Documentation [developers.lexware.io](https://developers.lexware.io/docs/) ## Lexware Office (lexoffice): common questions The questions buyers, developers and legal teams ask us most. Something missing? Ask us directly. No. As of November 2026 Haufe-Lexware has not released an MCP server for Lexware Office or lexoffice. Community servers on GitHub use the public API. This page uses JannikWempe/mcp-lexware-office, which is not affiliated with Haufe-Lexware. Yes. lexoffice was renamed Lexware Office, and the public API stayed the same. Older guides and searches still use lexoffice, which is why many people look for a lexoffice MCP server. The server on this page works with current Lexware Office accounts. It uses Code Mode. The \`search\` tool lets the agent look up endpoints in a curated catalogue, and \`execute\` runs a short sandboxed script against the API. That keeps the context small and allows multi-step reports, paging and totals in a single call. Only if you allow writes. The server blocks POST, PUT, PATCH and DELETE requests unless \`LEXWARE\_OFFICE\_ALLOW\_WRITES=true\` is set, and a read-only flag overrides that. Keep invoices as drafts and let a person finalise them. Sign in to Lexware Office and open the public API add-on at app.lexoffice.de/addons/public-api. Create a key and copy it once. On inference.eu you paste it into the connector, where it is stored encrypted in the EU. From the Lexware Office API directly to the agent, with no other provider in between. The model on inference.eu processes it in EU data centres. Haufe-Lexware handles the data under your existing contract. Yes, with writes allowed. The server supports binary-safe file uploads for vouchers, so a receipt PDF from email or a document store can be attached in Lexware Office and is then ready for booking by your team. Yes. lazyants/lexware-mcp-server offers 66 endpoint tools and stores the token in the OS keyring, and marselsel/Lexware-MCP-Server is a self-hosted HTTP server with OAuth 2.1. All are community projects, not products of Haufe-Lexware. [Ask a question](https://inference.eu/contact/) ## Related [All MCP servers](https://inference.eu/connect/#directory) - [sevdeskConnect inference.eu agents to sevdesk through an open-source MCP server. Audit VAT, reconcile bank payments and draft invoices, read-only by default.Accounting](https://inference.eu/connect/sevdesk/) - [DATEVConnect inference.eu agents to DATEV through an MCP server. Read postings, clients and documents, and prepare uncommitted booking batches for review.Accounting](https://inference.eu/connect/datev/) - [QontoConnect inference.eu agents to the official Qonto MCP server. Read transactions and invoices, issue client invoices and manage cards, within Qonto's approvals.Banking and payments](https://inference.eu/connect/qonto/) ## Move your AI workloads to EU infrastructure Tell us which models you use and roughly how much traffic you have. We reply within one working day with pricing and next steps. - Reply within one working day - Pricing for your volume - DPA ready to sign