Skip to main content
Glama
almostnine

Fatture in Cloud MCP

by almostnine

Related Servers

Alternatives to Fatture in Cloud MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables integration with Fatture in Cloud to manage Italian electronic invoices through natural conversation, including creating, sending, and tracking invoices and financial data.
      45 PyPI
      23
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Fatture in Cloud API v2 that lets Claude read and manage issued and received documents (invoices, credit notes, quotes, expenses, etc.) via CRUD operations.
      14
      1,544 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with freee accounting software through OAuth 2.0 authentication, supporting operations like transaction creation, account management, receipt uploads, and financial statement retrieval.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language management of FattureInCloud invoicing, clients, suppliers, and e-invoice workflows, with extensions for marking invoices as paid and caching payment accounts/VAT types.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Gives Claude access to a FreeAgent company, enabling read and write operations on contacts, projects, invoices, bills, and bank transactions with journaled undo support.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to inv.bg invoicing data, enabling users to list clients and invoices and retrieve full document details and line items through natural language in Claude.
      1
      -

    TDQS

    A3.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct scopes: list vs get for issued/received documents, installments, entities, and reference data are well separated. Minor overlap exists between fic_get_einvoice and fic_get_issued_document (both expose e-invoice status), and between fic_list_installments and fic_get_entity with include_open_installments, but descriptions clarify the intended use.

    Naming Consistency4/5

    All tools use a consistent fic_ prefix and snake_case, making the set very predictable. However, the pattern is not strictly verb_noun: some tools use noun phrases (fic_account_info, fic_situation, fic_reference_data, fic_api_catalog), which is a minor deviation.

    Tool Count4/5

    17 tools is slightly above the typical 3–15 range but reasonable for a broad accounting suite covering issued/received documents, entities, installments, reconciliation, reference data, and API passthrough. Each tool appears to serve a distinct purpose, though the set is on the heavier side.

    Completeness2/5

    The surface is mostly read-only despite descriptions referencing server write modes and a missing fic_api_write tool. Core write operations such as creating/updating invoices, registering payments, or managing clients are absent, and fic_set_installment_status is mentioned in fic_reconcile but not included. This will cause agent failures for common accounting workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues