
Confluent MCP Server
OfficialManage Confluent Cloud, Confluent Platform & Apache Kafka via natural language — 50+ tools across Kafka, Flink, Schema Registry & more.
Add to your client
Copy the config for your MCP client and paste it into its config file.
npx -y @confluentinc/mcp-confluentPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"confluent-mcp-server": {
"command": "npx",
"args": [
"-y",
"@confluentinc/mcp-confluent",
"--config",
"/path/to/config.yaml"
]
}
}
}Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- Node.js 22 or later
- A config.yaml file (generate with `npx @confluentinc/mcp-confluent --init-config`)
- For Confluent Cloud: a Confluent Cloud account with API keys, or OAuth sign-in credentials
- For local/Confluent Platform: a Kafka and/or Schema Registry endpoint
- pnpm only if building from source
About Confluent MCP Server
Confluent MCP Server connects MCP-compatible AI clients to Confluent Cloud, Confluent Platform, and standalone Apache Kafka. It provides 50+ tools across Kafka, Flink SQL, Schema Registry, Connectors, Tableflow, catalog/tags, metrics, and billing. Configuration is YAML-based (bootstrap with --init-config), tools are auto-enabled by the service blocks present in your config, and authentication uses static API keys or OAuth (PKCE). The server runs over stdio by default and optionally HTTP/SSE.
Tools & capabilities (71)
search-product-docsSearch Confluent product documentation (docs.confluent.io, developer.confluent.io, support.confluent.io) by keyword.
get-product-doc-pageFetch the full markdown content of a Confluent product documentation page.
explain-disabled-toolsExplain why a tool is missing or unavailable (e.g., why a Kafka tool can't be listed).
list-configured-connectionsList every configured connection and the connection-routable tools you can invoke against each.
describe-configured-connectionDescribe one configured connection by id: its non-secret config (type, endpoints, resource ids) and tool availability.
list-topicsList all topics in the Kafka cluster.
create-topicsCreate one or more Kafka topics with an optional partition count and replication factor.
delete-topicsDelete the topics with the given names.
produce-messageProduce records to a Kafka topic. Supports Confluent Schema Registry serialization (AVRO, JSON, PROTOBUF) for keys and values.
consume-messagesConsume messages from Kafka topics. Optionally restrict to a partition and start from an offset, timestamp, earliest, or latest.
list-consumer-groupsList consumer groups on a Kafka cluster (wraps the broker's listGroups admin call), with optional filters.
describe-consumer-groupDescribe a single consumer group on a Kafka cluster: state, type, protocol, partition assignor, and members.
get-consumer-group-lagCompute live offset lag for a single Kafka consumer group, per (topic, partition).
get-partition-offsetsReturn per-partition low/high watermarks and message counts for a Kafka topic.
alter-topic-configAlter topic configuration in Confluent Cloud.
get-topic-configRetrieve configuration details for a specific Kafka topic.
create-flink-statementMake a request to create a Flink SQL statement.
list-flink-statementsRetrieve a sorted, filtered, paginated list of all Flink statements.
read-flink-statementMake a request to read a Flink statement and its results.
delete-flink-statementsMake a request to delete a Flink statement.
get-flink-statement-exceptionsRetrieve the 10 most recent exceptions for a Flink SQL statement.
check-flink-statement-healthPerform an aggregate health check for a Flink SQL statement (healthy/warning/critical).
detect-flink-statement-issuesDetect issues for a Flink SQL statement by analyzing status, exceptions, and performance metrics.
get-flink-statement-profileGet Query Profiler data for a Flink SQL statement, including the task graph and performance metrics.
list-flink-catalogsList all catalogs available in the Flink environment via INFORMATION_SCHEMA.CATALOGS.
list-flink-databasesList all databases (schemas) in a Flink catalog via INFORMATION_SCHEMA.SCHEMATA.
list-flink-tablesList all tables in a Flink database via INFORMATION_SCHEMA.TABLES.
describe-flink-tableGet full schema details for a Flink table via INFORMATION_SCHEMA.COLUMNS.
get-flink-table-infoGet table metadata via INFORMATION_SCHEMA.TABLES: watermark configuration, distribution info, and table type.
list-connectorsRetrieve a list of names of the active connectors.
get-connector-configRetrieve the full configuration map for a connector.
get-connector-offsetsRetrieve current offsets for a connector's tasks.
get-connector-statusGet the current state of a connector and its tasks (RUNNING, FAILED, PAUSED, UNASSIGNED) including failure traces.
get-connector-tasksList the tasks of a connector along with their configurations.
get-connector-error-summarySummarize a connector's current errors in a compact, agent-friendly form.
get-connector-error-recommendationsGet suggested remediation steps for a connector that has failed or is in an error state.
get-connector-logsRetrieve recent log entries for a Confluent Cloud connector from the Cloud logging API.
create-connectorCreate a new connector. Returns the new connector information if successful.
delete-connectorDelete an existing connector.
pause-connectorPause a running connector and its tasks (idempotent).
resume-connectorResume a paused connector and its tasks (idempotent).
restart-connectorRestart a connector and its tasks (asynchronous).
update-connector-configUpdate the configuration of an existing connector (full-replace).
list-schemasList all schemas in the Schema Registry.
create-schemaRegister a new schema (or a new version of an existing schema) under a subject in the Schema Registry.
delete-schemaDelete a schema subject or a specific version from the Schema Registry.
search-topics-by-tagList all topics in the Kafka cluster with the specified tag.
search-topics-by-nameList all topics in the Kafka cluster matching the specified name.
create-topic-tagsCreate new tag definitions in Confluent Cloud.
delete-tagDelete a tag definition from Confluent Cloud.
remove-tag-from-entityRemove a tag from an entity in Confluent Cloud.
add-tags-to-topicAssign existing tags to Kafka topics in Confluent Cloud.
list-tagsRetrieve all tags with definitions from Confluent Cloud Schema Registry.
list-organizationsList Confluent Cloud organizations the current credentials can see (paginated).
list-environmentsGet all environments in Confluent Cloud with pagination support.
read-environmentGet details of a specific environment by ID.
list-clustersGet all clusters in the Confluent Cloud environment.
create-tableflow-topicMake a request to create a Tableflow topic.
list-tableflow-topicsRetrieve a sorted, filtered, paginated list of all Tableflow topics.
read-tableflow-topicMake a request to read a Tableflow topic.
update-tableflow-topicMake a request to update a Tableflow topic.
delete-tableflow-topicMake a request to delete a Tableflow topic.
list-tableflow-regionsRetrieve a sorted, filtered, paginated list of all Tableflow regions.
create-tableflow-catalog-integrationMake a request to create a Tableflow catalog integration (e.g., AWS Glue).
list-tableflow-catalog-integrationsRetrieve a sorted, filtered, paginated list of all catalog integrations.
read-tableflow-catalog-integrationMake a request to read a Tableflow catalog integration.
update-tableflow-catalog-integrationMake a request to update a Tableflow catalog integration.
delete-tableflow-catalog-integrationMake a request to delete a Tableflow catalog integration.
list-available-metricsList available Confluent Cloud metrics and their filter fields from the Telemetry API. Use before query-metrics.
query-metricsQuery Confluent Cloud metrics from the Telemetry API.
list-billing-costsRetrieve billing cost data for a Confluent Cloud organization within a specified date range (paginated).
What this server can do
Confluent MCP Server provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Manage Kafka topics, produce/consume messages, and inspect consumer group lag from an AI assistant
- Author, run, and diagnose Flink SQL statements with health checks and query profiling
- Inspect and manage Kafka Connect connectors, including error summaries and remediation recommendations
- Register and manage Schema Registry schemas (AVRO, JSON, PROTOBUF)
- Organize and search topics with catalog tags
- Query Confluent Cloud operational metrics and billing costs
- Operate self-managed Confluent Platform or local Kafka clusters during development
Security notes
Authenticates to Confluent Cloud via static API keys in config.yaml or OAuth (PKCE). For HTTP/SSE transports, generate an API key with `npx @confluentinc/mcp-confluent --generate-key` and set it under server.auth.api_key; --disable-auth should only be used in development. Includes DNS rebinding protection via --allowed-hosts. Telemetry is collected by default and can be disabled with DO_NOT_TRACK=true.
Confluent MCP Server FAQ
Is this an official Confluent project?
Yes. It is published by the confluentinc organization on GitHub and distributed as the npm package @confluentinc/mcp-confluent under the MIT license.
How do I authenticate to Confluent Cloud?
Two ways: static API keys defined in config.yaml, or OAuth (PKCE) which opens a browser sign-in on the first tool call that needs Confluent access. OAuth currently covers a subset of tool categories (Kafka, Schema Registry, Cloud resource listing, Billing); the rest still require a direct connection with static API keys.
Why don't all the tools show up?
Tools are auto-enabled based on which service blocks are present in your resolved config.yaml. Run `npx @confluentinc/mcp-confluent --list-tools` or invoke the explain-disabled-tools MCP tool to see which are active and why others are absent.
Which transports are supported?
stdio (default), plus optional http and sse. Select them with the --transport flag, e.g. --transport http,sse,stdio.
Can I use it with local Kafka or Confluent Platform instead of Confluent Cloud?
Yes. Point a 'direct' connection at your brokers and Schema Registry. Local/CP deployments expose the Kafka and Schema Registry tools; the Confluent Cloud-only tools (Flink, Tableflow, Billing, Metrics) stay disabled.
Alternatives to Confluent MCP Server
Compare all alternatives →Google's official MCP server with prebuilt BigQuery tools, querying datasets via Application Default Credentials.
Read/write Postgres access plus index tuning, EXPLAIN plans, and database health analysis for AI agents.
Official Supabase server: manage tables, run SQL, branches, configs and edge functions from your AI client.
Compare Confluent MCP Server with: