DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
uvx kafka-dataops-mcp
MCP client config
{
"mcpServers": {
"kafka-dataops": {
"command": "uvx",
"args": [
"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.
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 descriptionsThe diagnosis logic is not generic — it's based on actual operational experience:
pip install kafka-dataops-mcp
Add to your .mcp.json:
{
"mcpServers": {
"kafka": {
"command": "kafka-dataops-mcp",
"env": {
"KAFKA_BOOTSTRAP_SERVERS": "localhost:9092"
}
}
}
}
| Variable | Default | Description |
|---|---|---|
KAFKA_BOOTSTRAP_SERVERS | localhost:9092 | Kafka bootstrap servers |
KAFKA_COMMAND_TIMEOUT | 10 | Command timeout in seconds |
MIT