Skip to content

MCP server

Lexware Office MCP Server

MCP server for the Lexware Office (Lexoffice) API, letting assistants query and manage contacts, invoices, vouchers, payments, files and webhooks.

  • Community
  • Runs locally
  • API key

Repository and documentation last checked Built from public product pages and documentation. SourcesClaim this listing

ecommerceguide summary

Lexware Office MCP Server connects MCP-capable assistants to the Lexware Office (formerly Lexoffice) public API, covering contacts, sales documents such as invoices, quotations and credit notes, vouchers, payments, file uploads, webhooks and reference data. It is a community project by Jannik Wempe, written in TypeScript under an MIT licence, run locally over stdio via npx or Docker with a LEXWARE_OFFICE_API_KEY. Writes are blocked unless LEXWARE_OFFICE_ALLOW_WRITES is set to true.

Why it stands out

Uses Code Mode: two tools, search and execute, run sandboxed JavaScript against the Lexware API instead of per-endpoint tools.

What Lexware Office MCP Server does

ecommerceguide editorial
  • Community MCP server by Jannik Wempe, MIT licence, TypeScript
  • Exposes two tools: search the API catalogue, execute sandboxed calls
  • Covers invoices, credit notes, contacts, vouchers, payments, files, webhooks
  • Read-only by default; writes need LEXWARE_OFFICE_ALLOW_WRITES=true
  • Runs locally over stdio via npx or a Docker image
  • Setup documented for Claude Desktop; needs Node.js 22 or higher
  • Binary-safe file uploads by absolute path or base64 content

How ecommerce teams could use it

ecommerceguide editorial

Illustrative scenarios written by ecommerceguide from the product's documented capabilities. They are not customer case studies.

  1. A German ecommerce seller that keeps its books in Lexware Office

    Looking up customer records and outstanding sales documents during month-end close

    Intended outcomeThe assistant queries contacts, invoices and vouchers through the execute tool while the server stays read-only

  2. A DACH store operator with a technical team using Claude Desktop

    Issuing invoices and credit notes and attaching receipt PDFs to vouchers

    Intended outcomeWith LEXWARE_OFFICE_ALLOW_WRITES enabled, the server posts documents and uploads files from an absolute path on the host machine

  3. A developer building internal finance tooling on Lexware Office

    Subscribing to Lexware events and checking which subscriptions exist

    Intended outcomeThe server creates, lists, inspects and deletes webhook event subscriptions through the same two MCP tools

Who it suits

ecommerceguide editorial

Best for

You keep your accounting in Lexware Office, can run a local Node.js or Docker MCP server with an API key, and work in a client such as Claude Desktop.

Probably not for

You need a hosted remote endpoint, OAuth, or support for accounting systems other than Lexware Office, since this runs locally over stdio with an API key.

Business size
Any stageThe project is a free MIT-licensed community server and states no revenue, order or team bounds.

Technical details

From the vendor's own pages

From the server's repository, documentation and MCP directory listings.

What an agent can do
Accounting, Payments, Customers
Transport
stdio (local)
Authentication
API keyRequires LEXWARE_OFFICE_API_KEY env var; create key at app.lexoffice.de/addons/public-api.
Package
mcp-lexware-office (npm)
Language
TypeScript
Licence
MIT
Repository last updated
19 Jul 2026

Connect Lexware Office MCP Server

Third-party data

Setup documented for

Install command
npx -y --package=github:JannikWempe/mcp-lexware-office#semver:^2 lexware-office

Command as listed on the repository README, not tested by ecommerceguide. Check the repository README (opens in a new tab) for configuration and credentials before running it.

Categories and use cases