mcpField
K
kafka-dataops-mcp

kafka-dataops-mcp

Local
github.com/AguantarCloud & Infra0Updated 4w ago
Repository

About kafka-dataops-mcp

kafka-dataops-mcp is an MCP server for Kafka operations teams, covering consumer lag diagnosis and broker and topic health. Its diagnosis rules draw on CDC pipeline incidents, including Flink failures and replication issues.

Key features

  1. 01Consumer lag and incident diagnosis
  2. 02Topic details and replication health
  3. 03Broker and cluster status checks
  4. 04Topic catalog with descriptions

Use cases

  1. 01Investigating rising consumer lag
  2. 02Checking broker and controller health
  3. 03Finding topics with replication issues

MCP support

Exposes Kafka consumer lag, topic, broker-status, and topic-listing tools to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "aguantar-kafka-dataops": {
      "command": "uvx",
      "args": [
        "kafka-dataops-mcp"
      ],
      "env": {
        "KAFKA_BOOTSTRAP_SERVERS": "<KAFKA_BOOTSTRAP_SERVERS>"
      }
    }
  }
}
Run commanduvx kafka-dataops-mcp
Environment variables to set
KAFKA_BOOTSTRAP_SERVERSKafka bootstrap servers

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypikafka-dataops-mcp0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

kafka-dataops-mcp

mcp-name: io.github.Aguantar/kafka-dataops-mcp

A DataOps-focused Kafka MCP server with consumer lag diagnosis and broker health monitoring. Diagnosis logic is based on actual CDC pipeline operational experience.

Features

  • kafka_consumer_lag — Consumer group lag with incident-pattern diagnosis
  • kafka_topic_info — Topic details with ISR/replication health checks
  • kafka_broker_status — Cluster health: brokers, controller, under-replicated partitions
  • kafka_list_topics — Topic catalog with built-in descriptions
Diagnosis based on real incidents

The diagnosis logic is not generic — it's based on actual operational experience:

  • Flink crash detection: "no active members" + growing lag = likely Flink Job failure (based on a 46-hour outage caused by MySQL DELETE → Debezium tombstone → Flink NPE)
  • Checkpoint vs consumer group: warns that Kafka consumer group reset alone is insufficient for Flink — checkpoints must be deleted first
  • ClusterIdMismatch: detects missing brokers and suggests Docker volume conflict as root cause
  • ISR monitoring: ISR < min.insync.replicas = write failures (critical)

Installation

pip install kafka-dataops-mcp

Usage with Claude Code

Add to your .mcp.json:

{
  "mcpServers": {
    "kafka": {
      "command": "kafka-dataops-mcp",
      "env": {
        "KAFKA_BOOTSTRAP_SERVERS": "localhost:9092"
      }
    }
  }
}

Environment Variables

VariableDefaultDescription
KAFKA_BOOTSTRAP_SERVERSlocalhost:9092Kafka bootstrap servers
KAFKA_COMMAND_TIMEOUT10Command timeout in seconds

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.