Skip to main content
Glama
MatiasMinoni

ARCA Invoice MCP

by MatiasMinoni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to ARCA Invoice MCP

No user-submitted related servers found.

    Related Servers

    • keycae-mcp

      AMKRS3
      A
      license
      A
      quality
      F
      maintenance
      Argentine electronic invoicing (facturación electrónica) MCP Server for ARCA/AFIP. Emit invoices, manage credentials, check delegations, and look up taxpayers. 10 tools.
      12
      378 npm
      MIT

    • mcp-facturacion-electronica-es

      cmendezs
      A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Spanish Electronic Invoicing. Provides tools to generate, validate, and submit invoices across VERI\*FACTU, Facturae/FACe, SII, TicketBAI, and Crea y Crece B2B.
      20
      2
      Apache 2.0

    • velora-mcp

      crossi-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Hosted 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

    • peru-invoice-mcp

      junter1989k-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to issue Peruvian electronic invoices (factura/boleta) declared to SUNAT via Nubefact. Supports creating, querying, and canceling invoices with automatic IGV tax computation.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool covers a distinct action: prepare, issue, list, discard, and status. These lifecycle stages are clearly separated, so an agent can unambiguously select the correct tool for a given need.

    Naming Consistency4/5

    Four of the five tools follow the arca_verb_noun pattern (arca_prepare_invoice, arca_issue_invoice, arca_list_invoices, arca_discard_prepared_invoice). However, arca_invoice_status breaks this pattern by using a noun-like 'status' instead of a verb, causing a minor inconsistency.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its invoice lifecycle purpose. Each tool earns its place without redundancy or bloat, fitting the ideal 3-15 range.

    Completeness4/5

    The lifecycle of prepare, issue, discard, list, and local status covers the core workflow. However, after an uncertain issue response, there is no direct tool to verify the invoice status on the ARCA side (list_invoices requires knowing the date range and may not be real-time), leaving a minor gap in uncertainty resolution.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources