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 дней бесплатно · без карты · EU-хостинг

Спроси Zucchetti что угодно

Попробуй реальный промпт против Zucchetti via AnythingMCP — Claude вызывает tools, возвращает ответ. Нажми Enter на своём сообщении, чтобы установить в Cloud.

Установить Zucchetti в Cloud
Zucchetti · live via MCP
Поделиться
Opus 4.7

Claude — это AI, он может ошибаться. Проверяйте ответы.

Настройка за 2 минуты

  1. 1Запусти free trial на cloud.anythingmcp.com.
  2. 2Нажми Zucchetti в коннектор-сторе. Вставь учётные данные.
  3. 3Выпусти MCP API ключ и направьте AI-клиент на MCP URL.
Установить Zucchetti сейчас

Гиды по Zucchetti

Пошаговая настройка для основных AI-клиентов.

Настройка Zucchetti

Прямо из определения коннектора: где взять учётные данные, какие права им нужны и с каким API работает этот адаптер. Предоставлено автором коннектора на английском языке.

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.

Твой AI в двух кликах от Zucchetti.

Установи коннектор, вставь учётные данные, спроси AI. 7 дней бесплатно, без карты.