Skip to main content
Glama
openITCOCKPIT

openITCOCKPIT MCP Server

Official
by openITCOCKPIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to openITCOCKPIT MCP Server

  • Grafana by grafana

    Grafanaofficial

    grafana
    A
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server for Grafana. This provides access to your Grafana instance and the surrounding ecosystem.
    3,521
    Apache 2.0

Related Servers

  • GLPI MCP Server v2

    Luizcc87
    A
    license
    C
    quality
    A
    maintenance
    MCP server for GLPI integration, providing tools for ITIL management (tickets, problems, changes, knowledge base, stats, assets, and administration) via the GLPI API.
    30
    MIT

  • health-monitor-mcp

    oaslananka
    A
    license
    A
    quality
    B
    maintenance
    MCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
    22
    399 npm
    2
    MIT

  • Overwatch MCP

    malindarathnayake
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that enables querying logs and metrics from Graylog, Prometheus, and InfluxDB 2.x. It provides tools for executing Lucene log searches, PromQL queries, and Flux queries directly within MCP-compatible clients.
    MIT
  • HostTracker by HostTracker

    HostTrackerofficial

    HostTracker
    A
    license
    A
    quality
    B
    maintenance
    Official HostTracker MCP server: run uptime, SSL, DNS, blacklist and page-speed checks from 300+ global locations, and manage monitors, alerts, incidents and status pages. The repo packages the hosted endpoint as a stdio bridge (Dockerfile).
    65
    1
    MIT

  • keepitalive-mcp

    salab3rt
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server for KEEPitALIVE monitoring, enabling AI agents to read and manage monitors, incidents, triggers, and notification routing via the v1 API, with scope-based tool filtering and safety modes.
    7 npm
    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.2/5.0

Scored across 20 tools

Disambiguation5/5

Each tool targets a distinct aspect of monitoring—from finding hosts/services to explaining notifications, forecasting metrics, and investigating problems. There is minimal overlap; even similar tools like get_host_health and get_problem_overview serve different scopes (single object vs. global overview).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_, find_, list_, explain_, forecast_, investigate_). No mixed conventions or vague verbs; compound names like get_allowed_elements_for_container are still predictable.

Tool Count4/5

With 20 tools, the count is slightly above the typical 3-15 range, but it is justified for a comprehensive monitoring server covering search, health, configuration, reporting, and updates. The tools are well-scoped and not redundant, though a few could be merged (e.g., find_hosts and find_services are similar in style).

Completeness4/5

The tool surface covers the core monitoring lifecycle—discovering, diagnosing, and reporting—but lacks write operations (create/update/delete) for hosts or services, despite get_allowed_elements_for_container referencing create calls. This is a notable gap for full configuration management, but for read-only analysis it is sufficient.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources