KafDesk

com.kafdeskPublished by kafdesk.comv0.2.8Updated Nov 7, 2026

Apache Kafka for AI agents: topics, records, consumer lag and schemas. Read-only by default.

VerifiedSTDIODesktop onlyDatabases

Overview

AI-generated overview

KafDesk is a local MCP server that lets an AI assistant inspect Apache Kafka topics, records, consumer lag and schemas, read-only by default.

What you can do
  • Browse Kafka topics and their records
  • Inspect consumer lag
  • Look up message schemas
  • Operate read-only by default
When to use it
Useful when you want an assistant to explore or explain a Kafka cluster's topics, messages, consumer lag or schemas without writing ad-hoc scripts.
Requirements
Runs as a local stdio process installed from an .mcpb package; desktop-only, not runnable in a browser. No authentication, environment variables or headers are declared, so connection details for your Kafka cluster are not documented here.
Before you install
The description states it is read-only by default, but does not say whether that can be changed; confirm before pointing it at production clusters. Message records and schemas may contain sensitive data, and no credential handling is documented.

Installation

In SourceWeft

  1. Open KafDesk in the dashboard and add it to a workspace.
  2. 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.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.8LatestNov 7, 2026

Score

15% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.