io.github.Aguantar/kafka-dataops-mcp
DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring
What can you do with io.github.Aguantar/kafka-dataops-mcp?
kafka_consumer_lag— Consumer group lag with incident-pattern diagnosiskafka_topic_info— Topic details with ISR/replication health checkskafka_broker_status— Cluster health: brokers, controller, under-replicated partitionskafka_list_topics— Topic catalog with built-in descriptions
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
kafka-dataops-mcpclaude mcp add kafka-dataops-mcp -e 'KAFKA_BOOTSTRAP_SERVERS=<KAFKA_BOOTSTRAP_SERVERS>' -- uvx kafka-dataops-mcp==0.1.0
{
"mcpServers": {
"kafka-dataops-mcp": {
"command": "uvx",
"args": [
"kafka-dataops-mcp==0.1.0"
],
"env": {
"KAFKA_BOOTSTRAP_SERVERS": "<KAFKA_BOOTSTRAP_SERVERS>"
}
}
}
}
Environment variables
KAFKA_BOOTSTRAP_SERVERSKafka bootstrap servers
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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 diagnosiskafka_topic_info— Topic details with ISR/replication health checkskafka_broker_status— Cluster health: brokers, controller, under-replicated partitionskafka_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
| Variable | Default | Description |
|---|---|---|
KAFKA_BOOTSTRAP_SERVERS | localhost:9092 | Kafka bootstrap servers |
KAFKA_COMMAND_TIMEOUT | 10 | Command timeout in seconds |
License
MIT
Frequently asked questions
What is io.github.Aguantar/kafka-dataops-mcp?
DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring
How do I install io.github.Aguantar/kafka-dataops-mcp?
It runs on your machine. In Claude Code: claude mcp add kafka-dataops-mcp -e 'KAFKA_BOOTSTRAP_SERVERS=<KAFKA_BOOTSTRAP_SERVERS>' -- uvx kafka-dataops-mcp==0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.Aguantar/kafka-dataops-mcp need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.Aguantar/kafka-dataops-mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.Aguantar/kafka-dataops-mcp?
It is published by Aguantar. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.