lexware-php-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 | |
| LEXWARE_API_BASE_URL | No | The base URL for the Lexware API | https://api.lexware.io |
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 | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_itemsA | Lists unpaid sales invoices (open and overdue receivables) from Lexware Office, oldest due date first, with totals per currency. Amounts are gross; net amounts need the voucher detail. |
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 1 tool
There is only one tool, so there is nothing for an agent to confuse it with. Its purpose (listing unpaid sales invoices) is stated clearly and narrowly.
The single tool uses readable snake_case with a clear noun-phrase style. There is no set of names to check for pattern consistency, so it cannot reach a perfect 5.
One tool is far too thin for a Lexware Office integration, which would typically require invoices, vouchers, contacts, and payment operations. It reads like a partial slice of a much larger surface.
Only open receivables are exposed; there is no listing/detail for vouchers, contacts, invoices, or payables despite the description pointing to voucher detail for net amounts. Agents hitting those needs have no path forward.