Skip to main content
Glama
prenzio

Rudow MCP Server

by prenzio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Rudow MCP Server

No user-submitted related servers found.

    Related Servers

    • Datadog MCP Server

      TANTIOPE
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to access full Datadog observability, including log search, APM trace filtering, smart sampling, and cross-correlation between logs, traces, and metrics.
      23
      965 npm
      6
      Apache 2.0

    • datadog-mcp

      Vicks9070
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and manage Datadog observability data including metrics, logs, traces, and monitors through natural language. Supports read-only operations by default for security.
      MIT

    • k8s-troubleshoot-mcp

      NanaGyamfiPrempeh30
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to diagnose Kubernetes clusters through read-only MCP tools, such as inspecting pod status, logs, events, nodes, deployments, and HPA metrics via natural language queries.
      MIT

    • Kibana MCP Server

      jerrelblankenship
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Kibana dashboards, visualizations, and Elasticsearch data through read-only resources and executable tools for searching logs, exporting dashboards, and querying data.
      7
      15 npm
      3
      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

    B3.4/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools have distinct purposes, but metrics_summary and metrics_overview clearly overlap — summary is described as a superset of the overview content, so an agent could easily pick the wrong one. The six-tool metrics_* family (summary/overview/trends/distributions/routes/levels) also has blurry boundaries between 'health snapshot' and 'computed health overview.'

    Naming Consistency4/5

    All snake_case, which is good, but verb conventions vary: list_/get_/query_/fetch_/aggregate_ for retrieval plus bare-noun-prefixed metrics_* and semantic_search/route_drilldown. Still readable and predictable enough to map names to intent.

    Tool Count3/5

    17 tools for an observability/logging server is on the heavy side, and the metrics area is split into six separate tools where a composite or parameterized tool could reduce surface area. Individually each earns some place, but the metrics fan-out feels like over-decomposition.

    Completeness4/5

    Coverage is broad for the domain: logs (latest, sampled, aggregate, semantic, contextual), metrics, incidents, route drilldown, ingest failures, SDK onboarding, and project listing. The main gap is incident lifecycle actions (acknowledge/resolve) and any write/config operations, but core read workflows are well covered.

    Resources