Skip to main content
Glama
shigechika

zapi-mcp

by shigechika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to zapi-mcp

No user-submitted related servers found.

    Related Servers

    • zabbix-mcp

      marcelofmatos
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server to access the Zabbix API, providing tools to list hosts, problems, triggers, items, history, and events.
      -

    • Zabbix MCP Server

      leroylim
      A
      license
      C
      quality
      F
      maintenance
      Comprehensive MCP server for integrating with Zabbix monitoring systems, providing 90+ API tools across 19 categories for monitoring, alerting, and infrastructure management.
      100
      15
      MIT

    • zabbix-investigation-mcp

      Edrient17
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that provides Zabbix monitoring data to AI agents, enabling investigation of hosts, metrics, incidents, and triggers with deterministic aggregation.
      -

    • zabbix-mcp-server

      mpeirone
      A
      license
      A
      quality
      C
      maintenance
      🔌 Complete MCP server for Zabbix integration - Connect AI assistants to Zabbix monitoring with 40+ tools for hosts, items, triggers, templates, problems, and more. Features read-only mode and comprehensive API coverage.
      3
      255
      GPL 3.0

    • zendesk-ops-mcp

      avg-ape
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides operational tooling over the Zendesk Support API — ticket triage, SLA monitoring, agent workload analysis, and system health audits.
      11
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools map to distinct resources and actions: health_check is clearly separate, get_problems vs daily_brief could overlap but daily_brief is a curated summary while get_problems is a raw list, and the maintenance/host tools have clear boundaries. Minor overlap between daily_brief and get_problems is clarified by descriptions.

    Naming Consistency4/5

    The majority follow a verb_noun pattern (get_problems, get_hosts, acknowledge_problem, set_maintenance), but health_check and daily_brief are noun phrases, and number agreement is inconsistent (problem vs problems). No mixing of snake_case/camelCase, so the overall consistency is good but not perfect.

    Tool Count5/5

    8 tools is well-scoped for a Zabbix operations server, covering health checks, problem listing/acknowledgment, host inventory, item values, and maintenance windows without excessive overlap or bloat.

    Completeness3/5

    Core read and write operations are present (list problems, ack, create maintenance, list maintenance), but there is no delete_maintenance to reverse set_maintenance, nor an unacknowledge_problem, leaving lifecycle gaps in the maintenance and acknowledgment workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources