ArcaMCP
Related Servers
Alternatives to ArcaMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for integrating with AFIP (Argentine tax agency) to query documentation, manage authentication, and handle electronic invoicing.11 npmMIT
- AlicenseAqualityFmaintenanceArgentine electronic invoicing (facturación electrónica) MCP Server for ARCA/AFIP. Emit invoices, manage credentials, check delegations, and look up taxpayers. 10 tools.12378 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for ARCA (Agencia de Recaudación y Control Aduanero) that provides tools for AFIP electronic invoicing and authentication via stdio transport.11 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server to issue ARCA/AFIP Factura C for monotributistas using Afip SDK, PostgreSQL, and a secure preview-before-emission flow.MIT
- AlicenseAqualityDmaintenanceMCP server for Italian electronic invoicing via the Invoicetronic API, enabling management of invoices through SDI with 20 tools for sending, receiving, exporting, and more.1826 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceHosted MCP server for Argentine commerce: real AFIP/ARCA fiscal invoicing (live CAE), MercadoPago payments, logistics, catalog, cash register and WhatsApp behind one authenticated endpoint. Includes 9 no-auth fiscal validation/formatting tools.MIT
TDQS
Scored across 20 tools
Most tools target distinct resources or actions, and the many get_*_types catalog lookups are clearly separated by their respective AFIP type. The main overlap is create_voucher vs create_next_voucher, which both mint a voucher and differ only in explicit vs auto numbering, which could cause misselection without reading carefully.
The set follows a clean get_*/create_* verb_noun snake_case pattern throughout. The main deviation is 'mis_comprobantes', a Spanish, verbless name that breaks the otherwise consistent English convention (though get_currencies_types has a minor plural awkwardness).
At 20 tools the set is on the heavy side but each catalog lookup (concepts, document types, aliquots, taxes, etc.) maps to a genuine AFIP data domain, so most tools earn their place. The many independent get_*_types tools could in principle be consolidated, keeping it slightly above ideal.
The surface covers voucher creation (explicit and auto-numbered), retrieval, PDF generation, taxpayer lookup, certificate status, and full AFIP catalog discovery, plus an async automation for downloading comprobantes. The main gaps are no voucher listing/history or void/credit-note lifecycle beyond the generic create path, but core invoicing workflows are covered.