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 任何事
通过 AnythingMCP 对 Zucchetti 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 ZucchettiClaude 是 AI,可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Zucchetti。提示时粘贴凭据。
- 3生成 MCP API 密钥,将 AI 客户端指向生成的 MCP URL。
配置 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
- 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.