MCP.Market

Kafka Sentinel MCP server

by sanjay-amu·io.github.sanjay-amu/kafka-sentinel-mcp·v0.1.2·3 stars
No reviews yet

Read-only Kafka observability MCP server: cluster health, consumer lag, and replay-readiness.

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
Growing

3 stars24 downloads/wk

Reviews

Write one

Nobody has reviewed Kafka Sentinel yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Kafka Sentinel tools (8)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cluster_health

    Broker count, controller, and under-replicated / offline partition summary.

  • consumer_lag

    Per-partition lag for a consumer group on a topic: committed offset vs log-end offset. committed = -1 means no offset stored.

  • incident_snapshot

    One-call bundle: cluster health + lag + audit + partition state + replay readiness. Timestamped for postmortems.

  • list_consumer_groups

    List all consumer group IDs on the cluster with their state. Use this first if you don't already know a group name.

  • list_topics

    List all non-internal topics with partition count and replication factor. Use this first if you don't already know a topic name — every other tool needs one.

  • partition_state

    Leader/ISR state per partition, plus leader skew across brokers.

  • replay_readiness

    Can this group still replay everything since its committed offsets, or has retention already deleted part of the gap?

  • topic_audit

    Replication and durability config audit for a topic. Flags settings that violate mission-critical best practice.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 56 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Kafka Sentinel compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
24
more than 10% of 12,191 servers with a package

What its tools let an agent do: 8 read

Install Kafka Sentinel in Claude Code, Cursor or VS Code

claude mcp add kafka-sentinel-mcp -- uvx kafka-sentinel-mcp
Add to Cursor

What the publisher says

From the Kafka Sentinel repository's README, as published. We do not edit it. Read it on GitHub

kafka-sentinel-mcp

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.

Why this exists

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.

Tools

Quick start

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?"

Security posture

  • Read-only by construction: no produce, no topic/config mutation, no offset commits, no ACL ops. The mutation APIs are never imported, and a test in CI greps the server source on every run to keep it that way.
  • The observer consumer runs with enable.auto.commit=False and never commits — verified against a real broker, not just asserted.
  • Supports SASL/SSL; credentials are read from the environment only and never logged.
  • Every tool call is logged with its parameters for audit.
  • Least privilege: run with a principal that has only Describe on the cluster and topics, and Describe on consumer groups. When an ACL denies an operation the tool returns a structured result rather than a stack trace:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Kafka Sentinel: common questions

Is Kafka Sentinel MCP server safe?
Mostly: it is graded B (78/100). Read the Kafka Sentinel safety report
How do I install Kafka Sentinel?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Kafka Sentinel need an API key?
Yes. The registry entry asks for KAFKA_SASL_PASSWORD.
Is Kafka Sentinel maintained?
The last commit was 96 days ago (2026-07-31). The latest release is v0.1.2.
How does Kafka Sentinel compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.