mcp-kafka
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KAFKA_SSL | No | Set to 'true' to enable TLS for the Kafka connection. | |
| KAFKA_MODE | No | Access mode: read-only, read-write, or admin. Defaults to read-only. | read-only |
| KAFKA_BROKERS | Yes | Comma-separated list of Kafka broker addresses. Example: broker1:9092,broker2:9092 | |
| KAFKA_DRY_RUN | No | If 'true', write and admin tools validate + log intent without making cluster changes. Defaults to 'false'. | false |
| KAFKA_AUDIT_LOG | No | If 'true', emits a JSON audit log line to stderr per guarded operation. Defaults to 'true'. | true |
| KAFKA_ALLOW_DELETE | No | Set to 'true' to enable delete_topic and delete_consumer_group (requires admin mode). Defaults to 'false'. | false |
| KAFKA_SASL_PASSWORD | No | Password for SASL authentication. | |
| KAFKA_SASL_USERNAME | No | Username for SASL authentication. | |
| KAFKA_SASL_MECHANISM | No | SASL mechanism: PLAIN, SCRAM-SHA-256, or SCRAM-SHA-512. | |
| KAFKA_TOPIC_ALLOWLIST | No | Comma-separated list of allowed topics. When set, operations on other topics are refused. | |
| KAFKA_PROTECTED_TOPICS | No | Comma-separated list of additional topics that are read-only forever. | |
| KAFKA_PROTECT_INTERNAL_TOPICS | No | Set to 'false' to allow mutation of topics starting with an underscore. Defaults to 'true'. | true |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cluster_infoA | Describe the Kafka cluster: brokers, controller, and cluster id. |
| list_topicsA | List topic names. Topics outside the allowlist are filtered out. |
| describe_topicA | Partitions, replicas, in-sync replicas, and non-default configs for a topic. |
| topic_offsetsA | Earliest and latest offsets per partition for a topic (message backlog view). |
| list_consumer_groupsA | List consumer groups and their protocol types. |
| describe_consumer_groupA | Describe a consumer group's state and compute per-partition and total lag across its topics. |
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 6 tools
Each tool targets a distinct aspect: cluster metadata, topic names, topic configuration, offsets, consumer group listing, and consumer group lag. The only mild overlap is describe_topic vs topic_offsets, but their descriptions clearly separate configuration/replica details from offset ranges.
Most tools follow list_* or describe_* verb patterns, which is predictable and clear. However, topic_offsets and cluster_info use noun-style names rather than verb_noun, creating minor inconsistency.
Six tools is well-scoped for a Kafka inspection and monitoring server. Each tool covers a meaningful read-only capability without redundancy or bloat.
The set provides solid read-only coverage: cluster info, topic discovery/description, offsets, consumer groups, and lag. It lacks administrative operations like creating/deleting topics or message produce/consume, but those seem outside the likely inspection-focused purpose.