MCP.so
ログイン

Lexware Office MCP Server

@JannikWempe

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

JannikWempe

Lexware Office MCP Server について

MCP server to interact with Lexware Office

Lexware Office MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-lexware-office": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "LEXWARE_OFFICE_API_KEY",
        "mcp-lexware-office"
      ],
      "env": {
        "LEXWARE_OFFICE_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Lexware Office MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Lexware Office MCP Server?

An MCP server for Lexware Office (formerly Lexoffice) that enables MCP-capable assistants to query and manage contacts, sales documents, vouchers, files, payments, webhooks, and reference data through the Lexware Office public API. It offers two entrypoints: a stable v1 with many endpoint-shaped tools and a preview v2 with two Code Mode tools (search and execute).

How to use Lexware Office MCP Server?

Requires Node.js 22+ and the LEXWARE_OFFICE_API_KEY environment variable. Configure your MCP client (e.g., Claude Desktop) to start one of the two entrypoints via npx, Docker, or local TypeScript source. For v2, write safety is read-only by default unless LEXWARE_OFFICE_ALLOW_WRITES=true is set.

Key features of Lexware Office MCP Server

  • Broad Lexware Office API coverage for read and write workflows.
  • Sales documents: invoices, quotations, credit notes, delivery notes, and more.
  • Contact management: create, read, and update customers and vendors.
  • Bookkeeping: vouchers, posting categories, payments, and file uploads.
  • Webhooks: create, list, inspect, and delete event subscriptions.
  • v2 Code Mode with sandboxed JavaScript execution for complex workflows.

Use cases of Lexware Office MCP Server

  • Automate invoice creation and finalization from an AI assistant.
  • Manage customer and vendor contacts programmatically.
  • Upload and attach vouchers and files to bookkeeping records.
  • Query and update reference data like countries and payment conditions.
  • Set up and manage webhook subscriptions for event-driven integrations.

よくある質問

1

What is the difference between v1 and v2 entrypoints?

v1 is the stable legacy server with many endpoint-shaped tools (e.g., `get-contacts`, `create-invoice`). v2 is a preview with two Code Mode tools—`search` and `execute`—that run sandboxed JavaScript against a curated API catalog. v2 is intended to replace v1 in the future.

2

What are the runtime requirements?

Node.js 22 or higher and a `LEXWARE_OFFICE_API_KEY` environment variable. The server can be run via `npx`, Docker, or from TypeScript source with `tsx`.

3

How does write safety work in v2?

v2 is read-only by default. POST, PUT, PATCH, and DELETE requests are blocked. Set `LEXWARE_OFFICE_ALLOW_WRITES=true` to enable writes, but `LEXWARE_OFFICE_READ_ONLY=true` remains a hard block that overrides any write permission.

4

How do I upload binary files in v2?

In v2, binary-safe uploads are supported via `bodyBase64` (raw binary body) or `multipart` with `contentBase64` (binary FormData parts). The host decodes base64 and builds the binary body outside the sandbox.

5

What should I do if `npx` fails with a `--before` error?

The error can occur if your npm user config has `minimum-release-age`. Fix by bypassing user config: `NPM_CONFIG_USERCONFIG=/dev/null npx ...` or permanently remove the setting with `npm config delete minimum-release-age --location=user`.

コメント

「その他」の他のコンテンツ