pop-mcp
OfficialRelated Servers
Alternatives to pop-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for German e-invoice compliance (XRechnung 3.0 & ZUGFeRD 2.x) enabling AI agents to validate, generate, parse, and check compliance of electronic invoices per EN 16931.61MIT
- FlicenseAqualityBmaintenanceMCP server for interacting with Aruba Fatturazione Elettronica API, enabling users to manage electronic invoices with Claude, including sending invoices to SDI, searching, downloading, and retrieving invoice details and notifications.63-
- AlicenseAqualityAmaintenanceModel Context Protocol (MCP) server for Italian Electronic Invoicing (FatturaPA / SDI). Provide tools to validate, generate, and explore API specifications for Sistema di Interscambio (SDI) interoperability.4355 PyPI1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceHosted MCP server that enables AI assistants to manage clients, invoices, and expenses via the Invox API, supporting actions like drafting, sending, cancelling, and marking invoices as paid, as well as logging expenses and updating client information.-
- AlicenseBqualityBmaintenanceMCP server for VoxFactura enabling AI assistants to query business data (invoices, expenses, project margins, clients, VAT) and create draft quotes or mark invoices paid via a scoped API, with no direct client sends.15MIT
- FlicenseBqualityDmaintenanceMCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.1528 npm-
TDQS
Scored across 16 tools
Most tools have distinct purposes based on their target invoice format or operation. Potential confusion exists between pop_get_invoice_status and pop_get_sdi_document, but descriptions clearly differentiate status polling from document retrieval. Onboarding tools are distinctly sequenced.
All tools follow a consistent pop_ prefix with snake_case. Create tools follow pop_create_<format>_invoice, get tools use pop_get_<resource>, and onboarding tools are grouped as pop_onboarding_*. The naming pattern is predictable and uniform.
With 16 tools, the server is at the high end of the ideal range, but each tool serves a distinct purpose across multiple invoice formats and an onboarding sequence. The count is justified for the domain's breadth.
The server covers SdI and Peppol well with create/status/retrieve/verify operations, but lacks equivalent status and verification tools for KSeF and ZUGFeRD. Generic listing or cancellation tools are missing, and credit note support is inconsistent across formats.