Skip to main content
Glama
bdiaby1

Lexware Office MCP Server

by bdiaby1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Lexware Office MCP Server

No user-submitted related servers found.

    Related Servers

    • lexware-mcp-server

      lazyants
      A
      license
      B
      quality
      A
      maintenance
      MCP server for the Lexware Office API that enables management of invoices, contacts, articles, vouchers, and more through the Model Context Protocol.
      66
      114 npm
      8
      Functional Source , Version 1.1, MIT Future

    • Lexware Office MCP Server

      bdiaby1
      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

    • 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

    • 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
      -

    • bexio-mcp

      valmiremini
      A
      license
      A
      quality
      D
      maintenance
      A standalone MCP server for the bexio REST API, enabling interaction with bexio resources like contacts, invoices, and projects through natural language from any MCP client.
      21
      9 npm
      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

    A4.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: search is for discovering API endpoints and workflows, while execute is for making actual API requests. The descriptions explicitly state to use search before execute, eliminating ambiguity.

    Naming Consistency5/5

    Both tool names are single lowercase verbs ('search' and 'execute'), following a consistent imperative style. There is no mixing of conventions or confusing patterns.

    Tool Count3/5

    With only 2 tools, the server is at the low end of what might be considered adequate. However, the design intentionally uses a minimal pair of discovery and execution, which is reasonable for the broad API access it provides.

    Completeness5/5

    The search tool exposes the full API catalog, including workflows and domain guides, while execute can perform any documented API operation. Together they cover the complete lifecycle of discovering and interacting with the Lexware Office API, leaving no functional gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources