kafka-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_topicsB | List all topics in the Kafka cluster. |
| describe_topicC | Describe a Kafka topic. |
| create_topicC | Create a new Kafka topic. |
| produce_messageC | Produce a message to a Kafka topic. |
| consume_messagesC | Consume messages from a Kafka topic. |
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 5 tools
Each tool targets a distinct Kafka resource action: listing, describing, creating topics, plus producing and consuming messages. The two message tools (produce_message, consume_messages) are clearly opposite operations, so little confusion. Minor overlap between list_topics and describe_topic could cause slight ambiguity but descriptions are clear enough.
All tools follow a consistent verb_noun pattern: list_topics, describe_topic, create_topic, produce_message, consume_messages. The naming convention is uniform with no mixture of styles or vague verbs.
Five tools is a reasonable, well-scoped count for a Kafka server covering core topic management and messaging. It's on the leaner side but every tool earns its place for the apparent purpose.
The surface covers topic lifecycle (list, describe, create) and basic messaging (produce, consume). Missing obvious operations like delete_topic, update_topic (partitions/replication), and consumer group management, which are common Kafka workflows an agent would expect.