Invoice Bridge MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVOICE_INPUT_DIR | No | Absoluter oder relativer Pfad zum Eingangsverzeichnis für Rechnungen. | <Projekt-Root>/input |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_invoiceB | Extrahiert die eingebetteten XML-Daten aus einer PDF/A-3-Datei und speichert sie im Eingangsordner. |
| validate_complianceC | Prüft eine ZUGFeRD/Factur-X-XML-Datei auf formale und rechnerische Konformität nach § 14 UStG und EN 16931. |
| validate_invoice_pdfB | Direkte Prüfung einer PDF-Rechnung in einem Schritt: Extrahiert eingebettete ZUGFeRD/Factur-X XML-Daten und validiert die Konformität nach § 14 UStG. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_invoices | Listet alle verfügbaren E-Rechnungen im Eingangsordner auf. |
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.