Server data from the Official MCP Registry
Read-only Kafka observability MCP server: cluster health, consumer lag, and replay-readiness.
Read-only Kafka observability MCP server: cluster health, consumer lag, and replay-readiness.
kafka-sentinel-mcp is a well-designed read-only Kafka observability MCP server with strong security-first architecture. The codebase enforces immutability by design (no admin/producer APIs imported), handles credentials safely via environment variables with no logging of secrets, and implements proper audit logging. Minor code quality observations exist but do not impact security posture. Permissions align appropriately with the server's stated read-only observability purpose. Supply chain analysis found 5 known vulnerabilities in dependencies (0 critical, 5 high severity). Package verification found 1 issue.
6 files analyzed · 10 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: KAFKA_BOOTSTRAP
Environment variable: KAFKA_SECURITY_PROTOCOL
Environment variable: KAFKA_SASL_MECHANISM
Environment variable: KAFKA_SASL_USERNAME
Environment variable: KAFKA_SASL_PASSWORD
Environment variable: KAFKA_SSL_CA_LOCATION
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-sanjay-amu-kafka-sentinel-mcp": {
"env": {
"KAFKA_BOOTSTRAP": "your-kafka-bootstrap-here",
"KAFKA_SASL_PASSWORD": "your-kafka-sasl-password-here",
"KAFKA_SASL_USERNAME": "your-kafka-sasl-username-here",
"KAFKA_SASL_MECHANISM": "your-kafka-sasl-mechanism-here",
"KAFKA_SSL_CA_LOCATION": "your-kafka-ssl-ca-location-here",
"KAFKA_SECURITY_PROTOCOL": "your-kafka-security-protocol-here"
},
"args": [
"kafka-sentinel-mcp"
],
"command": "uvx"
}
}
}From the project's GitHub README.
Give AI agents safe, read-only eyes on your Kafka clusters.
An MCP (Model Context Protocol) server that exposes Kafka cluster health, consumer lag, partition state, and replay-readiness as structured tools — so LLM agents (Claude, or any MCP client) can diagnose streaming incidents without ever being able to break anything.
Built by an engineer who spent a decade running Kafka-based financial messaging at 99.999% availability, and got tired of every "AI + Kafka" demo assuming write access to production.
When a consumer group stalls at 3 a.m., the questions are always the same: Is it lag? A stuck partition? A rebalance storm? An offset reset gone wrong? These are pattern-matching questions — exactly what LLM agents are good at — but no operator will hand an agent admin rights on a production cluster.
kafka-sentinel-mcp draws a hard line: every tool is read-only by design, enforced at the client-config level (no admin operations are even imported). The agent can observe, correlate, and recommend; a human executes.
| Tool | What it returns |
|---|---|
cluster_health | Broker count, controller status, under-replicated / offline partition counts |
consumer_lag | Per-group, per-topic, per-partition lag with committed vs end offsets |
topic_audit | Replication factor, min.insync.replicas, retention, and flags configs that violate durability best practice |
partition_state | Leaders, ISR shrinkage, skew across brokers |
replay_readiness | For a group + topic: earliest available offsets vs committed, i.e., "can we still replay what we missed?" |
incident_snapshot | One-call bundle of all the above, timestamped — designed for pasting into a postmortem |
pip install kafka-sentinel-mcp # (or: uv tool install)
# Run against your cluster (read-only credentials!)
KAFKA_BOOTSTRAP=localhost:9092 kafka-sentinel-mcp
Add to Claude Desktop / any MCP client:
{
"mcpServers": {
"kafka-sentinel": {
"command": "kafka-sentinel-mcp",
"env": { "KAFKA_BOOTSTRAP": "broker1:9092,broker2:9092" }
}
}
}
Then ask your agent: "Why is the payments-consumer group falling behind, and can we still replay from where it stalled?"
Describe/Read ACLs only — the server degrades gracefully and reports what it can't see.Early. See ROADMAP.md. Issues and PRs welcome — especially war stories about what you wish an agent could have told you during an incident.
MIT
Be the first to review this server!
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption