🐍 ☁️ - Confluent integration to interact with Confluent Kafka and Confluent Cloud REST APIs
Confluent MCP Server
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
An open-source MCP server that enables AI assistants to interact with Confluent Cloud, Confluent Platform, and standalone Apache Kafka deployments through natural language.
It provides 50+ tools across Kafka, Flink SQL, Schema Registry, Connectors, Tableflow, and more -- usable from any MCP-compatible client including Claude Desktop, Claude Code, Cursor, VS Code, Goose, and Gemini CLI.
> [!TIP]
> **Already a Confluent Cloud customer?**
> Confluent offers a fully managed MCP server with no local server to run and no dependencies to install.
> It provides access to your Confluent Cloud resources with AI-powered connector diagnostics, governed by your existing RBAC permissions.
> Use this open-source server if you need Confluent Platform / self-managed Kafka support, or want to customize and extend the toolset.
>
> **NOTE:** The open-source MCP server is a community-supported project. Confluent doesn’t provide dedicated support for it, and support is best-effort only, with no service level commitments. If you run into an issue or want to contribute, open an issue or pull request directly in this repository.
Quick Start
> **Prerequisites:** Node.js 22.19.0+.
> If you want to interact with Confluent Cloud, you need to create an account first.
1. Generate a quick config.yaml file in your project root:
2. Edit the config.yaml file with your connection details, then:
See Getting Started for full setup instructions and Configuring MCP Clients for integration with your preferred AI tool.
Table of Contents
- Quick Start
- Available Tools
- Always Available
- Confluent Cloud
- Local deployments
- Using with Confluent Platform
- Getting Started
- Configuration
- OAuth Authentication for Confluent Cloud
- CLI Usage
- Configuring MCP Clients
- Telemetry
- Troubleshooting
- Contributing
Available Tools
Tools are auto-enabled based on which service blocks are present in your resolved configuration; see CONFIGURATION.md for the full block-to-tool mapping.
You can list all available tools via the CLI:
Always-Available Tools
These tools need no service blocks or authentication — they're enabled even on a bare config, regardless of which deployment the rest of your config targets.
| Category | Tools | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Documentation** | search-product-docs, get-product-doc-page | Search Confluent product docs and fetch full page content |
| **Diagnostics** | explain-disabled-tools, list-configured-connections, config-help, describe-configured-connection | Explain why tools are absent, list configured connections and the tools enabled on each, suggest the YAML to enable a specific tool, and describe one connection's config and tool availability |
Available Tools for Confluent Cloud
These tools require endpoints and authentication against specific Confluent Cloud components.
Refer to config.example.yaml for the full set of configuration variables.
Categories marked with ¹ also work with OAuth authentication — sign in via your browser instead of provisioning API keys.
| Category | Tools | Description |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Kafka** ¹ | list-topics, create-topics, delete-topics, produce-message, consume-messages, list-consumer-groups, describe-consumer-group, get-consumer-group-lag, alter-topic-config, get-topic-config | Manage topics, produce/consume messages, inspect consumer groups, configure topic settings |
| **Flink SQL** ¹ | create-flink-statement, list-flink-statements, get-flink-statement-results, delete-flink-statements, get-flink-statement-exceptions, list-compute-pools | Create and manage Flink SQL statements; discover Flink compute pools |