Haufe and AI: Is there an MCP server for Haufe?

Haufe is a provider of expert content and software based in Freiburg, Germany. Several products stand behind the name. This page separates them, because their AI interfaces differ a lot.

In short

Yes, with limits. Haufe runs an official MCP server for Haufe Copilot via API. It covers the Haufe CoPilots, not the ERP software Haufe X360 and not Haufe Personal Office. Access needs a service agreement, an API key and a licence ID. Haufe announces an update of the server. For X360 there is a third-party connector (AnythingMCP, open source).

Which Haufe products this covers

• Haufe Copilot via API: Haufe’s interface to its AI assistants (CoPilots). The MCP server belongs here.
• Haufe CoPilots: According to Haufe there are seven, including CoPilot HR, Tax, Finance, Sustainability and RE. They run inside the Haufe Office products, for example CoPilot HR in Haufe Personal Office.
• Haufe X360: Haufe’s ERP software. According to Haufe, it has its own AI Assistant.
• Lexware Office (lexoffice): also belongs to Haufe-Lexware and has its own page: Lexware Office in the MCP directory.

What Haufe offers itself

The MCP server. According to the Haufe documentation, it lets any MCP-compatible agent call Haufe Copilot tools without building a REST integration. The endpoint is https://api.haufe.ai/agents/v1/mcp, and the transport is Streamable HTTP. Without sign-in, the endpoint answers with 401. The documentation lists six tools. They cover tax law, employment and HR law, sustainability (ESRS, CSRD), real estate law, accounting and general German law. Each tool takes one argument, user_message, and returns an answer from the copilot. The documentation names no tool to change or delete data.

Access and licence. The server needs the header api-key. For each tool, a separate header license-id-<area> is added, for example license-id-hr. According to the documentation, Haufe checks the licence on every tool call. According to the documentation, the server shows only the tools that match the API key. The Haufe contact enables further copilots. According to Haufe, the Developer Portal requires an active service agreement, and a Haufe contact must approve the registration. For prices, Haufe refers to your contact. It also names no restriction to certain clients. The example is for Claude Code (.mcp.json). The page says nothing about ChatGPT and Microsoft Copilot.

The announced update. The page carries the note: “An update is on the way”. According to Haufe, the new version changes how you use the server. The page describes the current version. Haufe does not say what changes.

Limits. According to Haufe, tool calls count against the rate limit for answers. The usage guidelines forbid using answers for machine learning and require visible attribution of the content to Haufe. Haufe recommends not rewording answers. This matters for agents that summarise answers.

A REST API. According to Haufe, Copilot via API has a REST API with an API key or OAuth user tokens, and it works with any HTTP-capable platform.

Haufe X360. According to Haufe, systems can be connected to X360 through a REST API or a SOAP API. We found no public documentation of this API at Haufe. The interfaces page shows ready-made connections and refers to the ISV team. We found no official MCP server for X360. According to Haufe, the AI Assistant is available from version 26R1 and answers questions about data in X360 as text, tables, charts or pivot views. According to Haufe, it works read-only (AI security). The separate AI Automation feature writes AI results into record fields, according to Haufe, and uses a language model chosen by the customer.

Data location. According to the Haufe documentation, the service processes data exclusively in data centres in Europe. The privacy policy of the documentation site says in general: the contractually agreed processing takes place in data centres in the EU or the EEA. Transfers to the US are possible during maintenance and support. According to the Haufe press release, all Haufe AI solutions run on European servers. According to the Haufe FAQ, the service uses language models from third parties such as OpenAI and Azure OpenAI and does not train on customer data. We found no statement on where these providers process the data. The privacy policy describes the website. It does not say whether it expressly covers the API service.

What third parties offer

We found no MCP server on GitHub that is built only for Haufe. The open-source gateway AnythingMCP by helpcode.ai (AGPL-3.0) includes a connector for Haufe X360 with seven tools. According to AnythingMCP, it reads customers, vendors, stock items, sales orders, A/R invoices and shipments through the REST API and changes nothing. According to its licensing notes, the self-hosted Community edition is free for up to 3 active users. The cloud variant is a paid service with a 7-day trial. We did not test the connector against an X360 system. The page proves neither what Haufe says about it nor whether Haufe knows the connector. At Zapier and viaSocket we found no Haufe page at the obvious addresses. That does not prove there is no entry there.

What this means for your company

• For Haufe Copilot you need a service agreement with Haufe. Clarify licence IDs and price with your Haufe contact.
• Plan for the announced update: the setup may change.
• The MCP server returns answers from the copilot, not data from your Haufe X360 or Personal Office installation.
• We found no official MCP route for Haufe X360. A third-party connector needs an X360 user with read rights. Ask your Haufe X360 partner about the API.
• The data goes to language model providers. Review the data processing agreement with Haufe.