# confluentinc/mcp-confluent [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/confluentinc/mcp-confluent  
**GitHub Stars:** 168  
**npm Downloads (last month):** 2011  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/confluentinc-mcp-confluent

## Description
Confluent integration to interact with Confluent Kafka and Confluent Cloud REST APIs.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-confluent": {
    "command": "npx",
    "args": ["-y","@confluentinc/mcp-confluent"]
  }
}
```

## Documentation

## 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:

```bash
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:

```bash
npx @confluentinc/mcp-confluent --config ./config.yaml
```

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

```bash
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.

_Full upstream README: https://allmcps.com/mcp/confluentinc-mcp-confluent/readme_