Skip to main content
Glama
sanjay-amu

kafka-sentinel-mcp

by sanjay-amu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to kafka-sentinel-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-kafka-observer

      Rushi264
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents real-time observability into Apache Kafka clusters, enabling natural language queries for broker health, consumer lag, and diagnostics.
      MIT

    • kafka-mcp

      wklee610
      A
      license
      B
      quality
      B
      maintenance
      MCP server for Apache Kafka that allows LLM agents to inspect topics, consumer groups, and safely manage offsets (reset, rewind).
      19
      13
      Apache 2.0

    • platform-mcp-server

      kamroy
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.
      6
      -

    • platform-mcp

      deBilla
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that enables AI agents to act as GCP platform engineers, allowing them to investigate incidents, take inventory, and find cost-optimization opportunities in Google Cloud projects without mutating any infrastructure.
      16
      2
      MIT

    • k8s-readonly-mcp

      ziyuyu23
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for inspecting Kubernetes clusters, allowing LLMs to list resources, describe pods, and read logs without mutation.
      5
      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.
      -
    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 8 tools

    Disambiguation4/5

    Most tools target clearly distinct concerns: health, lag, audit, partition state, replay readiness. However, cluster_health and incident_snapshot overlap in scope since the snapshot bundles the health data, and topic_audit vs partition_state both touch replication/durability concerns at the partition level, creating minor confusion.

    Naming Consistency4/5

    Tool names use a consistent noun-based pattern (adjective_noun) like cluster_health, consumer_lag, topic_audit, partition_state — not strictly verb_noun but internally consistent. Minor deviation is having two 'list_' verbs mixed in with the descriptive noun pattern, though this reads as intentional since they are discovery operations.

    Tool Count4/5

    Eight tools for a Kafka operational monitoring server is a reasonable, focused scope. Each tool maps to a distinct operational concern with no obvious redundancy, and the incident_snapshot aggregation is a valuable convenience rather than bloat.

    Completeness4/5

    The surface covers the core read-only operational concerns an agent would need: discovery (list_topics, list_consumer_groups), health, lag, audit, partition state, and replay/retention analysis. Minor gaps exist — there's no consumer group reset or topic config mutation (read-only by design), and no offset trimming tool, but for an operational sentinel these are reasonable absences.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources