Lexware Office MCP Server

MCP server to interact with Lexware Office. The lexware office mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

An MCP server for Lexware Office (formerly Lexoffice). It lets MCP-capable assistants query and manage contacts, sales documents, vouchers, files, payments, webhooks, and reference data through the Lexware Office public API.

• Broad Lexware Office API coverage — for read and write workflows
• Sales documents — invoices, quotations, order confirmations, credit notes, delivery notes, dunning notices, and down-payment invoices
• Contact management — create, read, and update customers and vendors
• Bookkeeping — vouchers, posting categories, payments, and file uploads
• Reference data — profile, countries, print layouts, payment conditions, recurring templates
• Webhooks — create, list, inspect, and delete event subscriptions

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — The Prerequisites tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 3 environment variables: LEXWARE_OFFICE_API_KEY, LEXWARE_OFFICE_READ_ONLY, LEXWARE_OFFICE_ALLOW_WRITES. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 22 or higher - LEXWARE_OFFICE_API_KEY environment variable

When to reach for it

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lexware Office's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by JannikWempe; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the lexware office mcp server does with a few real requests.