Kafka MCP Enterprise Server
Provides tools for managing Apache Kafka clusters, including listing and describing topics, consumer groups, cluster metadata, producing and consuming messages, creating and altering topics, and managing ACLs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kafka MCP Enterprise ServerList all topics in the cluster"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kafka MCP Enterprise Server
PyPI
pip install kafka-mcp-enterprise-kip1318
echo {"jsonrpc":"2.0","id":1,"method":"tools/list"} | kafka-mcp-enterprisePackage | |
CLI |
|
Import |
|
Optional |
|
Publish | Tag |
Agents & skills (Cursor, Kiro, ChatGPT, Gemini, Copilot, …)
AGENTS.md |
|
Skills |
|
Guide |
|
Reference implementation of KIP-1318: a first-party Model Context Protocol (MCP) server for Apache Kafka—secure by design, fail-closed by default, and built for agent workloads that must not become a confused deputy on your cluster.
KIP | |
Jira | KAFKA-20436 — Implement KIP-1318 |
Discuss | [DISCUSS] KIP-1318 on |
This repo | Stdlib Python reference / conformance server (teaching, demos, security validation) |
KIP production target | Java module ( |
Scope clarity: The Apache Kafka project tracks the official implementation under KAFKA-20436. This repository is an independent, zero-dependency reference that encodes the enterprise control plane, error model, and conformance tests so designs can be validated before or alongside the Java work. It is not a drop-in replacement for the forthcoming first-party Java MCP server.
Why this exists
AI agents need governed Kafka access—not ad-hoc scripts, unbounded consumes, or shared “god” principals. KIP-1318 proposes a standalone MCP process (stdio / HTTP) that exposes tools and kafka:// resources without changing the Kafka wire protocol. This reference implements the full enterprise control plane below.
Broker ACLs remain authoritative. Guardrails here complement them; they never replace them.
Related MCP server: MCP Server Demo
Complete features, security controls & guardrails
Nothing below is optional marketing — every item is implemented in kafka_mcp/ and covered by the 72/72 conformance suite and/or demos/examples unless noted as a documented reference gap.
A. MCP protocol & surface
Feature | Detail |
JSON-RPC 2.0 | Strict |
|
|
| Visible tools honor deny-list, allow-list, and readonly |
| Full fail-closed pipeline + handler |
| Catalog of |
| Topic/cluster/group/audit/health reads |
stdio transport | Newline-delimited JSON ( |
HTTP notes | Stateless HTTP design documented; full HTTP listener is a KIP/Java concern |
Stateless approvals | HMAC tokens self-contained (no sticky session required for authz correctness) |
Correlation IDs | Per-call |
B. Tools (11) — classified
Tool | kind | module | Kafka op |
| read | control_plane | DESCRIBE |
| read | control_plane | DESCRIBE |
| read | control_plane | DESCRIBE |
| read | control_plane | DESCRIBE |
| read | control_plane | DESCRIBE |
| read | data_plane | READ |
| mutate | control_plane | CREATE |
| mutate | control_plane | ALTER |
| mutate | data_plane | WRITE |
| destructive | control_plane | DELETE |
| destructive | control_plane | ALTER |
C. Resources (kafka://)
URI | Purpose |
| List topics |
| Describe topic |
| Cluster id + brokers |
| Consumer groups |
| Recent audit entries |
| Liveness + per-module circuit breaker state |
D. Fail-closed security pipeline (exact order)
Every tools/call — first denial wins:
Step | Control | Denial code |
1 | Bearer auth — audience / issuer validation (off until configured) |
|
2 | Deny-list ( |
|
3 | Allow-list ( |
|
4 | Topic prefix scope + group prefix scope |
|
5 | Policy engine — callable; deny or exception → fail-closed |
|
6 | Taint guard / IFC — destructive tools; optional |
|
7 | Approval gate — HMAC signed TTL token ( |
|
8 | Rate limit — general vs admin/control-plane buckets |
|
9 | Execute via per-module circuit breaker + dependency check |
|
Pre / around execute (also enforced):
Guardrail | Behavior | Code |
Input validation | Identifier charset; |
|
Rogue-agent kill-switch | Per-identity destructive burst → quarantine |
|
Identity propagation | Optional per-principal broker ACL check before execute |
|
Sensitive-topic gating | Pattern match on consume → requires approval |
|
Egress DLP | Block secret categories on produce |
|
Dry-run tools |
| — |
Consume clamp |
| — |
Byte bounds |
| truncation tags |
Post-execute DLP scrub | Redact/scrub whole result tree | — |
Taint registration | Consumed values registered into session taint set | — |
Audit | ALLOW/DENY recorded (params truncated, hash-chained) | — |
E. Data-protection guardrails (DLP)
Capability | Detail |
Modes |
|
Default block categories |
|
Detectors (10) | email, ssn, credit_card (Luhn-validated), phone, ipv4, aws_access_key, private_key, jwt, iban, secret_assignment |
Consume path | Redact PII in records; block-mode can refuse |
Produce path | Egress scan → |
Sensitive configs | Mask password/secret-like keys on describe ( |
Scrub all outputs | Walk entire JSON result ( |
Legacy interceptor |
|
F. Approval, taint & IFC
Capability | Detail |
HMAC approval tokens |
|
Forged / expired tokens | Rejected → |
Default approval-required tools |
|
Taint guard | Best-effort substring match of session tainted values into destructive args |
| After untrusted read, blocks destructive/control-plane without approval |
Honesty | Taint is defeatable by laundering; least-privilege broker ACLs are load-bearing |
G. Scoping, exposure & identity
Capability | Detail |
Tool allow-list / deny-list |
|
Secure-by-default guidance | Ops should set allow-list to read/non-destructive (harness default |
Readonly mode | Disables create/produce/alter/delete/ACLs |
Topic prefixes |
|
Group prefixes |
|
Identity propagation |
|
Session identity |
|
H. Resilience & blast-radius controls
Capability | Detail |
Circuit breakers | Per module: |
Breaker isolation | Control-plane open does not take down data-plane consume/produce |
Dependency failure hook |
|
Rate limits |
|
Quarantine |
|
Health resource | Breaker states on |
I. Consume semantics (Direct Partition Assignment)
Mode | Behavior |
No |
|
With | Classic group path; register offsets; rebalance counter increments |
J. Backend surface (in-memory Kafka)
create_topic, delete_topic, list_topics, describe_topic, alter_topic_config, produce, consume, list_groups, describe_group, group_lag, create_acls, list_acls, describe_cluster, principal ACLs, rebalance counter, dependency hooks.
K. Audit
Capability | Detail |
Ring buffer | Recent entries ( |
Hash chaining | Tamper-resistant best-effort chain |
Param truncation | Long params truncated (>64 chars) |
Decisions |
|
Resource |
|
| Config name present; durable Kafka mirror is a documented reference gap |
L. Error codes (complete — 15)
Code | Constant | Meaning |
-32700 | PARSE_ERROR | JSON parse error |
-32600 | INVALID_REQUEST | Invalid request |
-32601 | METHOD_NOT_FOUND | Unknown method/tool |
-32602 | INVALID_PARAMS | Invalid params / structured Kafka errors |
-32603 | INTERNAL_ERROR | Internal error |
-32001 | UNAUTHORIZED | Bad/missing bearer |
-32029 | RATE_LIMITED | Rate limited |
-32040 | TAINT_VIOLATION | Tainted value into destructive tool |
-32041 | SCOPE_VIOLATION | Topic/group out of scope |
-32042 | APPROVAL_REQUIRED | Destructive/sensitive needs approval |
-32043 | DEPENDENCY_UNAVAILABLE | Circuit breaker open / dependency down |
-32044 | POLICY_DENIED | Deny/allow/readonly/policy/ACL propagation |
-32045 | SENSITIVE_DATA_BLOCKED | Egress / DLP block |
-32046 | VALIDATION_FAILED | Malformed identifier / oversized value |
-32047 | QUARANTINED | Rogue-agent kill-switch |
M. Configuration surface (32 fields)
bootstrap_servers, transport, tools_allowed, tools_denied, readonly, allowed_topic_prefixes, allowed_group_prefixes, taint_guard_enabled, approval_required_tools, dryrun_tools, audit_topic, policy_engine, circuit_breaker_enabled, dependency_timeout_ms, rate_requests_per_second, rate_admin_requests_per_second, oauth_expected_audience, oauth_expected_issuer, approval_signing_secret, redaction_enabled, dlp_mode, dlp_block_categories, scrub_all_outputs, redact_sensitive_configs, sensitive_topic_patterns, max_value_bytes, max_output_bytes, max_destructive_per_minute, ifc_strict, hard_max_records, hard_max_bytes, identity_propagation.
Full defaults: doc/configuration.md.
N. Quality, packaging & agent DX
Feature | Detail |
Conformance suite | 72/72 checks (functional, security, guardrails, mechanisms, resources, stdio) |
Smoke + demo |
|
Examples | Six folders with real-world |
PyPI |
|
Stdlib-only core | No hard third-party deps |
Optional OTel |
|
AGENTS.md + skills | Cursor / Kiro / Copilot / ChatGPT / Gemini (doc/agents-and-skills.md) |
O. Documented reference gaps (intentional)
HTTP full server · real brokers · HTTP policy URL client · durable audit_topic publish · wall-clock dependency_timeout_ms · some approval tool names reserved but not all registered · production language = Java (this package is the Python reference). See doc/kip-alignment.md.
Quick start
Requires Python 3.8+. Core has no third-party packages.
# From source
python run_tests.py
python demo_end_to_end.py
python examples/01_sre_readonly_triage/run.py
echo {"jsonrpc":"2.0","id":1,"method":"tools/list"} | python serve_stdio.pySee the PyPI section at the top for pip install, or doc/publishing.md to publish a release.
Documentation & examples
Resource | Description |
End-to-end guides: getting started, architecture, security, config, tools, errors, testing | |
Feature matrix vs KIP-1318 — what is implemented vs intentional reference gaps | |
PyPI package | |
OpenTelemetry: optional, not required | |
AGENTS.md + skills for all IDEs | |
Six folder-based scenarios ( |
Repository layout
kafka_mcp/ # Reference server package (security pipeline + in-memory Kafka)
tests/ # 72-check conformance suite
doc/ # Public documentation
examples/ # Production-shaped scenarios
serve_stdio.py # stdio entrypoint
run_tests.py # Master test runner
demo_end_to_end.py # 22-step control demoEngineering standards
This reference aims at production-grade practice even while staying a teaching implementation:
Practice | How it shows up |
Fail-closed | First denial wins; no execute-then-check paths |
Least privilege | Prefix scopes, allow/deny lists, readonly, approval for destructive ops |
Defense in depth | MCP controls + explicit honesty that broker ACLs are load-bearing |
Bounded blast radius | Hard record/byte caps, rate limits, per-plane breakers, quarantine |
Observable denials | Stable error codes, correlation IDs, audit ALLOW/DENY |
Testability | Deterministic in-memory backend; security + integration coverage |
Zero dependency debt | Python stdlib only — easy to audit and run in CI |
Clear product boundary | Official Kafka delivery tracked on KAFKA-20436 (Java) |
Honest limitations (by design)
Taint / IFC is best-effort — defeatable by data laundering; do not treat as complete mediation.
In-memory Kafka — validates control logic; not a broker client.
stdio-first — HTTP is specified in the KIP; this reference documents notes, full HTTP is a Java/production concern.
Secure-by-default in ops — tighten
tools_allowedto read/non-destructive in real deployments (see configuration guide).
Related links
KIP-1318 (wiki): https://cwiki.apache.org/confluence/display/KAFKA/KIP-1318%3A+Model+Context+Protocol+%28MCP%29+Server+for+Apache+Kafka
MCP specification: https://modelcontextprotocol.io/
License & affiliation
Apache Kafka, KIP-1318, and KAFKA-20436 are trademarks / projects of the Apache Software Foundation. This repository is a community reference aligned with that proposal; it is not the official ASF deliverable unless and until merged under the Kafka project.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vaquarkhan/kafka-mcp-enterprise-server-kip-1318'
If you have feedback or need assistance with the MCP directory API, please join our Discord server