kafka-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOTSTRAP_SERVER | No | Kafka bootstrap server(s) to connect to. | localhost: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 |
|---|---|
| List all non internal topics with their partition number and replication factorC | List Kafka topics with partition count and replication factor. |
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 1 tool
With only one tool, there is no risk of confusion between tools. The single tool's purpose is clear and unambiguous.
There is only one tool, so no inconsistency exists. However, its name is a full sentence rather than a concise verb_noun pattern, which is atypical for MCP tool naming.
A single tool for a Kafka server is insufficient. Kafka has a rich API requiring multiple operations; one tool suggests minimal functionality.
Only listing topics is available. Missing essential operations like creating, deleting, producing/consuming messages, managing consumer groups, etc. The tool surface is severely incomplete for a Kafka server.