Skip to main content
Glama
office-books-mcp

office-books-mcp

by mjmirza

Related Servers

Alternatives to office-books-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Connects 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.
      59
      16 npm
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables 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.
      30
      27 PyPI
      1
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Connects 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

    B3.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues