SDI vs Billingengine MCP
A side-by-side look at the SDI and Billingengine MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
SDIFinance & Fintech · Local subprocess (stdio)Italian e-invoicing (FatturaPA/SDI): parse invoices, detect anomalies, VAT checks via VIES, reports.53GoodAuth: no auth requiredVerdict: choose SDI for finance & fintech work as a local process; choose Billingengine MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose SDI when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
FATTURAPA_ALLOWED_ROOTS. - You want tools like
validate_invoice, extract_invoice_data, lookup_sdi_error.
Choose Billingengine MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
BILLINGENGINE_API_KEY. - You want tools like
find_customers, create_customer, update_customer.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | SDI | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 53/100 · Good | 78/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Paid service |
| Required env vars | FATTURAPA_ALLOWED_ROOTS | BILLINGENGINE_API_KEY |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 7 | 10 |
| Full listing | View SDI | View Billingengine MCP |
Tools & capabilities
SDI tools 7
validate_invoiceChecks that the XML is well-formed and has the FatturaPA root structure. ⚠️ **Not yet a full schema validation** — see Known limitationsextract_invoice_dataExtracts supplier, customer, amounts, line items and metadata from a valid FatturaPA documentlookup_sdi_errorReturns description, category and resolution hint for SDI error codes (offline). ⚠️ The table is being realigned with the official list — see Known limitationscheck_pivaValidates an Italian P.IVA (VAT number) using the official MEF checksum algorithm — no network callverify_piva_viesVerifies any EU VAT number against the live VIES REST API; degrades gracefully when the service is downfind_invoice_anomaliesDetects anomalies in a FatturaPA XML document: inconsistent totals, wrong VAT, future dates, invalid P.IVA, missing recipient, incomplete line items, negative amounts, missing payment infogenerate_invoice_reportAggregates multiple FatturaPA XML documents into a single report with statistics, supplier/customer breakdown and anomaly summary
Billingengine MCP tools 10
find_customersSearches customers by company, name or emailcreate_customerCreates a customerupdate_customerChanges a customercreate_invoiceCreates a **draft** invoice for a customerupdate_invoiceChanges a draft invoicelist_invoicesLists invoices, filtered by status, customer, number or dateget_invoiceReturns one invoice with items and payment statusdownload_invoiceSaves the PDF or the XML e-invoice to your Downloads folderrecord_paymentRecords a payment for sent invoiceslist_paymentsLists payments, optionally for one invoice
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SDI
{
"mcpServers": {
"fatturapa-sdi": {
"command": "uvx",
"args": [
"fatturapa-mcp-server"
],
"env": {
"FATTURAPA_ALLOWED_ROOTS": "YOUR_FATTURAPA_ALLOWED_ROOTS_HERE"
}
}
}
}
Billingengine MCP
{
"mcpServers": {
"billingengine-mcp": {
"command": "npx",
"args": [
"-y",
"billingengine-mcp"
],
"env": {
"BILLINGENGINE_API_KEY": "YOUR_BILLINGENGINE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
SDI is categorized under Finance & Fintech and uses a local stdio subprocess. Billingengine MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick SDI for finance & fintech work and Billingengine MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
SDI is listed as free. Auth: no auth required. Billingengine MCP is listed as a paid service. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fatturapa-sdi and billingengine-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SDI has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Billingengine MCP has 78/100 (Great) with 3 views, 0 installs and 0 GitHub stars.