Denmark Invoice MCP 🇩🇰 — How can my AI agent send a Peppol/NemHandel e-invoice in Denmark?

Use it in 60 seconds

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

{
  "mcpServers": {
    "denmark-invoice": {
      "type": "http",
      "url": "https://inv-dk.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:

git clone https://github.com/junter1989k-ai/denmark-invoice-mcp && cd denmark-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 Denmark B2B electronic invoices over the Peppol network in Peppol BIS 3.0 / EN 16931 format via Storecove, a certified Peppol Access Point. Denmark delivers over Peppol / NemHandel. It builds the structured invoice, computes the Danish VAT (moms) breakdown, and delivers it under the merchant's own Storecove account. Stateless, bring-your-own credentials, never stores anything.

Live endpoint: https://inv-dk.wishpool.app/mcp · Registry: app.wishpool/denmark-invoice-mcp

Related MCP server: norway-invoice-mcp

Why now — the Bookkeeping Act (elektronisk faktura NemHandel)

Denmark's Bookkeeping Act (Bogføringsloven) phases in mandatory digital bookkeeping and structured e-invoice send/receive over Peppol / NemHandel: from 2024 for reporting-obligated companies (accounting classes B/C/D), extending from 2026-01 to class A businesses with revenue above DKK 300,000. Paper and plain-PDF invoices no longer satisfy the B2B obligation for covered businesses.

Quick start

{
  "mcpServers": {
    "denmark-invoice": {
      "type": "http",
      "url": "https://inv-dk.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

Amounts are in DKK. Danish VAT (moms) rates: 25 (single standard rate), 0 (zero-rated/exempt/reverse charge). Parties identified by Danish VAT (DKxxxxxxxx) and/or CVR number (8 digits); Peppol routing scheme 0184.

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 @25% → taxable 150.00 / vat 37.50 / total 187.50

• 200 @25% + 100 @0% → taxable 300.00 / vat 50.00 (50 + 0) / total 350.00

• 3×33.33 @25% → taxable 99.99 / vat 25.00 (rounded from 24.9975) / total 124.99

• rounding: 33.33 @25% → 33.33 × 0.25 = 8.3325 → vat 8.33 / total 41.66

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: 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

node test/serve.js   # local server on :3245
node test/e2e.js     # VAT math + Peppol/NemHandel 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: Norway Peppol/EHF (inv-no) · Belgium Peppol BIS (inv-be) · 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 Nordics, the Netherlands and Luxembourg on Peppol — those sister countries replicate this exact server. Local logistics: logi.wishpool.app. Local payments in 81 countries: mcp.wishpool.app.

MIT licensed.