Mcp Kafka

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 28, 2026

Read-only Kafka for AI agents — topics, offsets, consumer groups, peek messages, health.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Read-only Kafka access for AI assistants: inspect topics, offsets, consumer groups, sample messages and cluster health from a local stdio process.

What you can do
  • Inspect Kafka topics and their metadata
  • Review offsets and consumer group state
  • Peek at messages to see what a topic contains
  • Check cluster health
  • All operations are described as read-only, so the assistant observes rather than changes the cluster.
When to use it
Useful when you want an assistant to help investigate a Kafka cluster: finding out which topics exist, why a consumer group is lagging, or what messages are flowing through a topic, without giving it write access.
Requirements
Runs as a local process over stdio, installed from the npm package @infoinlet/mcp-kafka, so Node.js and npm are needed. Desktop client only; no web execution. No authentication, environment variables or headers are declared, so broker connection details must be supplied some other way.
Before you install
The manifest declares no credentials, but the server still needs to reach your Kafka brokers, so connection details and any broker credentials will be configured locally. Peeking at messages exposes real topic payloads to the assistant and its model provider. It is advertised as read-only, but verify that before pointing it at production clusters.

Installation

In SourceWeft

  1. Open Mcp Kafka 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% 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
  • 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.