I'm going to show you how to go from "Claude has no idea my Kafka cluster exists" to "Claude lists topics, consumes messages, and inspects consumer groups" in under five minutes. No Python scripts. No REST wrappers. No Docker Compose stack. One binary, one YAML file.
Here's what we're building:
Claude Desktop ←→ MCP (stdio) ←→ KafkaMCP ←→ Your Kafka Cluster
Last month I watched a senior data engineer at a Series C fintech spend eleven days building a pipeline so their incident response agent could read from a single Kafka topic.
Eleven days. One topic.
She wrote a Python consumer that subscribed to orders.dlq, deserialized Avro messages using a hand-managed schema cache, dumped the results into a REST endpoint, wrote an MCP tool definition that called the REST endpoint, added error handling for when the consumer fell behind, and then spent two more days debugging a memory leak in the consumer process. When she was done, the agent could sample dead-letter queue messages. Read-only. No schema awareness. No consumer group inspection. And when the team wanted the agent to also read from payments.failed, the whole process started over.
This is the default experience for every team that wants AI agents to interact with Kafka. It's a hidden tax that compounds with every new topic and every new agent, and it's entirely unnecessary.