office-books-mcp
Related Servers
Alternatives to office-books-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and draft accounting documents such as invoices, vouchers, contacts, and articles via the Lexware Office API, including PDF rendering and receipt uploads. Supports OAuth and static token authentication for secure access.MIT
- AlicenseAqualityAmaintenanceConnects 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.26329 PyPI4MIT
- AlicenseAqualityBmaintenanceConnects an AI assistant to a BuchhaltungsButler tenant through 59 German-language tools — 54 endpoint tools (one per API v1 endpoint) plus 5 bundle tools — covering documents, payments, invoices, postings, master data, cost centers, and reports, of which 19 are read-only. Runs locally, so credentials go only to BuchhaltungsButler itself, and lets users control in their client which tools the assistant may call.5916 npm1MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to query and manage self-hosted accounting data—invoices, balances, and books—through natural language, with read-only tools by default and optional scoped write operations.3027 PyPI1AGPL 3.0
- AlicenseAqualityDmaintenanceEnables 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
- FlicenseNot gradedqualityBmaintenanceConnects AI assistants to the official DATEV APIs so users can query bookkeeping, payroll, and documents in plain language; any write is previewed and requires a matching one-time confirmation before it is executed.-
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.