
Strimzi Kafka Cli
io.github.SystemCraftsmanPublished by GitHub account SystemCraftsmanv1.0.0b11Updated Oct 24, 2026
Manage Apache Kafka on Kubernetes via Strimzi. Clusters, topics, users, connectors, MM2.
Overview
Lets an AI assistant manage Apache Kafka on Kubernetes through Strimzi: clusters, topics, users, connectors, MirrorMaker2, ACLs and the operator itself.
- What you can do
- List, inspect, create, alter and delete Kafka clusters, including status and configuration changes
- Manage topics, users and ACLs, and add or remove entity configs
- Manage Kafka Connect clusters, connectors and MirrorMaker2 instances
- Back up and restore Kafka and Connect resources
- Install or uninstall the Strimzi operator and manage Kafka node pools
- Report the CLI version
- When to use it
- Useful when you run Apache Kafka on Kubernetes with the Strimzi operator and want an assistant to inspect or change clusters, topics, users, connectors or mirroring from a chat, instead of typing kfk commands yourself.
- Requirements
- Local Python package (Python 3.11 or newer) installed with MCP extras, or via Homebrew, which includes MCP support; started with the kfk mcp command. Needs a configured Kubernetes cluster with Strimzi resources, which are downloaded on first use, and access through the Python Kubernetes client.
Installation
In SourceWeft
- Open Strimzi Kafka Cli in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[Build] [Integration Test] [Deploy] [PyPI] [Downloads] [License] [Strimzi] [MCP Server]
Strimzi Kafka CLI
Strimzi Kafka CLI is a CLI that helps traditional Apache Kafka users -both developers and administrators- to easily adapt to Strimzi, a Kubernetes operator for Apache Kafka.
The main intention is to ramp up Strimzi usage by creating a similar CLI experience with the traditional Apache Kafka tools that mostly starts with kafka-* prefix under the bin directory in an ordinary Kafka package.
Strimzi Kafka CLI uses the kfk command as an abbreviation for "Kafka For Kubernetes" or simply "k a f k a" which reminds of the kafka-* prefix of the ordinary Kafka script file names.
While having similar set of commands or options for some of the common objects, Strimzi Kafka CLI has some extra capabilities for managing or configuring Strimzi related resources.
Following are the commands of the current version of Strimzi Kafka CLI, that are used for different purposes:
Please take a look at the relevant article Strimzi Kafka CLI: Managing Strimzi in a Kafka Native Way for more details.
Installation
Using Python Package Installer
Or to install Strimzi Kafka CLI in an isolated environment, you can simply use pipx:
To install with MCP server support:
Or with pipx:
Using Homebrew
Installing the CLI by using Homebrew already uses a virtual environment, so you don't have to worry about your main Python environment. MCP server support is included by default.
Project requires: Python >=3.11
Examples
MCP Server
Strimzi Kafka CLI includes an MCP (Model Context Protocol) server that allows AI assistants to manage Strimzi Kafka deployments on Kubernetes.
Starting the MCP Server
Registering with Claude Code
Available Tools (42)
Dependencies
Python Dependencies
Please see pyproject.toml file.
External Dependencies
Strimzi resources are automatically downloaded when the first kfk command is run. Strimzi Kafka CLI uses the Python Kubernetes client to interact with the cluster directly. You can check the dependency versions with:
Source: README.md at commit 1727572
Tools
0Version history
1- v1.0.0b11LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts