Skip to main content
Glama
Aguantar

kafka-dataops-mcp

by Aguantar

Related Servers

Alternatives to kafka-dataops-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      B
      maintenance
      Read-only MCP server for Kafka cluster health, consumer lag, partition state, and replay-readiness, enabling AI agents to diagnose streaming incidents without write access.
      8
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage and monitor Apache Kafka clusters through natural language, providing real-time operations, health monitoring, consumer lag analysis, and temporal trend detection for intelligent cluster management.
      -
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      A comprehensive Model Context Protocol (MCP) server for Grafana, Prometheus, Kafka UI, and Datadog. Features a secure "Bring Your Own Key" (BYOK) architecture where credentials stay local. Provides tools for metrics querying, dashboard inspection, Kafka lag monitoring, and unified health checks.
      23
      10
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Kafka clusters to manage topics, monitor consumer groups, and stream messages. It provides a comprehensive suite of tools for broker metadata inspection and local Kafka user management.
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Kafka operation: cluster health, consumer lag, topic listing, and topic details. No functional overlap.

    Naming Consistency4/5

    All tools start with 'kafka_' but mix verb-noun ('list_topics') and noun phrases ('broker_status'). Still predictable and readable.

    Tool Count4/5

    Four tools is reasonable for a monitoring-focused server. Could expand with more actions but not too sparse.

    Completeness3/5

    Covers key diagnostic needs (health, lag, topic details) but lacks topic creation or consumer group management. Adequate for observability.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues