io.github.dockndevai/mcp-kafka
Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.
What can you do with io.github.dockndevai/mcp-kafka?
- Monitoring — cluster/broker info, topic metadata and offsets, consumer groups, and per-partition + total consumer lag.
- Management — create topics, add partitions, alter topic configs, reset group offsets; delete topics/groups (admin).
- Access modes —
read-only→read-write→admin, layered so a mode never exposes tools above its level. - Security flags — topic allowlist, protected/internal topics, delete gating, dry-run, and JSON audit logging (see below).
- Auth — plaintext, TLS, and SASL (PLAIN / SCRAM-SHA-256 / SCRAM-SHA-512).
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@dockndevai/mcp-kafkaclaude mcp add mcp-kafka -e 'KAFKA_BROKERS=<KAFKA_BROKERS>' -e 'KAFKA_MODE=<KAFKA_MODE>' -- npx -y @dockndevai/mcp-kafka@0.3.3
{
"mcpServers": {
"mcp-kafka": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-kafka@0.3.3"
],
"env": {
"KAFKA_BROKERS": "<KAFKA_BROKERS>",
"KAFKA_MODE": "<KAFKA_MODE>"
}
}
}
}
Environment variables
KAFKA_BROKERSrequired Comma-separated broker list (host:port).KAFKA_MODEAccess mode: read-only | read-write | admin.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-kafka
A Model Context Protocol server for Apache Kafka. It lets an MCP-capable client (Claude Desktop, Claude Code, etc.) monitor and manage Kafka clusters — topics, partitions, configs, and consumer groups (including lag) — with behaviour controlled entirely by flags.
Safe by default: it starts read-only, can be scoped to an allowlist of topics, protects internal/critical topics from mutation, and gates destructive operations behind an explicit opt-in.
Features
- Monitoring — cluster/broker info, topic metadata and offsets, consumer groups, and per-partition + total consumer lag.
- Management — create topics, add partitions, alter topic configs, reset group offsets; delete topics/groups (admin).
- Access modes —
read-only→read-write→admin, layered so a mode never exposes tools above its level. - Security flags — topic allowlist, protected/internal topics, delete gating, dry-run, and JSON audit logging (see below).
- Auth — plaintext, TLS, and SASL (PLAIN / SCRAM-SHA-256 / SCRAM-SHA-512).
Security model
| Concern | Flag | Default | Effect |
|---|---|---|---|
| What can the server do? | KAFKA_MODE | read-only | read-only exposes only monitoring; read-write adds management; admin adds deletes. Tools above the mode are never registered. |
| Which topics are in scope? | KAFKA_TOPIC_ALLOWLIST | (all) | When set, operations on other topics are refused. |
| Protect internal topics | KAFKA_PROTECT_INTERNAL_TOPICS | true | Topics starting with _ can be read but never mutated. |
| Protect specific topics | KAFKA_PROTECTED_TOPICS | (none) | Additional read-only-forever topics. |
| Can it delete? | KAFKA_ALLOW_DELETE | false | delete_topic / delete_consumer_group need this and admin mode. |
| Preview without touching the cluster | KAFKA_DRY_RUN | false | Write/admin tools validate + log intent, then return. |
| Audit trail | KAFKA_AUDIT_LOG | true | Emits a JSON line to stderr per guarded operation. |
| Interactive confirmation | (automatic) | — | Destructive & high-impact actions prompt the human to approve via MCP elicitation before running; clients without elicitation fall back to the *_ALLOW_* gate. |
Tools
Read (read-only+): cluster_info, list_topics, describe_topic, topic_offsets, list_consumer_groups, describe_consumer_group (with lag)
Write (read-write+): create_topic, create_partitions, alter_topic_config, reset_consumer_group_offsets
Admin (admin): delete_topic, delete_consumer_group (both need KAFKA_ALLOW_DELETE)
Quickstart — add to your agent
Published on npm as @dockndevai/mcp-kafka. No clone or build needed — your MCP client runs it on demand with npx. Start in read-only mode; see .env.example for every variable and docs/CLIENTS.md for the full per-client guide.
Claude Code (CLI)
claude mcp add kafka -e KAFKA_BROKERS="localhost:9092" -e KAFKA_MODE="read-only" -- npx -y @dockndevai/mcp-kafka
Claude Desktop · Cursor · Windsurf — same block in claude_desktop_config.json, .cursor/mcp.json, or ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"kafka": {
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-kafka"
],
"env": {
"KAFKA_BROKERS": "localhost:9092",
"KAFKA_MODE": "read-only"
}
}
}
}
OpenAI Codex CLI — in ~/.codex/config.toml:
[mcp_servers.kafka]
command = "npx"
args = ["-y", "@dockndevai/mcp-kafka"]
env = { KAFKA_BROKERS = "localhost:9092", KAFKA_MODE = "read-only" }
VS Code (GitHub Copilot, Agent mode) — in .vscode/mcp.json:
{
"servers": {
"kafka": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@dockndevai/mcp-kafka"
],
"env": {
"KAFKA_BROKERS": "localhost:9092",
"KAFKA_MODE": "read-only"
}
}
}
}
Example prompts
- "Which consumer groups have the most lag right now?"
- "Describe the
orderstopic and show its offsets." - "Create a topic
eventswith 6 partitions and 7-day retention." (needsread-write)
Run from source (development)
Prefer the published package above. To run from a clone:
npm install
npm run build
node dist/index.js # with the environment variables set
Develop
npm run dev
npm test
npm run typecheck
Publishing
This server ships a server.json for the official MCP registry and an mcpName for npm ownership validation. See PUBLISHING.md for publishing to npm and listing on the MCP registry, Smithery, Glama, Cursor, and PulseMCP.
License
MIT
Frequently asked questions
What is io.github.dockndevai/mcp-kafka?
Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.
How do I install io.github.dockndevai/mcp-kafka?
It runs on your machine. In Claude Code: claude mcp add mcp-kafka -e 'KAFKA_BROKERS=<KAFKA_BROKERS>' -e 'KAFKA_MODE=<KAFKA_MODE>' -- npx -y @dockndevai/mcp-kafka@0.3.3. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.dockndevai/mcp-kafka need an API key?
Yes. It expects KAFKA_BROKERS, which you set in its configuration.
Is io.github.dockndevai/mcp-kafka open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.dockndevai/mcp-kafka?
It is published by dockndevai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.