kafka-mcpCAUTION

Put an AI assistant in charge of your Kafka estate.

Not a chat window onto a cluster. A way for agents — yours, or ours — to see what is actually happening across every cluster you run, and to act on it: reclaim the topics nobody consumes, attribute cost back to the teams spending it, catch the certificate expiring next month, restart the connector that failed at 3am, label the topics whose owner left the company.

The MCP endpoint ships inside Conduktor Console. There is nothing to deploy, and nothing new to secure: the assistant inherits the RBAC, audit trail and ownership model you already run.

Try it first

No Kafka to hand? demo/ brings up a cluster, Console and the MCP endpoint with docker compose up -d, seeded with topics, traffic and a consumer group that is deliberately behind.

Setup

Create a Personal Access Token in Console, then point your MCP client at your own Console:

{
"mcpServers": {
"conduktor": {
"command": "npx",
"args": ["-y", "@conduktor/mcp"],
"env": {
"CONDUKTOR_CONSOLE_URL": "https://console.acme-corp.com",
"CONDUKTOR_API_TOKEN": "your-personal-access-token"
}
}
}
}

/api/mcp is appended for you. Pasting a URL that already ends in it works too.

Connecting without the package

@conduktor/mcp wraps `mcp-remote`. Call it yourself if you prefer:

{
"mcpServers": {
"conduktor": {
"command": "npx",
"args": [
"mcp-remote",
"https://console.acme-corp.com/api/mcp",
"--header",
"Authorization: Bearer ${CONDUKTOR_API_TOKEN}"
],
"env": { "CONDUKTOR_API_TOKEN": "your-personal-