DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring
DataOps Kafka MCP server with consumer lag diagnosis and broker monitoring
Is it safe?
No known CVEs for kafka-dataops-mcp.
No authentication — any process on your machine can connect to this server.
License not specified.
Last scanned 0 days ago.
Is it maintained?
Last commit 15 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
How much context will it use?
4 tools. Estimated ~200 tokens of your context window (0.1% of 200K).
What if it doesn't work?
Common issues: JSON syntax errors in config, Python version mismatch. Setup guide covers troubleshooting.
{
"mcpServers": {
"kafka": {
"env": {
"KAFKA_BOOTSTRAP_SERVERS": "localhost:9092"
},
"command": "kafka-dataops-mcp"
}
}
}Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx kafka-dataops-mcp 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
kafka_consumer_lagConsumer group lag with incident-pattern diagnosis
kafka_topic_infoTopic details with ISR/replication health checks
kafka_broker_statusCluster health: brokers, controller, under-replicated partitions
kafka_list_topicsTopic catalog with built-in descriptions
Last scanned 1h ago
No known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.