Lexware OfficeSAFE
MCP server to interact with Lexware Office
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
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.
The server uses Code Mode: instead of one MCP tool per API endpoint, it exposes two tools — search to explore a curated Lexware API catalog and execute to run constrained, sandboxed API workflows. This keeps the tool surface small while covering the whole API, including pagination, aggregation, and multi-step reporting in a single call.
Upgrading from 1.x? The legacy tool-per-endpoint server was removed in 2.0.0. See docs/guide.md#migrating-from-1x.
Features
- 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
- Read-only by default: writes require explicit opt-in via environment variable
How it works
The server exposes two MCP tools:
search— runs a sandboxed JavaScript async arrow function against a curated OpenAPI-lite Lexware catalog.execute— runs a sandboxed JavaScript async arrow function with one host capability,lexware.request, for relative/v1/...Lexware API calls.
Example execute call:
async () => {
const response = await lexware.request({
method: 'GET',
path: '/v1/contacts',
query: { name: 'Muster', page: 0, size: 10 }
});
return response.data;
}The sandbox does not receive the Lexware AP
4fdf939a7a6cOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-lexware-office --env LEXWARE_OFFICE_API_KEY=${LEXWARE_OFFICE_API_KEY} -- npx -y [email protected]{
"mcpServers": {
"mcp-lexware-office": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"LEXWARE_OFFICE_API_KEY": "${LEXWARE_OFFICE_API_KEY}"
}
}
}
}Exposed tools (2)
1 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
execute | write | |
search | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (4)
.release-please-manifest.json
const bomBody = '' + JSON.stringify(COUNTRIES_FIXTURE);
@modelcontextprotocol/sdk, zod, @types/node, shx, typescript
- Default read-only mirrors how Cloudflare's OAuth scope template defaults to read-only; Lexware API keys have no equivalent OAuth scopes, so the MCP server provides the safety boundary.
Gates applied: no_behavioural_pass.
4fdf939a7a6cfull audit observations/trust-audit/mcp-server/jannikwempe__lexware-office.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4fdf939a7a6c | SAFE | B | 89 | first audit |
Questions
What is the Lexware Office MCP server?
MCP server to interact with Lexware Office
What tools does Lexware Office expose?
2 in total: 1 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Lexware Office safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Lexware Office need?
It reads LEXWARE_OFFICE_API_KEY from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Lexware Office run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as mcp-lexware-office at 2.0.0.
How current is this page?
The grade is for one exact copy of the source (4fdf939a7a6c), read on 2026-10-08. The repository is watched and re-audited when it changes.