Skip to main content
Glama
fredriksknese

mcp-centreon

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-centreon

No user-submitted related servers found.

    Related Servers

    • thruk-mcp

      k9fr4n
      A
      license
      C
      quality
      B
      maintenance
      Enables natural language interaction with Thruk monitoring systems, allowing users to query hosts/services, schedule downtimes, acknowledge problems, and more via MCP-compatible clients.
      65
      1
      MIT
    • Sentio MCP Server by sentioxyz

      Sentio MCP Serverofficial

      sentioxyz
      A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server integrates with Sentio's API services to provide web, data, price, processor, and alerts tools, enabling users to manage and query Sentio resources through natural language.
      60 npm
      1
      Apache 2.0
    • Drumbeats MCP by drumbeats-io

      Drumbeats MCPofficial

      drumbeats-io
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.
      16
      13 npm
      2
      Apache 2.0

    • server-monitor-mcp

      Call123X
      F
      license
      Not graded
      quality
      B
      maintenance
      Server Monitor MCP is a Linux server inspection service with web backend and MCP interface. It allows you to manage SSH hosts and query server metrics via natural language.
      -

    • mcp-uptime-kuma

      DavidFuchs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.
      31
      209 npm
      50
      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

    A3.7/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (list vs get, host vs service, acknowledge vs downtime, metrics discovery vs data retrieval). No two tools appear to do the same thing, and action verbs clearly differentiate between read and write operations.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_, list_, acknowledge_, add_downtime_), using snake_case throughout. The pattern is predictable and makes it easy to guess the purpose of a tool from its name.

    Tool Count4/5

    At 17 tools, the server is slightly above the ideal 3-15 range but each tool serves a distinct purpose within the monitoring domain. The count feels justified, covering hosts, services, groups, events, acknowledgements, downtimes, metrics, and pollers, though it is a bit heavy.

    Completeness4/5

    The tool surface covers the core monitoring lifecycle: viewing hosts/services, acknowledging problems, scheduling downtimes, and fetching performance metrics. Missing operations like canceling a downtime or listing acknowledgements in detail are minor gaps that agents could work around, but the set is largely complete for common monitoring tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources