Use Lexware Office with AI via MCP
Lexware Office – known as lexoffice before the rename – runs day-to-day accounting in many German companies. MCP access comes from the community, and we operate it as a container in your CompanyGPT environment, read-only by default.
What is Lexware Office?
Lexware Office is the cloud accounting solution from Haufe-Lexware GmbH & Co. KG in Freiburg, previously marketed as lexoffice. The product covers quotes and invoices, receipt capture, bank reconciliation, payroll functions and the handover to the tax advisor, and is built consistently around German requirements.
What matters for AI use is that these records are accessible through a public API. An agent can look up receipts and invoices, summarize situations and answer questions that would otherwise require someone to open the application and filter.
Connection at a Glance
- MCP server
- Community (JannikWempe/mcp-lexware-office), self-hosted
- Transport
- Container in the CompanyGPT environment
- Authentication
- API key
- Default behavior
- Read-only as shipped
- Operating model
- SaaS accounting, MCP server in your own tenant
- Origin
- German product (formerly lexoffice), Haufe-Lexware
How to Connect Lexware Office to CompanyGPT
There is currently no vendor MCP server for Lexware Office. What is available is a mature community server, JannikWempe/mcp-lexware-office, which accesses the Lexware Office API through an API key and operates read-only by default – write operations are a deliberate decision rather than the starting state.
We run this server as a container in your CompanyGPT environment. The data path stays entirely under your control: CompanyGPT calls the container inside your own cloud tenant, and the container calls the Lexware Office API. No additional operator is involved that could see or store accounting data.
The API key is stored in the protected configuration area of the instance. Via roles and groups, your CompanyGPT administrators decide who may work with the integration.
Typical Use Cases
How AI agents in CompanyGPT work with Lexware Office
Receipt status without switching systems
A chat question settles whether an incoming invoice has been recorded and paid – useful for project leads who have no accounting access of their own.
Invoice overview for sales
Ahead of a customer meeting, an agent summarizes which invoices for that customer are open or were recently settled.
Groundwork for the tax advisor
The agent compiles which documents exist for a given period and names the gaps that should be closed before handover.
Frequently Asked Questions
Lexware Office and AI – the most important answers
Is there an official MCP server for Lexware Office?
Not from the vendor at this time. We use the mature community server JannikWempe/mcp-lexware-office, which accesses the Lexware Office API via an API key.
Is access write-enabled by default?
No. The server operates read-only by default, so write operations require a deliberate decision rather than being the starting state.
Where is the server operated?
As a container in your CompanyGPT environment. CompanyGPT and the MCP server run in your own cloud tenant, and requests go from there directly to Lexware Office.
Isn't the product called lexoffice?
The solution was previously known as lexoffice and is now offered by Haufe-Lexware under the name Lexware Office. It is the same product.
Who may use the integration?
Your CompanyGPT administrators define that via roles and groups, so access can be limited to accounting and management, for example.
Lexware Office and Your AI – GDPR-Compliant with CompanyGPT
CompanyGPT is the enterprise AI assistant in your own cloud tenant: all relevant AI models, your company data and integrations like Lexware Office – centrally managed, with roles and permissions. We set up the connection together with you.
Lexware Office is a trademark of its respective owner (Haufe-Lexware GmbH & Co. KG). Its mention describes compatibility and does not imply any partnership or endorsement. Availability and scope of the connection depend on the respective vendor.