Back to MCP Servers

Confluent

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

databasesapirest
By confluentinc
16455Updated 3 days agoTypeScriptMIT

Installation

npx -y mcp-confluent

Configuration

{
  "mcpServers": {
    "mcp-confluent": {
      "command": "npx",
      "args": ["-y", "mcp-confluent"]
    }
  }
}

How to use

  1. Run the installation command above (if needed)
  2. Open your Claude Code settings file (~/.claude/settings.json)
  3. Add the configuration to the mcpServers section
  4. Restart Claude Code to apply changes

Confluent MCP Server

npm version License: MIT

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.

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:
npx @confluentinc/mcp-confluent --init-config
  1. Edit the config.yaml file with your connection details, then:
npx @confluentinc/mcp-confluent --config ./config.yaml

See Getting Started for full setup instructions and Configuring MCP Clients for integration with your preferred AI tool.

Table of Contents

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:

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

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.

CategoryToolsDescription
Documentationsearch-product-docs, get-product-doc-pageSearch Confluent product docs and fetch full page content
Diagnosticsexplain-disabled-tools, list-configured-connections, config-help, describe-configured-connectionExplain 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.

CategoryToolsDescription
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-configManage 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-poolsCreate and manage Flink SQL statements; discover Flink compute pools
Flink Catalog ¹list-flink-catalogs, list-flink-databases, list-flink-tables, describe-flink-table, get-flink-table-infoExplore Flink catalogs, databases, and table schemas
Flink Diagnostics ¹check-flink-statement-health, detect-flink-statement-issues, get-flink-statement-profileHealth checks, issue detection, and query profiling
Connectors ¹list-connectors, get-connector-config, get-connector-offsets, get-connector-status, get-connector-tasks, get-connector-error-summary, get-connector-error-recommendations, get-connector-logs, create-connector ², delete-connector, pause-connector, resume-connector, restart-connector, update-connector-configInspect and manage Kafka Connect connectors
Schema Registry ¹list-schemas, create-schema, delete-schemaList, inspect, create, and delete data schemas
Catalog & Tags ¹search-topics-by-tag, search-topics-by-name, create-topic-tags, delete-tag, remove-tag-from-entity, add-tags-to-topic, list-tagsOrganize and search topics using tags
Organizations, Environments & Clusters ¹list-organizations, list-environments, read-environment, list-clustersDiscover Confluent Cloud resources
Tableflow ¹create-tableflow-topic, list-tableflow-topics, read-tableflow-topic, update-tableflow-topic, delete-tableflow-topic, list-tableflow-regionsManage Tableflow-enabled topics
Tableflow Catalog ¹create-tableflow-catalog-integration, list-tableflow-catalog-integrations, read-tableflow-catalog-integration, update-tableflow-catalog-integration, delete-tableflow-catalog-integrationManage Tableflow catalog integrations (e.g., AWS Glue)
Metrics ¹list-available-metrics, query-metricsDiscover and query Confluent Cloud operational metrics
Billing ¹list-billing-costsQuery billing and cost data

¹ Also available under OAuth — see OAuth Authentication for Confluent Cloud for setup and caveats. Categories not marked currently require a direct connection with static API keys; OAuth migration is in progress.

² Individual tool not available under OAuth; requires a direct connection with static API keys.

Available Tools for local deployments

These tools only require Kafka or Schema Registry endpoints - no Confluent Cloud API key/secret is needed. Ideal for local development with self-managed clusters, including Confluent Platform.

View source on GitHub