Log inSubmit server
MCP Confluent logo

MCP Confluent

by confluentinc

Connects AI assistants to Kafka, Confluent Cloud, Flink SQL, Schema Registry, and Kafka Connect through 50+ MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Confluent

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "confluentinc-mcp-confluent": {
      "command": "npx",
      "args": [
        "-y",
        "@confluentinc/mcp-confluent"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

confluentinc/mcp-confluent exposes Confluent Cloud, Confluent Platform, and standalone Apache Kafka operations through the Model Context Protocol. Its toolset covers Kafka topics and messages, Flink SQL and diagnostics, Schema Registry, Kafka Connect, Tableflow, documentation search, and configuration diagnostics. Tools are enabled from configured service blocks in a YAML file, so the available capabilities depend on the connections and authentication you provide. Reach for it when an MCP-compatible assistant needs to inspect or manage Confluent resources, including self-managed Kafka deployments.

Use cases

  • Manage Kafka topics and topic configuration
  • Produce and consume Kafka messages
  • Inspect consumer groups and connector failures
  • Run and diagnose Flink SQL statements
  • Create and manage schemas and connectors

Key features

  • Kafka topic, message, and consumer-group operations
  • Flink SQL execution and diagnostics
  • Kafka Connect inspection and lifecycle management
  • Schema Registry schema management
  • Confluent documentation search
  • Configuration and disabled-tool diagnostics

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

20/21 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @confluentinc/mcp-confluent (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars168Stargazers on the source repository.
npm downloads2kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Confluent works

What confluentinc/mcp-confluent does

confluentinc/mcp-confluent lets MCP-compatible AI assistants work with Confluent Cloud, Confluent Platform, and standalone Apache Kafka through natural-language requests. The open-source server provides more than 50 tools spanning Kafka, Flink SQL, Flink catalogs, Kafka Connect, Schema Registry, Tableflow, product documentation, and configuration diagnostics.

Kafka tools can list, create, and delete topics; produce and consume messages; inspect consumer groups; and read or change topic configuration. Flink tools cover statement creation and management, result retrieval, exceptions, compute-pool discovery, catalog exploration, table descriptions, health checks, issue detection, and query profiling. Connector tools inspect status, tasks, offsets, configuration, logs, errors, and recommendations, as well as create, delete, pause, resume, restart, and update connectors. Schema Registry tools list, create, and delete schemas.

How it works

The server reads a YAML configuration and automatically enables tools based on the service blocks present in the resolved configuration. A bare configuration still exposes documentation and diagnostic functions, including product-documentation search, full-page retrieval, connection listing, configuration help, and explanations for disabled tools.

Cloud-facing capabilities use endpoints and authentication for the relevant Confluent Cloud components. Some Confluent Cloud categories support OAuth authentication, allowing sign-in through a browser instead of using API keys. The same project can also target Confluent Platform and self-managed Kafka deployments.

Setup and configuration

Node.js 22.19.0 or newer is required. Generate a starter configuration in the project directory with:

Terminal
npx @confluentinc/mcp-confluent --init-config

Edit the resulting config.yaml with the connection details for the services you intend to use, then start the server:

Terminal
npx @confluentinc/mcp-confluent --config ./config.yaml

Use the tool-listing command to inspect the capabilities enabled by a configuration:

Terminal
npx -y @confluentinc/mcp-confluent --list-tools

The project can be configured for MCP clients including Claude Desktop, Claude Code, Cursor, VS Code, Goose, and Gemini CLI. Confluent Cloud users can also choose Confluent's separately managed MCP server when they do not need local execution, self-managed Kafka support, or customization of this toolset.

Tools and capabilities

Key tool groups include:

  • Kafka topics, messages, consumer groups, and topic settings
  • Flink SQL statements, results, exceptions, compute pools, and diagnostics
  • Flink catalogs, databases, tables, and schema information
  • Kafka Connect connectors, tasks, offsets, status, logs, errors, and lifecycle operations
  • Schema Registry schema listing, creation, and deletion
  • Topic and entity tagging, plus Tableflow operations
  • Confluent product-documentation search and page retrieval
  • Connection inspection, configuration guidance, and disabled-tool diagnostics

Tools that modify topics, messages, statements, connectors, schemas, or tags should be enabled only for configurations with appropriate access controls.

Limitations and notes

The open-source project is community-supported and has best-effort support without service-level commitments. Confluent Cloud authentication and available operations depend on the configured endpoints, credentials, and enabled service blocks. The managed Confluent Cloud MCP server is a separate option and is not required for this local server.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Confluent

confluentinc/mcp-confluent is an MCP server that connects AI assistants to Confluent Cloud, Confluent Platform, and standalone Apache Kafka. Its main tools manage Kafka topics and messages, run Flink SQL, inspect connectors and consumer groups, manage schemas, search product documentation, and diagnose configuration.

Install and run it with `npx` after installing Node.js 22.19.0 or newer. Generate a starter file with `npx @confluentinc/mcp-confluent --init-config`, edit `config.yaml`, then start it with the `--config` option.

Configure tools by adding the relevant service blocks and connection details to the YAML configuration. The server enables tools automatically from those blocks, and `--list-tools` shows the resulting tool set.

Yes, Cursor is listed as a compatible MCP client for confluentinc/mcp-confluent. The server can also be used with Claude Desktop, Claude Code, VS Code, Goose, and Gemini CLI.

Yes, it supports Confluent Platform and standalone Apache Kafka deployments as well as Confluent Cloud. This makes the open-source server suitable when local or self-managed Kafka access is required.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Confluent AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/confluentinc-mcp-confluent?style=directory)](https://allmcps.com/mcp/confluentinc-mcp-confluent)
HTML Embed
<a href="https://allmcps.com/mcp/confluentinc-mcp-confluent"><img src="https://allmcps.com/api/badge/confluentinc-mcp-confluent?style=directory" alt="MCP Confluent on AllMCPs" /></a>