lexware-php-mcp
Related Servers
Alternatives to lexware-php-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Lexware Office that enables querying and managing contacts, sales documents, vouchers, files, payments, and webhooks through a sandboxed two-tool interface (search/execute) with read-only-by-default write safety.2MIT
- AlicenseBqualityAmaintenanceMCP server for the Lexware Office API that enables management of invoices, contacts, articles, vouchers, and more through the Model Context Protocol.66189 npm6Functional Source , Version 1.1, MIT Future
- AlicenseAqualityCmaintenanceA small MCP server that wraps MoneyMoney on macOS via AppleScript, exporting account lists and transactions (bookingDate, amount, name, purpose) as plists for invoice reconciliation, complementing a companion Apple Mail server.2MIT
- AlicenseNot gradedqualityAmaintenanceConnects to the Lexware Office API to provide read and write access to accounting data such as invoices, contacts, vouchers, and articles. Enables natural language queries and management operations through an MCP client.600 PyPI2MIT
- AlicenseAqualityBmaintenanceEnables MCP-capable assistants to query and manage Lexware Office contacts, sales documents, vouchers, files, payments, webhooks, and reference data via the Lexware Office public API. Adds bank reconciliation tools for matching bank statement CSVs against Lexware vouchers or scanned receipt PDFs.4MIT
- FlicenseBqualityDmaintenanceMCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.1540 npm-
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.