Fatture in Cloud MCP
Related Servers
Alternatives to Fatture in Cloud MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables integration with Fatture in Cloud to manage Italian electronic invoices through natural conversation, including creating, sending, and tracking invoices and financial data.44 PyPI25MIT
- AlicenseAqualityCmaintenanceMCP 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.14108 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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
- AlicenseNot gradedqualityCmaintenanceEnables Claude to access Acumatica ERP 2025 R2 through per-user OAuth and role-governed tools for lookups, discovery, documentation, and optional customer updates. Includes consent, sensitive-field redaction, rate limiting, pagination safeguards, and audit logging.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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
- FlicenseNot gradedqualityDmaintenanceGives Claude access to a FreeAgent company, enabling read and write operations on contacts, projects, invoices, bills, and bank transactions with journaled undo support.-
TDQS
Scored across 17 tools
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.
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.
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.
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.