Zucchetti
Zucchetti ERP and HR suites over the Zucchetti REST / Infinity API: anagrafiche, documents, items and HR records. Basic or token auth against the customer's own Infinity or Ad Hoc installation. Partner credentials required.
7 giorni gratis · senza carta · hosting UE
Chiedi qualsiasi cosa a Zucchetti
Prova un prompt reale su Zucchetti via AnythingMCP — Claude chiama i tool e risponde. Premi Enter sul tuo messaggio per installare su Cloud.
Installa Zucchetti su CloudClaude è un'AI e può sbagliare. Verifica sempre le risposte.
Setup in 2 minuti
- 1Avvia la trial gratuita su cloud.anythingmcp.com.
- 2Clicca Zucchetti nel connector store. Incolla le credenziali quando richiesto.
- 3Genera una MCP API key e punta il client AI all'URL MCP generato.
Guide per Zucchetti
Setup passo-passo per i principali client AI.
Configurare Zucchetti
Direttamente dalla definizione del connettore: dove trovare le credenziali, quali permessi servono e con quale API parla questo adapter. Fornite in inglese dall'autore del connettore.
Partner credentials required, and Zucchetti is not one product. The group ships dozens of applications — Infinity Zucchetti, Ad Hoc Revolution, HR Zucchetti, Mago — each with its own API surface, versioning and documentation, distributed through the partner portal rather than publicly. There is no single api.zucchetti.it, and no public sandbox. This adapter therefore ships unverified and deliberately generic: it gives you an authenticated, paged HTTP client against a Zucchetti Infinity-style REST endpoint, and expects you to point it at the module you actually licensed.
Setup
- Ask your Zucchetti partner for the REST endpoint of the installation and the API user. They will also tell you the service path prefix, which differs per module.
- Set
ZUCCHETTI_URLto that endpoint root (no trailing slash), plusZUCCHETTI_USERNAMEandZUCCHETTI_PASSWORD. - Set
ZUCCHETTI_COMPANYto the azienda code if the installation hosts several.
resource is a parameter, not a path. Because the entity names differ per module, zucchetti_list_records and zucchetti_get_record take the resource name (anagrafiche, documenti, articoli, dipendenti, …) as an argument. Your partner's documentation is the authority on which names your installation exposes.
Start with zucchetti_list_services, which asks the installation what it publishes. If it 404s, your endpoint prefix is different from the default and everything else will 404 too — fix that before anything else.
Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.
Self-hosted, which is the thing to plan for.
- On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
- On an internal host (
zucchetti.intern,10.0.0.x), self-host AnythingMCP on the same network and add that host toSSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.
La tua AI è a due click da Zucchetti.
Installa il connettore, incolla le credenziali, chiedi all'AI. 7 giorni gratis, niente carta.