Mcp Einvoicing Be
Generate and validate Belgian-compliant e-invoices (Peppol, UBL, PINT-BE) and interact with Mercurius from your agent.
Overview
io.github.cmendezs/mcp-einvoicing-be is an Operate-phase MCP server that helps agents produce and work with Belgian e-invoices across Peppol BIS 3.0, UBL 2.1, PINT-BE, and Mercurius.
What is this MCP server?
- Belgian stacks: Peppol BIS 3.0, UBL 2.1, PINT-BE (NBB), Mercurius
- Optional BCE_API_KEY for enriched KBO/BCE enterprise lookups
- PEPPOL_ENV switches production vs test Peppol network
- PyPI package mcp-einvoicing-be v0.2.0 over stdio MCP
- LOG_LEVEL env for DEBUG through ERROR
- Version 0.2.0
- Formats: Peppol BIS 3.0, UBL 2.1, PINT-BE (NBB), Mercurius
- Env vars: BCE_API_KEY (optional secret), PEPPOL_ENV, LOG_LEVEL
What problem does it solve?
Belgian Peppol and Mercurius rules are easy to get wrong in custom billing code, and solo builders lack time to memorize every XML profile and test-network nuance.
Who is it for?
EU solo founders or micro-SaaS sellers invoicing Belgian B2B buyers who already use MCP and want agent-assisted UBL/Peppol workflows.
Skip if: US-only businesses, merchants who only need Stripe PDF receipts, or teams needing a certified accountant portal replacement.
What do I get? / Deliverables
Your agent can invoke Belgian e-invoicing tools with the right Peppol environment and formats so invoices move toward network-ready XML instead of one-off spreadsheets.
- Agent-driven Belgian e-invoice XML and Peppol-oriented workflows
- Test vs production Peppol network separation via configuration
- Enterprise identifier lookups when BCE_API_KEY is configured
Recommended MCP Servers
Journey fit
EU e-invoicing obligations are ongoing compliance and billing operations once you sell to Belgian entities, not a one-time build spike. Iterate fits recurring invoice fixes, format updates, and Peppol environment toggles as rules and customers change.
How it compares
Country-specific e-invoicing MCP integration, not a general ledger or Stripe payment skill.
Common Questions / FAQ
Who is io.github.cmendezs/mcp-einvoicing-be for?
Builders and operators who must issue or validate Belgian e-invoices and want Peppol, UBL, and Mercurius-aware tools inside their coding agent.
When should I use io.github.cmendezs/mcp-einvoicing-be?
Use it when implementing or fixing Belgian billing pipelines, testing against Peppol test network, or validating UBL/PINT-BE outputs during Operate-phase compliance work.
How do I add io.github.cmendezs/mcp-einvoicing-be to my agent?
Install mcp-einvoicing-be from PyPI (0.2.0), set PEPPOL_ENV and optional BCE_API_KEY, register the stdio server in MCP config, and follow github.com/cmendezs/mcp-einvoicing-be setup.