MCP E Invoicing Core
Reuse shared European e-invoicing models, XML helpers, and OAuth2 client code when building or extending country-specific einvoicing MCP servers.
Overview
io.github.cmendezs/mcp-einvoicing-core is a Build-phase MCP library package that supplies shared European e-invoicing models, XML utils, and OAuth2 for country einvoicing servers.
What is this MCP server?
- Base package mcp-einvoicing-core v1.3.0 on PyPI
- Shared European e-invoicing data models for downstream servers
- XML utilities for UBL-oriented document handling
- OAuth2 client for secured e-invoicing APIs
- Stdio MCP transport identifier for monorepo-style server builds
- Version 1.3.0
- PyPI identifier mcp-einvoicing-core
- Includes shared models, XML utils, OAuth2 client
What problem does it solve?
Duplicating UBL models, XML validators, and OAuth glue across every EU country MCP server wastes time and drifts out of sync with standards updates.
Who is it for?
Developers extending mcp-einvoicing-be/de or building another EU MCP server who need shared einvoicing primitives.
Skip if: Operators who only want to send invoices today without maintaining Python MCP server code.
What do I get? / Deliverables
New or customized einvoicing MCP servers import one core package so models and auth behavior stay consistent across Belgium, Germany, and future locales.
- Reusable models and XML helpers inside custom MCP servers
- OAuth2 client integration for secured einvoicing endpoints
- Consistent foundation across cmendezs EU server variants
Recommended MCP Servers
Journey fit
Library and shared protocol code belongs in Build when you integrate compliance features into your product or fork country MCP servers. Integrations is the shelf because the package is plumbing for MCP einvoicing servers, not end-user invoice sending on its own.
How it compares
Shared library for einvoicing MCP authors, not a standalone consumer invoicing product.
Common Questions / FAQ
Who is io.github.cmendezs/mcp-einvoicing-core for?
Integrators and maintainers of European e-invoicing MCP servers who need common models, XML tooling, and OAuth2 in one dependency.
When should I use io.github.cmendezs/mcp-einvoicing-core?
Use it during Build integrations when creating or upgrading country-specific einvoicing MCP servers that depend on the cmendezs stack.
How do I add io.github.cmendezs/mcp-einvoicing-core to my agent?
Add mcp-einvoicing-core 1.3.0 as a Python dependency of your custom MCP server, wire stdio in your server entrypoint, and expose tools via your country package—not as a solo merchant shortcut.