The app.wishpool/luxembourg-invoice-mcp server enables AI agents to work with Luxembourg Peppol BIS 3.0 e-invoices. It supports sending e-invoices, checking a recipient, and retrieving delivery proof. The server exposes three tools (toolCount: 3) for these tasks.

🛠️ Key Features

Luxembourg Peppol BIS 3.0 e-invoices
Send e-invoices
Check recipient
Get delivery proof
MCP server accessible via https://inv-lu.wishpool.app/mcp

🚀 Use Cases

Automating Luxembourg invoice submission by an AI agent
Verifying recipient details before sending invoices
Providing delivery evidence after an invoice is sent

⚡ Developer Benefits

“Nothing to install” for basic use
Credentials are sent as HTTP headers on each request and are not stored (per the readmeExcerpt)
Intended for MCP-capable clients (e.g., Claude Desktop, Cursor, Windsurf)

⚠️ Limitations

Requires an MCP client configuration to connect to the HTTP endpoint; additional steps may be needed when credentials are required.

Luxembourg Invoice MCP 🇱🇺 — How can my AI agent send a Peppol e-invoice (facture électronique) in Luxembourg?

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

json

{
  "mcpServers": {
    "luxembourg-invoice": {
      "type": "http",
      "url": "https://inv-lu.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

bash

git clone https://github.com/junter1989k-ai/luxembourg-invoice-mcp && cd luxembourg-invoice-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Remote MCP server that lets any AI agent send Luxembourg B2B electronic invoices (facture électronique) over the Peppol network in Peppol BIS 3.0 / EN 16931 format via Storecove, a certified Peppol Access Point. It builds the structured invoice, computes the Luxembourg VAT breakdown, and delivers it under the merchant's own Storecove account. Stateless, bring-your-own credentials, never stores anything.

Live endpoint: https://inv-lu.wishpool.app/mcp · Registry: app.wishpool/luxembourg-invoice-mcp

Why now — B2G mandatory, B2B on the way

Luxembourg has mandated structured e-invoicing over Peppol for B2G since 2023 (fully in force for all sizes of business), and B2B e-invoicing is expected to be legislated around 2026. Sending a structured Peppol invoice (facture électronique) now is future-proof — a structured EN 16931 document delivered over Peppol, not a plain PDF.

Quick start

json

{
  "mcpServers": {
    "luxembourg-invoice": {
      "type": "http",
      "url": "https://inv-lu.wishpool.app/mcp",
      "headers": {
        "x-storecove-key": "your-storecove-api-key"
      }
    }
  }
}

Sign up at storecove.com — the merchant is the Peppol Access Point account holder. Request a free 30-day sandbox account from Storecove for a test key (sandbox does not need production onboarding). Create your sender under Senders to get the legalEntityId you pass as seller_legal_entity_id. Sandbox vs production is determined by the account your key belongs to — the base URL is the same. Authentication is HTTP Bearer with your key. Your key stays with you and travels per-request; this server never stores it.

Tools

Tool	What it does
`check_recipient`	Peppol participant discovery — is the buyer reachable on Peppol before you send? Pass the identifier (VAT number scheme `9938`). Returns `can_receive`. The safe pre-flight.
`create_invoice`	Build a Peppol BIS 3.0 invoice from seller + buyer (Luxembourg VAT `LUxxxxxxxx`, address) and line items (description, net unit price, VAT rate 17/14/8/3/0, quantity), then submit over Peppol via Storecove. Returns a submission `guid` + computed VAT totals (`taxable`, `vat`, `total`).
`get_delivery_evidence`	Fetch the proof of what was sent and the Peppol delivery status by `guid`.

Amounts are in EUR. Luxembourg VAT (TVA) rates: 17 (standard), 14 (intermediate), 8 (reduced), 3 (super-reduced), 0 (zero-rated/exempt/reverse charge). Parties identified by Luxembourg VAT (LUxxxxxxxx, Peppol scheme 9938).

No cancel over Peppol — to reverse an invoice you issue a credit note (a new invoice). create_invoice needs seller_legal_entity_id (your Storecove sender id). Owner policy guardrails ride optional headers (x-agentpay-max-amount, x-agentpay-approval-above, x-agentpay-allowed-tools) — set by the human owner in client config; the agent cannot relax them.

VAT math (deterministic)

Per line amountExcludingVat = round2(quantity × unit_price); grouped by (rate, category) into taxSubtotals (taxableAmount, taxAmount = round2(taxable × rate / 100)); gross amountIncludingVat = taxable + tax. Examples:

100 + 50 both @17% → taxable 150.00 / vat 25.50 / total 175.50
200 @17% + 100 @8% → taxable 300.00 / vat 42.00 (34 + 8) / total 342.00
100 @17% + 50 @14% + 40 @8% + 100 @3% + 25 @0% → taxable 315.00 / vat 30.20 (17 + 7 + 3.20 + 3 + 0) / total 345.20
rounding: 3×11.11 @3% → line 33.33, vat 1.00 (0.9999 rounded) / total 34.33

Endpoints wrapped (Storecove REST)

Base: https://api.storecove.com/api/v2 (single base URL; auth = HTTP Bearer with your API key)
Send: POST /document_submissions — JSON { legalEntityId, routing, document:{ documentType:"invoice", invoice:{…} } } → { guid }
Evidence: GET /document_submissions/{guid}/evidence — proof of what was sent + Peppol delivery status
Discovery: POST /discovery/receives — JSON { documentTypes, network, metaScheme, scheme, identifier } → { code:"OK", email }
Verified probe (2026-07-10): a fake Bearer key really hits api.storecove.com/api/v2 → 403 {"errors":[{"source":"generic","details":"Not Authorized"}]} (endpoint alive; BYO = the merchant's own key validates).

Develop

bash

node test/serve.js   # local server on :3245
node test/e2e.js     # VAT math + Peppol JSON structure + protocol + validation + policy + fake-key live probe

Safety

Pure stateless translation layer over the Storecove REST API. Storecove is the certified Peppol Access Point under the merchant's own account; this service never signs, never onboards, and never stores anything. The API key travels per-request in a header, and funds are never touched — this issues tax invoices, it does not move money. Privacy policy.

Sister servers

Local invoices, one family: Belgium Peppol (inv-be) · Netherlands Peppol (inv-nl) · Italy FatturaPA (inv-it) · Malaysia MyInvois (inv-my) · Mexico CFDI (inv-mx) · Brazil NF-e (inv-br) · India GST (inv-in). Storecove also covers the Netherlands, Belgium and the Nordics on Peppol — those sister countries replicate this exact server. Local logistics: logi.wishpool.app. Local payments in 81 countries: mcp.wishpool.app.

MIT licensed.

seller_legal_entity_id	string	required	REQUIRED. The Storecove legalEntityId of the sender (created in your Storecove account under Senders). Numeric id, passed through to Storecove.
seller_name	string	required	Seller legal/company name.
seller_vat	string	required	Seller Luxembourg VAT (TVA) number, format LUxxxxxxxx (LU + 8 digits). Required — Luxembourg parties are identified on Peppol by their VAT number (scheme 9938).
seller_address	string	required	Seller street address.
seller_city	string	required	Seller city.
seller_zip	string	required	Seller postal code.
seller_country	string	optional	Seller country code. Default LU.
customer_name	string	required	Buyer legal/company name.
customer_vat	string	optional	Buyer Luxembourg VAT number LUxxxxxxxx (used to route on Peppol, scheme 9938, if no explicit recipient id is given).
customer_address	string	required	Buyer street address.
customer_city	string	required	Buyer city.
customer_zip	string	required	Buyer postal code.
customer_country	string	optional	Buyer country code. Default LU.
recipient_peppol_scheme	string	optional	Optional explicit Peppol routing scheme (EAS/ISO6523). Luxembourg: 9938 (LU VAT number). Default 9938 when routing by VAT number.
recipient_peppol_id	string	optional	Optional explicit Peppol participant identifier to route to (overrides deriving from the customer VAT number).
recipient_email	string	optional	Optional email fallback — used if the recipient is not on Peppol (Storecove can email a copy).
invoice_number	string	optional	Invoice number. Auto-generated if omitted.
issue_date	string	optional	Invoice issue date, YYYY-MM-DD. Default: today (UTC).
due_date	string	optional	Optional payment due date, YYYY-MM-DD.
currency	string	optional	Document currency. Default EUR.
note	string	optional	Optional free-text note on the invoice.
lines	array	required	Invoice line items. Each: description, unit_price (net, VAT-exclusive, EUR), vat_rate (17\|14\|8\|3\|0), optional quantity (default 1), optional tax_category (S standard / Z zero-rated / E exempt / AE reverse charge; default S for rate>0, Z for rate 0), optional item_name.

identifier	string	required	The recipient Peppol identifier. Luxembourg: the VAT number LUxxxxxxxx (scheme 9938).
scheme	string	optional	Peppol/ISO6523 scheme. Default 9938 (Luxembourg VAT number).
network	string	optional	Network to check. Default peppol.
document_types	array	optional	Document types to check receipt for. Default ["invoice"].

Luxembourg Invoices (Peppol BIS 3.0 via Storecove)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_invoice

check_recipient

get_delivery_evidence