Zucchetti

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 días gratis · sin tarjeta · hosting UE

Pregunta cualquier cosa a Zucchetti

Prueba un prompt real contra Zucchetti vía AnythingMCP — Claude llama a los tools y responde. Pulsa Enter en tu mensaje para instalar en Cloud.

Instalar Zucchetti en Cloud
Zucchetti · live vía MCP
Compartir
Opus 4.7

Claude es IA y puede equivocarse. Verifica siempre las respuestas.

Setup en 2 minutos

  1. 1Inicia trial gratuita en cloud.anythingmcp.com.
  2. 2Click en Zucchetti en el connector store. Pega las credenciales.
  3. 3Genera MCP API key y apunta el cliente AI a la URL MCP.
Instalar Zucchetti ahora

Guías para Zucchetti

Setup paso a paso para los principales clientes AI.

Configurar Zucchetti

Directamente de la definición del conector: dónde encontrar las credenciales, qué permisos necesitan y con qué API habla este adaptador. Proporcionadas en inglés por el autor del conector.

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

  1. 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.
  2. Set ZUCCHETTI_URL to that endpoint root (no trailing slash), plus ZUCCHETTI_USERNAME and ZUCCHETTI_PASSWORD.
  3. Set ZUCCHETTI_COMPANY to 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 to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.

Tu IA está a dos clicks de Zucchetti.

Instala el conector, pega credenciales, pregunta a la IA. 7 días gratis, sin tarjeta.