
Mcp Kafka
Let your coding agent inspect Kafka topics, lag, and sample messages without leaving the editor during incident triage or pipeline debugging.
Overview
io.github.infoinlet-marketplace/mcp-kafka is an Operate-phase MCP server that gives AI agents read-only Kafka topic, offset, consumer-group, message-peek, and health visibility.
What is this MCP server?
- Read-only access to topics, partition offsets, and consumer group lag
- Peek messages for debugging without producing or deleting data
- Cluster health checks suited to agent-driven incident summaries
- Stdio MCP package @infoinlet/mcp-kafka v0.1.1 from infoinlet marketplace
- Fits agents that need Kafka context alongside logs and traces
- npm package @infoinlet/mcp-kafka at version 0.1.1
- stdio transport per MCP server schema 2025-12-11
- Read-only surface: topics, offsets, consumer groups, peek, health
What problem does it solve?
Debugging Kafka from chat usually means copy-pasting CLI output or risking write commands when you only need to see what the cluster is doing.
Who is it for?
Indie builders or tiny teams who operate Kafka-backed services and want agent-assisted triage without shell access on every machine.
Skip if: Greenfield projects with no Kafka yet, or teams that need topic creation, ACL changes, or message publishing from the agent.
What do I get? / Deliverables
After you register the stdio server, your agent can cite live topic layout, lag, and sample payloads while you stay in a safe read-only posture.
- Agent-visible topic and partition metadata
- Lag and consumer-group summaries with optional message peeks
- Health-oriented answers grounded in live cluster reads
Recommended MCP Servers
Journey fit
Event buses are diagnosed after deploy when consumers stall or partitions misbehave—canonical shelf is production operations, not greenfield coding. Offsets, consumer groups, peek, and cluster health are observability workflows that match monitoring rather than generic backend build.
How it compares
Read-only Kafka MCP bridge, not a stream-processing framework or a full Kafdrop UI.
Common Questions / FAQ
Who is mcp-kafka for?
Solo and indie builders using Claude Code, Cursor, or Codex who already run Kafka and need safe, agent-readable cluster inspection during operations.
When should I use mcp-kafka?
Use it during Operate when consumer lag, partition skew, or mystery messages need quick reads before you change application code or redeploy.
How do I add mcp-kafka to my agent?
Install @infoinlet/mcp-kafka from npm, point your MCP client at the stdio server entry from the infoinlet marketplace manifest, and supply broker connection settings your host expects.