MCP servers · aguantar

kafka-dataops-mcp: Kafka consumer lag and broker health monitoring

An MCP server for Kafka DataOps that diagnoses consumer lag and monitors broker health.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The server provides four tools: kafka_consumer_lag, which reports consumer group lag with incident-pattern diagnosis; kafka_topic_info, which shows topic details with ISR and replication health checks; kafka_broker_status, which reports brokers, the controller and under-replicated partitions; and kafka_list_topics, which lists topics with built-in descriptions.

The diagnosis logic is based on operational experience with a CDC pipeline rather than generic rules. A consumer group with no active members and growing lag is flagged as a likely Flink job failure, drawn from a 46-hour outage caused by a MySQL DELETE, a Debezium tombstone and a Flink NPE. It warns that resetting a consumer group alone is insufficient for Flink because checkpoints must be deleted first. It detects missing brokers under ClusterIdMismatch and suggests a Docker volume conflict as the root cause, and it treats an ISR below min.insync.replicas as a critical write-failure condition.

It is intended for teams running Kafka-based data pipelines who want lag and broker diagnostics within Claude Code. It is registered in a .mcp.json file. The environment variable KAFKA_BOOTSTRAP_SERVERS sets the bootstrap servers, with a default of localhost:9092, and KAFKA_COMMAND_TIMEOUT sets the command timeout in seconds, with a default of 10.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Aguantar/kafka-dataops-mcp

    DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
modelcontextprotocol

MCP reference servers

Seven small example servers maintained by the Model Context Protocol project: files, Git, web fetching, memory, time, step-by-step thinking and a test server.

92K GitHub starsSoftware development
Updated 18 Nov 2026
MCP servers
firecrawl

Firecrawl MCP Server (web search and scraping)

Firecrawl's MCP server that lets an AI assistant search the web, turn pages and PDFs into clean Markdown, crawl sites and interact with dynamic pages.

7.8K GitHub starsWeb, search & browserProductivity & automation
Updated 17 Nov 2026
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
docker

Docker Hub MCP Server

Docker's MCP server that helps an AI assistant find and compare container images on Docker Hub and, with your token, manage your own repositories and tags.

171 GitHub starsCloud & DevOpsSoftware development
Updated 13 Nov 2026
kafka-dataops-mcp: Kafka consumer lag and broker health monitoring | AI Gate Discover