office-books-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LEXWARE_API_KEY | Yes | Your Lexware Office Public API key, created in Lexware Office (XL plan). The key can be supplied via the MCP client config env or in .env/.env.local. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Read the connected Lexware Office company profile: company name, tax type, small business status and connected user. |
| list_contactsB | List customers and vendors. Filter by name (min 3 chars), email, customer or vendor number, or role. |
| get_contactA | Read one contact with addresses, email addresses and phone numbers. |
| list_articlesC | List products and services from the article catalogue. |
| get_articleB | Read one article with its price. |
| list_vouchersA | Search all vouchers (sales and purchase invoices, credit notes, quotations and more) by type, status and dates. Returns metadata. Use get_sales_document or get_voucher for full details. |
| get_voucherB | Read a bookkeeping voucher (salesinvoice, salescreditnote, purchaseinvoice, purchasecreditnote) with its items and booking categories. |
| get_sales_documentC | Read an invoice, credit note, quotation, order confirmation, delivery note, down payment invoice or dunning by id. |
| get_paymentsB | Read the payment status and payment items of a voucher or sales document. |
| list_recurring_templatesC | List templates for recurring invoices. |
| get_reference_dataB | Read reference lists needed to fill documents correctly: countries with tax classification, payment conditions, posting categories, print layouts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target a distinct resource (profile, contacts, articles, payments, reference data), and descriptions clarify the list/detail split. However list_vouchers vs get_voucher vs get_sales_document overlap conceptually around invoices, requiring careful reading to pick the right entry point.
Every tool follows a consistent verb_noun pattern using only get_ and list_ prefixes (get_profile, list_contacts, get_contact, list_articles, etc.). The convention is predictable and readable throughout.
11 tools is well within the ideal 3-15 range and each tool maps to a distinct resource or query type in the Lexware Office domain. Nothing feels redundant or padded.
The surface is entirely read-only: contacts, articles, vouchers, and recurring templates can be listed and read but never created, updated, or deleted, leaving common accounting workflows as dead ends. Listing recurring templates without a get_recurring_template also hints at an incomplete lifecycle.