Skip to main content
Glama
badbat75

FattureInCloud MCP

by badbat75

Related Servers

Alternatives to FattureInCloud MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      MCP 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.
      6
      3
      -
    • A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server for the Holded Invoice API. This server allows AI assistants like Claude to interact with Holded's invoicing, contacts, products, and more.
      78
      45 npm
      19
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Hosted 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.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for the FreshBooks API that lets Claude read and manage invoices, clients, expenses, projects, services, payments, and time entries.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that connects Claude Code to the Holded API for natural language financial, accounting, and invoicing queries, with built-in Spanish PGC context.
      13
      2
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for creating and fiscalizing invoices via solo.com.hr API. Enables AI agents to generate invoices, retrieve invoice details, list invoices, and check next invoice number.
      4
      MIT

    TDQS

    A4.2/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource (issued document, received document, company, company info, attachment) and action (get, create, list, update, delete, upload, remove). The parallel issued/received sets are clearly separated by document type, and the attachment tools are distinct. No two tools could be confused for the same purpose.

    Naming Consistency4/5

    The core document tools follow a consistent verb_noun pattern: get_issued_document, create_received_document, list_issued_documents, etc. Minor deviations exist: 'get_company_info' and 'delete_document_attachment' use slightly different structures (info suffix, document_attachment compound). Overall, the pattern is predictable and readable.

    Tool Count5/5

    14 tools is well-scoped for a document management server. It covers two document types with full CRUD plus list, company management, configuration lookup, and attachment handling. Each tool has a clear role, and the count is not excessive or overly sparse.

    Completeness4/5

    The toolset provides complete CRUD and listing for both issued and received documents, plus company info and attachment upload/delete. A notable gap is the lack of a download attachment (or document PDF) function, which would be useful for a full document workflow, but the core lifecycle is covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues