redpanda-console-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONSOLE_API_KEY | No | Sent as Authorization: Bearer <key> | |
| CONSOLE_TIMEOUT | No | HTTP timeout in seconds | 60 |
| CONSOLE_BASE_URL | Yes | Console base URL, e.g. https://console.example.com | |
| CONSOLE_VERIFY_TLS | No | Set false only for trusted self-signed hosts | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_topicsB | List Kafka topics with partition count and replication factor. |
| cluster_infoA | Get cluster health: status, version, broker and partition counts. |
| describe_topicA | Get the effective configuration of a topic. |
| fetch_latestB | Fetch the most recent messages from a topic. |
| fetch_by_offsetB | Fetch messages starting at an offset, reading forwards. With partition_id=-1 the offset is applied to every partition, so pass an explicit partition to page deterministically through a topic. |
| fetch_by_timeA | Fetch messages from the first offset at or after a timestamp. |
| search_messagesA | Find messages whose key or value contains the given text. Matching runs server-side in the Console's sandboxed JavaScript interpreter, so only matching messages are transferred. Scanning starts from the oldest message by default; narrow the range with start_offset or start_timestamp_ms on high-volume topics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target distinct resources or operations: listing topics, cluster health, topic config, and message retrieval. The four message-fetching tools (fetch_latest, fetch_by_offset, fetch_by_time, search_messages) share a domain but are clearly differentiated by their selection criteria, so an agent can select correctly.
Tool names follow a mostly consistent snake_case pattern with action-first verbs like list_, describe_, fetch_, and search_. Minor deviations include cluster_info (noun phrase instead of verb_noun) and fetch_latest (verb_adjective), but the overall style is predictable and readable.
Seven tools is a well-scoped set for a read-only Kafka console interface. Each tool earns its place by covering topic listing, cluster health, topic configuration, and various message retrieval strategies without redundancy or bloat.
The surface adequately covers read-only inspection of a Kafka cluster: topics, cluster state, topic configs, and message retrieval by newest, offset, time, or content. Missing consumer group inspection and topic management (create/delete) are notable but likely outside the read-only console scope, so agents can still achieve core monitoring tasks.