The v2 version has been released, introducing a significant change in how this MCP works.
In version 1, each API required a dedicated tool. However, since Zabbix exposes a large number of APIs and each user typically needs only a subset of them, this approach is no longer scalable. Exposing all tools individually led to a rapidly increasing number of tools connected to the model, resulting in higher token consumption and reduced efficiency.
In v2, we have moved to a new approach: a single unified tool provides access to all APIs, complemented by two additional tools for documentation retrieval.
This redesign greatly reduces tool sprawl and improves overall efficiency and maintainability.
Additionally, various improvements and fixes have been introduced based on issues and pull requests submitted by the community.