This page is an honest hub: what FacturaHub really connects, today, and what it doesn't. Instead of a logo wall of integrations that don't exist, we tell you the ones in production and the ones on the roadmap. FacturaHub has a single backend shared by all channels, so any data that comes in through one integration appears instantly in the others.
/mcp with real tools (create_invoice, get_overdue, get_profit_loss, get_tax_summary, get_deductible_expenses, receipt OCR, get/save_business_context). Auth via OAuth 2.0 or x-api-key. Step by step at /es/spain/mcp-facturacion./es/spain/n8n.x-api-key or JWT: your code creates invoices, logs expenses, emits Verifactu or prepares the quarterly IVA summary. Spec at /openapi.json, Swagger at /api-docs/, examples at https://github.com/FacturaHub-com/facturahub-api. Detail at /es/spain/api./openapi.json and auto-generate tools for your agent.https://github.com/FacturaHub-com/facturahub-verifactu.There's no Stripe gateway integration or bank connection: you mark payments yourself (or ask the AI from Claude or the dashboard). We'd rather be clear before you assume it.
What isn't there yet (and we don't announce as available):
invoice.paid calling your URL./v1 — today the API lives under /api.Until they arrive, the REST API and MCP cover practically any flow. Everything free and unlimited; only AI is metered (25 actions/month, one-off packs from €4.99).
You talk to your invoicing with the AI: "invoice 1,000 to Acme", "who owes me?". Connect Claude via MCP and the agent acts on your real data.
MCP server at /mcp with real tools (create_invoice, get_overdue, get_profit_loss, get_tax_summary, OCR). OAuth 2.0 or x-api-key auth. See /es/spain/mcp-facturacion.
Connect your store and each order becomes an invoice with sequential numbering and tax data. The only e-commerce integration today; more connectors on the roadmap.
Custom integrations from your code: invoices, expenses, Verifactu, Modelo 303. OpenAPI 3.1 spec at /openapi.json, Swagger at /api-docs. Detail at /es/spain/api.
Point any OpenAPI-to-MCP bridge at /openapi.json and auto-generate tools for the full API for your agent, without writing integration code.
You don't connect it: it comes included and free. When you emit an e-invoice, FacturaHub signs and sends the record to the AEAT. Mandatory in 2027.
Native Zapier/Make, outbound webhooks, public sandbox, /v1 base path and e-commerce connectors beyond WooCommerce are on the roadmap. Not there yet.
In production: Claude/Cursor/ChatGPT via MCP server (AI agent), WooCommerce (orders to invoice), n8n via the API, the REST API with OpenAPI 3.1 spec and Verifactu (AEAT) included. Everything shares a single backend.
Not yet. There is no payment gateway or bank connection: when you get paid, you mark the invoice as paid yourself or ask the AI.
Today with WooCommerce: connect the store and each order becomes an invoice with sequential numbering. Connectors with other e-commerce platforms are on the roadmap. For any other store or your own system, you can create the invoice from your code with the REST API.
Not yet, and we prefer to be honest: native Zapier/Make integration and outbound webhooks are on the roadmap as coming soon. In the meantime, the REST API (x-api-key or JWT) and the MCP server let you build practically any flow with your own tools.
Through the MCP server at /mcp. You connect Claude Desktop, Claude Code, Cursor or ChatGPT with OAuth 2.0 or your x-api-key and your agent gains real tools on your account. The step-by-step, with example config, is at /es/spain/mcp-facturacion.
No. All integrations (MCP, WooCommerce, API, Verifactu) are in the single free, unlimited plan. Only AI is metered: 10 free actions per month and one-off token packs from €4.99 if you need more. No tiered plans or 7-day trial.