Skip to main content
Glama
Rechnungsapi

rechnungsapi-mcp

Official
by Rechnungsapi

Related Servers

Alternatives to rechnungsapi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create and manage e-invoices through natural language, supporting EU compliance formats like ZUGFeRD and XRechnung, as well as US plain PDF invoices.
      7
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      InvoiceXML brings e-invoice compliance to your AI agent. Create, validate, convert, render, and extract structured invoices across UBL (Peppol BIS Billing 3.0, used worldwide), CII, Factur-X, ZUGFeRD, and XRechnung, all checked against the EN 16931 standard and official Schematron rules. Ask your assistant to generate a compliant invoice, validate one for errors, or convert between formats, with n
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to parse and analyze PDF invoices, including text, field, and table extraction, OCR for scanned documents, ZUGFeRD support, compliance validation, and batch processing via MCP.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for German e-invoice compliance (XRechnung 3.0 & ZUGFeRD 2.x) enabling AI agents to validate, generate, parse, and check compliance of electronic invoices per EN 16931.
      6
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but create_zugferd_from_pdf overlaps with the analyze_pdf_invoice + create_zugferd_invoice two-step workflow, and create_zugferd_invoice vs create_zugferd_pdf differ only by input type (JSON vs XML), which could cause minor misselection.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun pattern (analyze_pdf_invoice, create_xrechnung, validate_zugferd_pdf, etc.), including the async variants which follow a predictable prefix-based convention.

    Tool Count5/5

    10 tools is well-scoped for an e-invoicing API covering analysis, creation, validation, extraction, and async operations; each tool earns its place without redundancy.

    Completeness5/5

    The surface covers the full lifecycle: analyze PDF/image to JSON, create XRechnung XML, create ZUGFeRD PDF from JSON or XML, convert PDF to ZUGFeRD, extract XRechnung from ZUGFeRD, and validate both XRechnung XML and ZUGFeRD PDF, with async support for large files.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues