Confluent Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

MCP server for Confluent Cloud: environments, Kafka clusters. Needs an API key.

VerifiedSTDIODesktop onlyCloud & Infrastructure

Overview

AI-generated overview

An MCP server that lets an assistant work with Confluent Cloud environments and Kafka clusters.

What you can do
It exposes Confluent Cloud resources to an assistant, covering environments and Kafka clusters. The registry description says it is an MCP server for Confluent Cloud: environments, Kafka clusters. No tool list is published, so the exact operations are not documented here. It runs locally over stdio as an npm package.
When to use it
Worth considering when you manage Confluent Cloud and want an assistant to reach your environments and Kafka clusters without leaving the chat. It is a poor fit if you do not use Confluent Cloud or need documented, granular tool behavior before installing.
Requirements
Runs as a local process over stdio, installed from the npm package confluent-mcp, so Node.js and npm are needed. The description states it needs an API key, though no environment variable or header name is declared. Desktop only; no web execution.
Before you install
It asks for a Confluent Cloud API key, which is a credential granting access to your account resources; the input does not name the variable or header that carries it, so confirm how it is supplied and scope the key narrowly. The published tool list is empty, so what the assistant can read or change in your environments and clusters is unverified. Treat cluster-affecting actions with care.

Installation

In SourceWeft

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

2
  1. v1.0.1LatestOct 17, 2026
  2. v1.0.0Sep 22, 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.