io.github.dockndevai/mcp-kafka
Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.
Que pouvez-vous faire avec 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).
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@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>"
}
}
}
}
Variables d'environnement
KAFKA_BROKERSobligatoire Comma-separated broker list (host:port).KAFKA_MODEAccess mode: read-only | read-write | admin.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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
Questions fréquentes
Qu'est-ce que io.github.dockndevai/mcp-kafka ?
Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.
Comment installer io.github.dockndevai/mcp-kafka ?
Il s'exécute sur votre machine. Dans 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. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.dockndevai/mcp-kafka ?
Oui. Il attend KAFKA_BROKERS, à renseigner dans sa configuration.
io.github.dockndevai/mcp-kafka est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.dockndevai/mcp-kafka ?
Il est publié par dockndevai. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.