Mcp Facturacion Electronica Es
Wire Spanish AEAT e-invoicing (VERI*FACTU, SII, Facturae, FACe, Crea y Crece B2B) into your agent or billing stack from Claude Code or Cursor.
Overview
mcp-facturacion-electronica-es is a MCP server for the Build phase that automates Spanish AEAT e-invoicing workflows including VERI*FACTU, SII, Facturae/FACe, and Crea y Crece B2B from your AI coding agent.
What is this MCP server?
- Covers VERI*FACTU, SII, Facturae/FACe, and Crea y Crece B2B Spanish e-invoicing regimes
- AEAT sandbox or production via AEAT_ENV with optional FNMT-RCM PKCS#12 MTLS for authority submission
- FACe public-sector invoicing with separate FACE_ENV sandbox or production targeting
- Default submitter identity configurable with AEAT_NIF for recurring AEAT operations
- PyPI package mcp-facturacion-electronica-es v0.2.0 over stdio MCP transport
- Server version 0.2.0 on PyPI identifier mcp-facturacion-electronica-es
- Supports AEAT_ENV and FACE_ENV each as sandbox or production
- Optional AEAT_CERTIFICATE_PATH for PKCS#12 MTLS to AEAT
What problem does it solve?
Spanish tax and e-invoice rules span multiple APIs and certificate-heavy submissions, which is painful to implement correctly as a one-person team without constant doc-diving.
Who is it for?
Indie SaaS or agency builders selling in Spain who want agent-driven Facturae, VERI*FACTU, or FACe integration during product development.
Skip if: Teams with no Spanish customers, or finance staff who only need a hosted invoicing UI with no developer MCP setup.
What do I get? / Deliverables
After you register the server, your agent can validate and prepare compliant Spanish invoice actions against sandbox or production AEAT and FACe environments with consistent tooling.
- Agent-callable Spanish e-invoice validation and submission flows toward AEAT and FACe
- Environment-separated sandbox vs production configuration for safer pre-release testing
- Unified MCP surface for multiple Spanish invoicing regimes in one billing integration
Recommended MCP Servers
Journey fit
E-invoicing MCP servers are developer integrations you add while building products or internal tools that must talk to Spain’s tax and public-procurement systems. Canonical shelf is integrations: stdio MCP tools that generate, validate, and submit invoice payloads instead of hand-maintaining AEAT XML and certificate flows.
How it compares
Country-specific AEAT MCP integration, not a generic Stripe-style payments skill or a broad accounting marketplace.
Common Questions / FAQ
Who is mcp-facturacion-electronica-es for?
It is for developers and solo builders using Claude Code, Cursor, or Codex who need programmatic Spanish e-invoicing aligned with AEAT (VERI*FACTU, SII, Facturae, FACe, Crea y Crece B2B).
When should I use mcp-facturacion-electronica-es?
Use it while building or extending billing, ERP exports, or B2G invoicing features that must target Spanish sandbox or production tax endpoints.
How do I add mcp-facturacion-electronica-es to my agent?
Install the PyPI package mcp-facturacion-electronica-es, configure stdio MCP in your client, and set AEAT_ENV plus AEAT_NIF; add AEAT_CERTIFICATE_PATH and password when submitting to AEAT with MTLS.