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 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
      25 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
      56 npm
      -

    • informer-mcp

      vladxyz
      A
      license
      B
      quality
      B
      maintenance
      MCP server for the Informer bookkeeping API, providing direct access to relations, invoices, quotations, orders, receipts, products, and financial reports.
      71
      MIT
    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.1/5.0

    Scored across 66 tools

    Disambiguation4/5

    Most tools target a unique resource-action pair, and the repetitive structure (get/download/deeplink/pursue) is clear per document type. The main confusion risk is between list_vouchers and list_voucherlist, and between generic file upload/download and voucher/file-specific variants, though descriptions do clarify these.

    Naming Consistency4/5

    All tools follow a consistent lexware_verb_noun pattern with snake_case throughout. Minor deviations like list_voucherlist (noun already contains 'list') and get_payments (rather than list_payments) keep this from being a perfect 5.

    Tool Count2/5

    With 66 tools, the surface is very large and will likely overwhelm an agent choosing among options. The breadth reflects a full ERP domain, but it far exceeds the 3-15 well-scoped range and feels heavier than necessary.

    Completeness4/5

    The server covers core lifecycles well: articles and contacts have CRUD, sales documents have create/get/download/pursue/deeplink, and vouchers have create/get/update/upload/list. Minor gaps exist—such as no create operation for down payment invoices and no update/delete for most document types—but these may reflect API constraints rather than missing coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources