Verifactu Mcp
Wire Spanish VeriFactu (AEAT) electronic invoicing into Claude Code so your agent can issue compliant e-invoices from the IDE.
Overview
verifactu-mcp is an MCP server for the Build phase that connects Claude Code to Spanish VeriFactu (AEAT) electronic invoicing.
What is this MCP server?
- MCP server for VeriFactu and AEAT Spanish electronic invoicing
- Designed for use from Claude Code per package description
- Stdio transport via PyPI package verifactu-mcp v0.1.1
- Open-source repo on GitHub for self-hosted stdio wiring
- Package version 0.1.1 on PyPI identifier verifactu-mcp
- Transport: stdio
- Repository: github.com/KmOnBeIbI31/verifactu-mcp
What problem does it solve?
You must comply with AEAT VeriFactu e-invoicing but do not want a separate manual portal workflow every time your agent or app generates invoices.
Who is it for?
Solo builders and small teams shipping Spanish-market SaaS or services who want agent-assisted AEAT e-invoice integration.
Skip if: Businesses outside Spain’s VeriFactu scope or teams that need multi-country VAT, payments, and ledger in one suite without AEAT work.
What do I get? / Deliverables
Your agent can drive VeriFactu-compliant electronic invoicing through a local stdio MCP package integrated into Claude Code.
- Agent-triggered VeriFactu electronic invoice workflows
- MCP-accessible bridge between your codebase and AEAT invoicing
- Local stdio integration without a hosted invoice UI
Recommended MCP Servers
Journey fit
Facturación electrónica is integrated when you build billing backends or automation for Spain-facing products, not during pure idea research. This is an MCP bridge to AEAT VeriFactu—canonical placement is integrations because it connects your agent to a national e-invoicing regime.
How it compares
AEAT VeriFactu MCP bridge, not a general Stripe-style payments skill or accounting marketplace.
Common Questions / FAQ
Who is verifactu-mcp for?
Developers and solo founders in Spain (or building for Spanish customers) who use Claude Code and need VeriFactu electronic invoicing via MCP.
When should I use verifactu-mcp?
Use it while building or operating billing integrations that must submit or align with AEAT VeriFactu from your agent workflow.
How do I add verifactu-mcp to my agent?
Install the PyPI package verifactu-mcp (v0.1.1), configure stdio MCP in Claude Code, and follow the GitHub repo setup for AEAT credentials and environment.