csv2zugferd
Related Servers
Alternatives to csv2zugferd
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, validate against the official KoSIT rules (no Java), create, and display XRechnung and ZUGFeRD e-invoices, and export incoming invoices as DATEV posting batches. Running it with a cloud language model sends invoice contents to that provider's service.MIT
- AlicenseAqualityBmaintenanceRead and check European e-invoices (Factur-X, ZUGFeRD, XRechnung, UBL, CII) from an AI assistant: contents in plain text plus an EN 16931 consistency check.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to locally parse, validate, audit, explain, generate, and convert XRechnung and ZUGFeRD/Factur-X e-invoices using official rule sets, fully offline with no API keys required.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI assistants to read and modify an Acumulus administration through natural language over the official API, including invoices, picklists, and direct endpoint calls. Runs locally over stdio and supports test mode to validate writes without persisting them.429 PyPIAGPL 3.0

rechnungsapi-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants and agents to create, validate, read and convert German and EU e-invoices in ZUGFeRD, XRechnung and Factur-X formats, including extracting structured data from scanned or PDF invoices and embedding XML into PDF/A-3 files. It can run as a hosted remote server or locally, with each request authenticated by the caller's own API token.1020 npmMIT- FlicenseBqualityBmaintenanceEnables an AI assistant to read and manage a local project-management database over stdio: listing and creating projects, tasks, expenses, chats and people, and pulling money, margin, deadline and overdue summaries. It runs on the same service layer and SQLite file as the bundled web UI, so figures shown to the assistant and to the human always agree.14-
TDQS
Scored across 5 tools
Each tool targets a distinct step of the workflow: writing a config file, inspecting a config, fetching the schema reference, reading a CSV header, and doing an in-memory trial run. The descriptions explicitly disambiguate with cross-references ('use csv2zugferd_invoice_get first', 'use csv2zugferd_config_get'). No two tools overlap in purpose.
All names use snake_case with a shared csv2zugferd_ prefix and a resource_then_action ordering (config_get, csv_header_get, invoice_get). The one deviation is csv2zugferd_config_file_create, which nests an extra noun (config_file) while config_get does not, making resource granularity slightly uneven.
Five tools map cleanly onto five distinct workflow stages (schema reference → CSV inspection → config authoring → config validation → trial run), with no filler. The surface is well scoped for a config/validation assistant around a CLI.
The surface covers the full prepare-validate-preview lifecycle including schema lookup, header inspection, config write, config lint and a dry-run mapping, which is coherent for the stated read-only purpose. The absence of any tool to actually emit production XML/PDF (delegated to the CLI) and no way to remove or list saved config files are minor gaps agents can work around.