Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lexware-mcp-server

No user-submitted related servers found.

    Related Servers

    • Lexware Office MCP Server

      bdiaby1
      A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      2
      MIT

    • lexware-php-mcp

      Stefan39
      A
      license
      A
      quality
      B
      maintenance
      Unofficial read-only MCP server for Lexware Office (lexoffice), written in PHP. Lists open and overdue invoices with totals per currency; bank details are stripped before data reaches the model.
      1
      MIT

    • Lexware Office MCP Server

      bdiaby1
      A
      license
      A
      quality
      B
      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

    • easybill-mcp

      stack74
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing access to the easybill REST API for managing invoices, customers, articles, payments, projects, and time tracking, with read-only mode by default.
      28
      10 npm
      MIT

    • buchpilot-mcp

      makririch
      F
      license
      B
      quality
      D
      maintenance
      MCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.
      15
      28 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 66 tools

    Disambiguation3/5

    Most tools target distinct resources, but several pairs overlap: create_invoice vs pursue_invoice (create-from-preceding-voucher), the generic download_file/upload_file vs per-type download_invoice_file/download_credit_note_file/upload_voucher_file, and the similarly-named list_vouchers (lookup) vs list_voucherlist (collection). Descriptions do a good job disambiguating them, but the boundaries are not obvious from names alone.

    Naming Consistency4/5

    Nearly everything follows a predictable lexware_verb_noun snake_case pattern (create_/get_/list_/update_/download_/deeplink_). Minor deviations: the odd verb 'pursue' for create-from-preceding, and the inconsistent list_vouchers vs list_voucherlist naming.

    Tool Count2/5

    66 tools is very heavy and well past the point where an agent can easily scan the surface. The broad ERP domain (articles, contacts, vouchers, sales documents, files, webhooks) justifies many tools, but the count is inflated by per-type download/deeplink/pursue variants that could be consolidated.

    Completeness4/5

    Core workflows are covered: articles and contacts have CRUD, vouchers have create/get/update/list plus file upload and payments, webhooks have full lifecycle including signature verification. Gaps remain (no delete for contacts or most sales documents, no update for invoices/quotations), though many reflect Lexware API limits.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources