Apache Kafka client
Inspect topic messages and consumer lag, or produce a test message with KafkaQL, TablePro’s own command language.
At a glance
- Query language
- KafkaQL
- Driver
- Downloads on first use
- Connect with
- Host and port, SSH tunnel, SSL/TLS
- Default port
- 9092
- Minimum version
- 0.11


Connect
Enter a bootstrap broker’s host and port, and add fallback brokers in Additional Bootstrap Servers. Each connection reaches one cluster, with its topics in the sidebar.
Security Protocol is PLAINTEXT, SSL, SASL_PLAINTEXT or SASL_SSL, and SASL Mechanism is PLAIN, SCRAM-SHA-256 or SCRAM-SHA-512: PLAIN suits Confluent Cloud, SCRAM suits Amazon MSK and self-hosted brokers. With SSL or SASL_SSL and no SSL mode chosen, the certificate chain and hostname are verified. A private CA goes in CA Certificate, and a client certificate and key add mutual TLS.
Through an SSH tunnel, the connection stays on the bootstrap broker, so it reads only the partitions that broker leads. Import from URL… accepts kafka:// URLs, which macOS does not open as links.
Read, inspect and produce
Browse recent messages with partition, offset, timestamp, key, value and headers. Messages from several partitions are interleaved by timestamp, non-UTF-8 values show as hex, and tombstones stay distinct from empty messages.
KafkaQL consumes from the newest or oldest message, an offset or an ISO 8601 timestamp, optionally scoped to partitions. SHOW lists topics, brokers, groups and cluster details, and DESCRIBE TOPIC inspects a topic. DESCRIBE GROUP is the lag report: the committed offset, the end offset and the gap, per partition. A partition the group never committed shows no lag rather than a number counted from zero.
PRODUCE INTO writes a message with an optional key, headers and partition, and a keyed message with no partition lands where Kafka’s own producer would put it. gzip, snappy, lz4 and zstd batches are decompressed as they are read.
Messages cannot be edited or deleted one by one, and paging continues from the previous position as new messages arrive.
Topics
Dropping a topic, from the sidebar or with DROP TOPIC, is the one destructive action. The cluster removes the log afterwards, so the topic can stay in the list for a moment. Truncate is not offered: Kafka removes records by retention or by an offset per partition, and neither empties a topic.
This page covers what is specific to Apache Kafka. Safe Mode, the AI assistant, the MCP server and the rest of TablePro are on the feature pages.
Also
Move data
There is no import: put messages into a topic with
PRODUCE INTO. Export the messages a query read as CSV, JSON, SQL, XLSX, Markdown, HTML and XML.Limits
- Schema Registry is not read, so Avro and Protobuf values show as raw bytes.
- Creating topics, editing topic configuration and resetting consumer-group offsets are not supported.
- Message counts are approximate.
Why do topics load but their messages time out?
The cluster advertises addresses this Mac cannot reach, such as a container hostname or a private IP. Fix
advertised.listeners, or set Broker Addresses to use only the bootstrap address.Does Amazon MSK IAM sign-in work?
No. The SASL mechanisms are PLAIN, SCRAM-SHA-256 and SCRAM-SHA-512, so create a SCRAM user on the MSK cluster and connect with SASL_SSL.
Get TablePro
Everything on this page is free.