monzphere-zabbix-module-builder vs Zabbix API MCP
monzphere-zabbix-module-builder is a plugin bundle for AI coding tools published by Monzphere. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Zabbix API MCP is an MCP server published by shigechika. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Zabbix API MCP | |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 7f7f54f No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.13.0 Downloads/month (PyPI): 381 Downloads/week (PyPI): 147 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | monzphere-zabbix-module-builder | Zabbix API MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (zapi-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/monzphere/zabbix-module-builder | github.com/shigechika/zapi-mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
monzphere-zabbix-module-builder
Generate complete Zabbix 7.x frontend modules with one slash command. Outputs manifest, PHP controller, view, scoped JavaScript, and theme-aware CSS following the MonZphere ruleset: mnz- CSS prefix, default + .blue-theme + dark-theme, _ i18n, CProfile for user state, CWebUser/CRoleHelper for permissions, JS-on-view loading, and a "Developed by MonZphere" footer. Commercial — $5/month subscription.
Zabbix API MCP
MCP server for the Zabbix API — daily brief, problems, hosts, items
How to run each
monzphere-zabbix-module-builder As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install monzphere-zabbix-module-builder@claude-communityZabbix API MCP As a local MCP server: PyPI package
claude mcp add --transport stdio zapi-mcp -- uvx zapi-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: monzphere-zabbix-module-builder · What it can do: Zabbix API MCP · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.