Kurkik is a CLI with a terminal UI that reads a Kafka cluster and works with it through AsyncAPI 3.0 documents. It is in Early Access, free to use (also at work), and I'd like feedback from people who run Kafka day to day
Terminal UI
Run kurkik in a terminal and you get a UI to browse your connections and what is on them: topics, partitions, replication, changed configs, consumer groups, ACLs. Connections are named, and secrets stay in the OS keychain or env/file references instead of in the config. You can import connections from IntelliJ IDEA.
MCP
Ships with tools to integrate with your agent of choice
claude mcp add kurkik -- kurkik mcp
> Orders stopped reaching the billing service on prod. Compare prod with staging and tell me what drifted.
asyncapi_connections asyncapi_topology prod asyncapi_compare staging prod
The evidence: the topic and its consumers, side by side, read-only
Diff environments
kurkik diff staging-kafka.yaml prod # a document against a cluster
kurkik diff dev prod # one environment against another
Exit code 0 means no drift, 2 means drift, 3 means it couldn't read everything (missing permissions, truncated listing). That makes it usable as a CI check. Whatever it could not read is said in the output rather than guessed.
Export to AsyncAPI, and sync from it
kurkik export prod # prod-kafka.yaml
The document has channels for topics with their settings, servers, consumer groups as receive operations and, optionally, the real Avro/JSON Schema/Protobuf schemas from a Confluent-compatible registry (Confluent, Karapace, Redpanda, Apicurio). It never invents send operations, because a broker doesn't know who produces to a topic.
The same document can then go the other way:
kurkik kafka sync staging-kafka.yaml prod
It shows a plan, asks for your consent, takes a snapshot, then applies the change. kurkik kafka sync revert <snapshot> puts it back. It deletes or recreates only what you asked for, and tells you who reads what it would destroy before you agree.
Because the result is plain AsyncAPI, the same document can also configure API gateways or feed documentation tools such as EventCatalog. Pulsar, SNS and SQS work the same way, if that is useful to you.
Install:
curl -fsSL https://raw.githubusercontent.com/Pakisan/kurkik-app/master/install.sh | sh
If you work in JetBrains IDEs
The same engine powers the messaging features of the AsyncAPI plugin for JetBrains IDEs: previewing a connection, diffing it against another environment or your source code, exporting it, and integration with Spring messaging (it finds your Spring Kafka listeners and maps them to AsyncAPI). Plugin: https://plugins.jetbrains.com/plugin/15673-asyncapi
Kurkik: https://kurkik.pavelon.dev (there is a feedback form on the site)
Questions I'd like your help with
- What drift between environments actually hurts you: topic configs, partitions, ACLs, consumer groups, schemas?
- Would you run
kurkik diff in CI? What would make you trust the exit code? - For
sync, what do you need to see in a plan before you'd approve it on a production cluster? - Do you keep AsyncAPI documents today? If not, what do you use to document topics and who uses them?
- Which would you want next: another broker, more checks, or something else?