Lexware Office (lexoffice) MCP Server

Presupuestos, facturas, contactos y recibos en Lexware Office.

Servidor MCP alojado

npx add-mcp 'https://cotlet.dev/mcp/v1/lexware-office'

Se instala en Claude Code, Codex, Cursor y más

Documentación

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Lexware Office (lexoffice) API and MCP server: Let your AI agent write and chase your Lexware invoices.

Lexware Office has a Public API on version XL and no MCP server of its own (checked 27 Oct 2026). The API creates contacts, quotes, invoices and draft reminders and uploads receipts; it cannot email a document, record a payment or cancel an invoice. Cotlet runs 14 tools hosted on any version from S, over MCP for agents and REST for scripts.

Quotes, invoices, contacts and receipts in Lexware Office. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Lexware or Haufe
Page: https://cotlet.dev/integrations/lexware-office-api-mcp-server

What can you automate in Lexware Office (lexoffice)?

Invoice a billing list
Email finalised invoices and quotes
Send Mahnungen for overdue invoices
Record customer payments
Upload supplier receipts
Draft quotes from a brief

Does Lexware Office have an MCP server or an API?

Only XL (32.90 EUR a month net) lists the API. S, M and L at 7.90, 12.90 and 21.90 EUR have none; the step from M to XL is 20 EUR a month.
An invoice is finalised only when the API creates it. A draft cannot be finalised later, payments are read only, and a reminder (Mahnung) stays a draft with a PDF.
Zapier has one action, Upload Document for Bookkeeping Purposes. Make has an app with about 17 modules on the XL key. There is no n8n node.

What you need	Public API (XL)	Make	Cotlet
Works on S, M and L	XL only	XL key	Yes, any version
Create contacts, quotes and invoices	Yes	Contacts, invoices	Yes
Email an invoice or quote	No endpoint	No	Yes, after your OK
Send a payment reminder	Draft only	No	Yes, after your OK
Record a payment, cancel an invoice	Read only	No	Yes, after your OK
Allowed by Lexware	Yes, official	Yes, on the API	Uses the web app

Checked 27 Oct 2026. Sources: Lexware Office Public API, Lexware Office API documentation, Lexware Office Public API license and terms of use, Lexware Office prices and versions, Zapier: Lexware Office integrations

How does Cotlet connect to Lexware Office (lexoffice)?

Sign in to Lexware Office (lexoffice). Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never keep your Lexware password, and nothing is finalised, sent, reminded or cancelled until you approve it.

Connect Lexware Office (lexoffice) to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Enable Lexware Office for agents. Open a Cotlet account, sign in to Lexware Office in its Cloud Browser with your own user, then press Enable for agents.
Add the Cotlet address. Put https://cotlet.dev/mcp/v1 into your agent as a remote MCP server or custom connector.
Approve the connection. Chat apps show a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.

https://cotlet.dev/mcp/v1 carries Lexware Office next to your other apps. With two-step sign-in on, you confirm the Lexware App push or code yourself, and Lexware can remember the browser for 90 days. Refresh the connector after enabling Lexware Office so its tools load.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-lexware-office \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-lexware-office": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-lexware-office]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: lexware_office_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: lexware_office_write

How to use the Lexware Office (lexoffice) REST API

Create your Cotlet API key

Create a Cotlet API key with access to Lexware Office (lexoffice) and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Connect Lexware Office (lexoffice) in Cotlet and enable it for agents. Account access: Your own Lexware Office user. Invoices, quotes and reminders need version M or higher, receipts version S or higher. The restricted role "Belege, Kontakte & Produkte" cannot cancel paid invoices or delete payments.

Make your first Lexware Office (lexoffice) API request

REST:

curl https://cotlet.dev/api/v1/lexware-office/documents \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read documents and apply the operation limits

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "lexware-office",
  "tool": "list_documents",
  "result": {
    "documents": [
      {
        "document_id": "d_9c31be",
        "type": "invoice",
        "number": "RE1031",
        "contact": "Nordlicht Design GmbH",
        "date": "2026-09-02",
        "due_date": "2026-09-16",
        "total_gross": 1130.5,
        "currency": "EUR",
        "status": "overdue"
      },
      {
        "document_id": "d_7a02f4",
        "type": "invoice",
        "number": "RE1034",
        "contact": "Becker Consulting",
        "date": "2026-09-05",
        "due_date": "2026-09-19",
        "total_gross": 2380,
        "currency": "EUR",
        "status": "overdue"
      }
    ],
    "next_cursor": null
  }
}

Lists sales documents from the Belege list, newest first, with number, customer, date, gross total and status. Filter by type and status; overdue returns open invoices past their due date.

Use the IDs with get_document, finalize_document or send_document.

limit: 1 to 100. Default: 50.

cursor: Next page cursor from the previous call.

Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.

Lexware Office (lexoffice) workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	One document with its lines, totals, status and reminders already sent. Use `get_document` in your configured operations sheet.
Make	HTTP > Make a request	Customers and suppliers saved in Lexware Office, searchable by name or email. Use `list_contacts` in your configured operations sheet.
Python or Node.js	REST API	Receipts in Lexware Office with the fields the automatic recognition filled in. Use `list_receipts` in your configured operations sheet.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Lexware Office (lexoffice); your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Lexware Office (lexoffice) API endpoints and MCP tools

Invoices and quotes

Drafts have no number and run at once. Finalising gives the number from your number range and locks the document, so it asks first, like sending and cancelling.

List documents (list_documents, read): Invoices, quotes, order confirmations and delivery notes, filtered by type and status.
Get document (get_document, read): One document with its lines, totals, status and reminders already sent.
Create invoice (create_invoice, write): Save a draft invoice for a contact. Nothing is sent and no number is assigned yet.
Create quote (create_quotation, write): Save a draft quote for a contact. Nothing is sent.
Finalise document (finalize_document, write, asks first): Finalise a draft invoice or quote: it gets its number and can no longer be edited.
Send document (send_document, write, asks first): Email a finalised invoice or quote to the customer with its PDF attached.
Download document PDF (download_document_pdf, read): The PDF of a finalised invoice or quote.
Cancel invoice (cancel_invoice, write, asks first): Cancel (stornieren) a finalised invoice. The number stays blocked.

Payments and reminders

Mahnen works only on invoices written in Lexware Office, not imported ones. Payments go in as private or cash.

Record payment (record_payment, write, asks first): Record a customer payment on an open invoice.
Send payment reminder (send_payment_reminder, write, asks first): Send a Mahnung or Zahlungserinnerung for an overdue invoice, with an optional fee.

Contacts

Saved customers and suppliers. One-off names kept only on a document (Einmalkontakte) are not listed.

List contacts (list_contacts, read): Customers and suppliers saved in Lexware Office, searchable by name or email.
Create contact (create_contact, write): Save a new customer or supplier in Lexware Office.

Receipts

Uploads land in Zu prüfen with what the recognition read. Booking (Beleg erfassen) stays with you or your tax adviser.

Upload receipt (upload_receipt, write): Upload a supplier invoice or receipt file for bookkeeping. It lands in "Zu prüfen".
List receipts (list_receipts, read): Receipts in Lexware Office with the fields the automatic recognition filled in.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/lexware-office-api-mcp-server#tools

Who can see my Lexware Office session, and how do I revoke it?

What we store. Your signed-in Lexware Office browser profile, AES-256-GCM encrypted, in Finland. Never the password.
What your agent gets. The 14 Lexware Office tools, not the cookie or an API key.
What the session sees. What your Lexware user sees: documents, contacts, receipts, open amounts.
What no tool touches. Banking, transfers, payroll, tax returns, bookings and user rights.
If Lexware asks to verify. You confirm the push or type the code yourself. We never do.
How to cut access. Disable for agents, reset the browser, or sign the session out in Lexware.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.

Is it against Lexware Office's terms? Account safety

die Nutzung von Schnittstellen, die nicht über die Public API oder Partner API angeboten werden und undokumentiert sind, ist untersagt

Lexware Office terms for SaaS, 2.2 (d), Stand 11 Aug 2026

In English: using interfaces that are undocumented and not offered through the Public or Partner API is prohibited. Clause 2.2 (e) lets Lexware restrict use or terminate for good cause, and the general terms allow blocking access on misuse and termination when access data is handed to third parties. A tool working in the web app could be read as such an interface, and on XL the Public API is the allowed route for what it covers. We found no public case of a Lexware Office account blocked for automation (checked 27 Oct 2026); the block reasons Lexware lists are for its business bank account.

How we keep your account looking like you:

Your own Lexware user, signed in by you, so no access data changes hands
One Cloud Browser with a fixed IP and cookies, not a new device per call
Finalising, sending, reminders, payments and cancelling wait for your OK
No tool books receipts, deletes documents or touches banking
If Lexware objects, we pause the Lexware Office tools for everyone within 24 h

Lexware's Fair Usage Policy caps outgoing documents at 20 a minute and asks you to stop bulk work on error codes. Spread a big invoice run over the day.

What happens when Lexware Office changes?

12 h between tests of the Lexware Office reads and drafts
24 h between tests of sends and reminders a customer gets
$0 for a call to a Lexware Office tool paused for repair

Lexware Office keeps adding to its documents, such as e-invoice formats since 2025, and screens move with it. When one does, we fix the tool and the names, inputs and answers your agent uses stay as they were. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Matches the contact. list_contacts by customer number or exact name for each line.
Saves a draft. create_invoice returns net, VAT and gross to compare with your list.
Waits for your OK. Finalising and the email each show up in your Cotlet console first.
Reports the run. Invoice numbers, the total sent, and drafts left with both amounts.

Action	Undo
Create a draft invoice or quote	Delete the draft in Lexware Office
Finalise an invoice	Only by Stornieren; the number stays blocked
Send an invoice or reminder	No, the customer has the email
Record a payment	Delete it with the trash icon in the invoice
Upload a receipt	Delete it from Zu prüfen

5 of 14 tools ask first: finalize_document, send_document, send_payment_reminder, record_payment and cancel_invoice, the ones a customer or your books feel. Reads, drafts, new contacts and uploads run at once. Switch the wait off per tool for a scheduled run.

A finalised invoice is legally binding and cannot be edited. The run compares totals while the invoice is still a draft, so a wrong amount never gets a number.

MCP call:

{
  "name": "finalize_document",
  "arguments": {
    "document_id": "d_c44e19"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/lexware-office/documents/d_c44e19/finalize \
  -H "Authorization: Bearer $COTLET_API_KEY"

Response:

{
  "document_id": "d_c44e19",
  "type": "invoice",
  "number": "RE1043",
  "status": "open",
  "total_gross": 1130.5,
  "currency": "EUR"
}

Scripts and month-end jobs reach the same tools over REST at /api/v1/lexware-office, with the same key and price. A call that fails, such as finalising a document that is already final, costs nothing. The tools table lists the REST path of each tool.

How much does the Lexware Office MCP server cost?

About $20 a month for a small business with about 20 invoices and 40 receipts a month, 3,460 credits. Lexware still bills your version as before.

Job	Calls	Credits
Create, finalise and send an invoice	4 × 20	800
Overdue invoices and reminders, weekly	5 × 4	200
Upload a supplier receipt	1 × 40	400
Check receipts in Zu prüfen, weekly	1 × 4	40
Record a customer payment	2 × 20	400
Quote from a client brief	3 × 4	120
Cloud Browser, 30 days		1,500
Total		3,460

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
No XL upgrade, any version that has the screen

Reported sizes run from 8 to 12 invoices a month for a freelancer to about 30 invoices and 50 receipts for a craft business; the payment and quote mix is our example. Moving from M to XL for the API alone costs 20 EUR a month and still sends nothing. Dollars at the $29 pack rate.

Lexware Office MCP server: GitHub, hosted connectors or Cotlet

Option	What it does	Where it stops
JannikWempe/mcp-lexware-office	The most starred server (71 stars, MIT, last commit 15 Oct 2026). Two tools, search and execute, run small scripts against the whole Public API.	Needs an XL key, runs on your computer, writes off until you set a flag. The API still cannot send or record payments.
marselsel/Lexware-MCP-Server	62 tools, self-hosted over HTTP with OAuth for chat apps (42 stars, MIT, last commit 1 Oct 2026).	XL key; you host it. Finalising is off by default and happens only at creation.
oemedia connector	Hosted MCP for Claude and ChatGPT: open invoices, quotes, quote to invoice, paid status, PDFs.	XL key; creates drafts you finalise yourself; no price on the page.
Make	Official app with about 17 modules, Watch Invoices and Watch Events triggers.	XL key; scenarios, not an agent; no send or reminder module found.

If you are on XL and your agent only reads and drafts, a free GitHub server on the official API does it, and you run it. Emailing documents, sending Mahnungen, recording payments and Stornieren are in no API, and S, M and L have no API at all: that is where Cotlet fits.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Lexware Office tools go to contact@cotlet.dev.

Lexware Office (lexoffice) API and MCP: questions

How do I get access?

Sign up free at https://cotlet.dev, open Lexware Office under Integrations in the console and sign in to Lexware Office in its Cloud Browser. The trial starts when you sign up, and no card is asked.

How do I connect Lexware Office (lexoffice) to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Lexware Office (lexoffice) once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Lexware Office (lexoffice) account through Cotlet, in their phone apps too.

What can ChatGPT do in Lexware Office (lexoffice)?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Lexware Office (lexoffice): create and send invoices from a billing list; chase overdue invoices with payment reminders; upload receipts for bookkeeping. You ask in plain words, and anything that reaches other people waits for your OK first.

Do I need Lexware Office version XL to use Cotlet?

No. The public API needs version XL (checked 14 Oct 2026), but Cotlet works the screens you use yourself. Invoices, quotes and reminders need version M or higher, and receipt capture is part of version S.

Can my agent undo a finalised invoice?

Only the way you would: cancel_invoice clicks Stornieren, and the corrected invoice is a new document. A cancellation cannot be undone and the cancelled number stays blocked, which Lexware says GoBD requires.

Does Lexware Office have webhooks?

Yes, on XL: the Public API has event subscriptions for changes such as new invoices or contacts. Cotlet does not use them. On other versions, run your agent on a schedule, for example a list_documents pass each Monday for overdue invoices.

Can I use the Public API and Cotlet together?

Yes. On XL, keep the API or Make for syncing contacts and drafts, and connect Cotlet to the same agent for sending, reminders, payments and cancelling.

Does it work during the Lexware Office trial?

Yes. The 30-day Lexware trial has every XL feature, and Cotlet works in that account like in a paid one. After the trial, the tools you can use follow your version: invoices and reminders need M or higher.

Is the MCP server different from the REST API?

Only in how you reach it. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Lexware?

No. Cotlet is independent and not affiliated with Lexware, Haufe-Lexware or the Haufe Group.

Can I use the Lexware Office (lexoffice) API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.