BeeL MCP server

BeeL MCP server — VeriFactu e-invoicing for AI agents

Servidor MCP de facturación electrónica española con VeriFactu (AEAT): crea, emite y rectifica facturas desde Claude, ChatGPT, Cursor o VS Code. MCP server for Spanish e-invoicing with VeriFactu compliance — issue, correct and register invoices with AEAT straight from your AI agent. beel.es · API docs · MCP guide · npm

An MCP (Model Context Protocol) server that lets an AI agent issue legally compliant Spanish electronic invoices — VeriFactu registration with AEAT, F1/F2 invoice types, R1–R5 correctives, NIF validation against the census, and the regime keys the regulation requires. Connect it to Claude, ChatGPT, Cursor or VS Code and your agent can handle Spanish invoicing — facturación electrónica and factura electrónica VeriFactu — end to end, without you writing a single API call.

It is not a generated wrapper around an API. Three things make it usable by a model:

the operation's real schema — enums, line items, regime keys and all. The surface cannot drift from the API.

• Tools are derived from the public OpenAPI contract, so each tool's input schema is

downloads, multipart uploads, webhook plumbing, operations only a browser session can authenticate, and deprecated ones are excluded by rule, not by hand.

• A tool-inclusion policy decides what an agent should actually be given. Binary

miss, both as documentation the model reads and as pre-flight checks that stop a non-compliant request before it becomes a fiscal document.

• Fiscal guardrails travel with the tools: the invariants a generated wrapper would

One codebase, two transports: the hosted remote server at https://mcp.beel.es/mcp (Streamable HTTP + OAuth — one login per user, nothing to install), and a local stdio server built from this repository for headless use, where an API key works and a browser-based login does not.

Quick start

Add https://mcp.beel.es/mcp as a connector in Claude, ChatGPT, Cursor or VS Code and log in with your BeeL account. Nothing to install and no API key to handle: the server acts with your own credentials, and the OAuth flow is discovered from the URL.

# Claude Code
claude mcp add --transport http beel https://mcp.beel.es/mcp

That is the whole setup for interactive use. Read on only if you need the local server.

Running it locally

Use the local server when OAuth cannot: a scheduled job that issues invoices, a CI pipeline, or any headless process where no one is present to complete a browser login. It authenticates with an API key instead.

Requires Node ≥ 20.

Shortened. The full README is on GitHub.