Invoice Bridge MCP
Related Servers
Alternatives to Invoice Bridge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to extract invoice data from existing PDFs and create EN 16931-compliant ZUGFeRD/Factur-X e-invoices or XRechnung XML locally, without uploading documents.857 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseNot gradedqualityCmaintenanceEnables 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
- 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.1MIT

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.1010 npmMIT- AlicenseAqualityBmaintenanceCheck, convert and explain Factur-X / ZUGFeRD e-invoices from your AI assistant: validate a PDF against EN 16931 or the French 2026 rules, dry-run or convert an invoice to Factur-X, and get a plain explanation of any validation error.24MIT
TDQS
Scored across 3 tools
parse_invoice and validate_invoice_pdf both extract embedded XML from PDFs, creating overlap. Descriptions clarify that parse_invoice only extracts and saves, while validate_invoice_pdf also validates, and validate_compliance validates standalone XML, but the extraction overlap still causes potential confusion.
All tools follow a consistent snake_case verb_noun pattern (parse_invoice, validate_compliance, validate_invoice_pdf). The convention is predictable and easy to understand.
Three tools is slightly below the typical 3-15 range but each serves a distinct purpose (extraction, XML validation, PDF validation). However, some redundancy between parse_invoice and validate_invoice_pdf suggests the set could be streamlined.
The server covers extraction and validation of ZUGFeRD/Factur-X invoices, but lacks tools for generating or converting invoices, which might be expected from an 'Invoice Bridge'. This is a notable gap for a domain that often requires bridging between formats.