kafka-sentinel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAFKA_BOOTSTRAP | No | The Kafka bootstrap servers to connect to (e.g., broker1:9092,broker2:9092) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cluster_healthB | Broker count, controller, and under-replicated / offline partition summary. |
| consumer_lagB | Per-partition lag for a consumer group on a topic: committed offset vs log-end offset. committed = -1 means no offset stored. |
| topic_auditA | Replication and durability config audit for a topic. Flags settings that violate mission-critical best practice. |
| partition_stateC | Leader/ISR state per partition, plus leader skew across brokers. |
| replay_readinessC | Can this group still replay everything since its committed offsets, or has retention already deleted part of the gap? |
| list_topicsA | 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. |
| list_consumer_groupsA | List all consumer group IDs on the cluster with their state. Use this first if you don't already know a group name. |
| incident_snapshotA | One-call bundle: cluster health + lag + audit + partition state + replay readiness. Timestamped for postmortems. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target clearly distinct concerns: health, lag, audit, partition state, replay readiness. However, cluster_health and incident_snapshot overlap in scope since the snapshot bundles the health data, and topic_audit vs partition_state both touch replication/durability concerns at the partition level, creating minor confusion.
Tool names use a consistent noun-based pattern (adjective_noun) like cluster_health, consumer_lag, topic_audit, partition_state — not strictly verb_noun but internally consistent. Minor deviation is having two 'list_' verbs mixed in with the descriptive noun pattern, though this reads as intentional since they are discovery operations.
Eight tools for a Kafka operational monitoring server is a reasonable, focused scope. Each tool maps to a distinct operational concern with no obvious redundancy, and the incident_snapshot aggregation is a valuable convenience rather than bloat.
The surface covers the core read-only operational concerns an agent would need: discovery (list_topics, list_consumer_groups), health, lag, audit, partition state, and replay/retention analysis. Minor gaps exist — there's no consumer group reset or topic config mutation (read-only by design), and no offset trimming tool, but for an operational sentinel these are reasonable absences.