BeeL

What BeeL MCP server does

The BeeL MCP server gives an MCP-compatible AI agent access to BeeL’s Spanish electronic invoicing system. Its main scope is VeriFactu registration with AEAT, including invoice issuance, invoice correction, customer and company management, product data, recurring invoices, series, tax configuration, and NIF validation against the census.

The server exposes 124 tools generated from BeeL’s public OpenAPI contract. It also adds synthetic tools for searching and reading documentation, looking up fiscal rules, inspecting API schemas, and checking setup status for a NIF. Setup status reports missing requirements, the next action, and identifiers such as the company and default invoice series.

The BeeL MCP server includes workflow prompts for issuing and fixing invoices, onboarding a NIF, setting up representation, inviting a member, connecting payments, and upgrading an integration. Generating an invoice PDF can open an inline viewer in MCP hosts that support MCP Apps.

How it works

Tools are derived from the public API specification, so their input structures include the API’s fields, enumerations, line-item definitions, and regime keys. A selection policy excludes operations that are unsuitable for agents, including binary downloads, multipart uploads, webhook infrastructure, browser-only authentication flows, and deprecated endpoints.

Fiscal guidance is available through tool descriptions, guardrail resources, and rule lookup tools. These resources cover invoice corrections, invoice types, regime keys, API usage, and error codes. The server also performs pre-flight checks intended to stop requests that violate supported fiscal constraints before they become fiscal documents. Workflow prompts encode ordering where sequence matters, such as validating a NIF, selecting F1 or F2, checking VeriFactu requirements, and then issuing an invoice.

Setup and configuration

For interactive use, connect an MCP client to https://mcp.beel.es/mcp. The hosted endpoint uses Streamable HTTP and OAuth, so users sign in with their BeeL account and do not need to install the package or manage an API key.

For headless processes such as scheduled jobs or CI pipelines, install or run the local package through npm. The local server requires Node 20 or newer and authenticates with BEEL_API_KEY.

{
  "mcpServers": {
    "beel": {
      "command": "npx",
      "args": ["-y", "@beel_es/mcp"],
      "env": { "BEEL_API_KEY": "beel_sk_test_xxx" }
    }
  }
}

Test keys begin with beel_sk_test_; live keys begin with beel_sk_live_ and issue real fiscal documents. The hosted and local transports are both listed for the es.beel/mcp MCP Registry entry.

Tools and capabilities

The BeeL MCP server provides:

• Invoice issuance and correction workflows for Spanish e-invoicing.
• Customer, company, product, series, tax, and recurring-invoice operations.
• NIF validation and per-NIF setup status checks.
• Documentation, fiscal-rule, schema, and error-code lookup.
• Guardrail resources describing applicable fiscal and API rules.
• Workflow prompts for common invoicing and account-management sequences.

Limitations and notes

The server does not expose binary downloads, bulk ZIP or spreadsheet exports, multipart imports, signed-PDF submission, webhook infrastructure, browser-only operations, or deprecated API operations as agent tools. PDF viewing depends on host support for MCP Apps. OAuth is intended for interactive hosted use; local headless execution uses an API key instead.