Tools & prompts
The tools the BeeL. MCP server exposes and what they do not cover yet, the guided workflow prompts, and the inline invoice PDF viewer.
Through the BeeL. MCP server your assistant can issue and manage invoices, customers, products, series, recurring invoices and NIFs, run your account's members and webhooks, and read your fiscal data. On top of that there are a few helper tools and guided prompts that keep fiscal steps in the right order.
The tools are derived from the API contract, so each one takes the same fields as the operation behind it. They cover most of the API, not all of it: some operations are left out on purpose and a few newer ones are not exposed yet. See what the tools don't cover. This page describes version 0.5.0 of the server.
Tools are named beel_<action> and grouped by resource. Each needs specific scopes; the assistant can only use a tool if the scopes you approved on the consent screen cover it.
Helper tools
A few tools help the assistant orient itself before it acts:
| Tool | Description |
|---|---|
beel_get_setup_status | One-call checklist of every NIF's readiness with a recommended next action — the fastest way to see what's missing. |
beel_docs_search | Search these docs from inside the client. |
beel_docs_get | Read a documentation page in full. |
beel_docs_list | List the available documentation pages. |
beel_rules_list | List the fiscal rules, one line each, filtered by domain, responsibility (enforced_by), severity or keywords. Called with no filters it also lists the domains. |
beel_rules_get | Read one fiscal rule by id (statement, legal basis, error codes, examples, related rules), or every rule that cites an error code. |
When an API call fails with an error code that a rule cites, the error the assistant gets back names that rule. For the other ways to use the rules, see Use the rules in your tools.
Guided prompts
Prompts are templates you invoke like a command; they seed the conversation with the correct order of operations so the assistant doesn't skip a fiscal step.
| Prompt | What it does |
|---|---|
issue-invoice | Issue an invoice: F1 vs F2, validate the NIF, set regime keys, clear the VeriFactu gates. |
fix-invoice | Fix an issued invoice the right way: void vs corrective invoice (R1–R5). |
onboard-nif | Get a NIF ready to issue Live end to end: readiness → default series → VeriFactu → payments → first Test invoice. |
setup-representation | Set up the AEAT fiscal representation (apoderamiento) a NIF needs for VeriFactu — resolves the NIF_REPRESENTATION_REQUIRED blocker. |
invite-member | Invite a collaborator (such as an accounting firm) or teammate and grant the right role, account-wide or per-NIF. |
connect-payments | Connect Stripe to a NIF or account-wide, and verify it is active. |
upgrade-integration | Bring an existing BeeL. API integration up to current best practices. |
Inline invoice PDF
When the assistant fetches an invoice PDF, the BeeL. MCP server returns it as an MCP App: a client that supports MCP UI (such as Claude) renders the invoice inline in the chat as an embedded viewer, instead of a bare download link — so you review the document without leaving the conversation.
Tool catalogue
The API tools, grouped by resource, with the scopes each one needs.
What the tools don't cover
Left out on purpose. Operations that move a file, operations that only a signed-in dashboard session can call, and deprecated operations have no tool:
- Downloading several invoice PDFs as a ZIP, exporting invoices to Excel, and the PDF preview of a draft. For a single invoice,
beel_get_invoice_pdfreturns the download URL and the client shows the PDF inline. - Uploading a company logo, importing customers or managed accounts from a file, the import templates, and submitting the signed representation document.
- Setting the account owner.
Not exposed yet. These operations are in the API but have no tool in this version. Call them through the API or the Node SDK meanwhile:
- Listing the VeriFactu records of an invoice.
- Recurring invoice statistics.
- Updating a payment connection's settings.
- Resolving, discarding and restoring payment events.
Payment event tools fail in 0.5.0
beel_list_payment_events, beel_get_payment_event, beel_retry_payment_event, beel_generate_payment_event_draft and beel_disconnect_payment_connection still appear in your client's tool list, but they address a connection by its provider, a route shape the API no longer serves. Every call to them fails. They are left out of the catalogue above. To audit or recover payment events, or to disconnect a connection, use the API or the SDK, which address each connection by its own ID. See Payment connections.
Related
Overview
Connect AI assistants to BeeL. through the Model Context Protocol — issue invoices, manage NIFs and customers, and read your fiscal data in natural language, with VeriFactu guardrails built in.
Claude Code
Use the BeeL. plugin for Claude Code to implement, audit, and maintain BeeL. API integrations with AI assistance.