Loading...

The mcp-confluent server enables AI assistants to interact with Confluent Cloud REST APIs for managing Kafka, Flink, and related services via natural language.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
The mcp-confluent server enables AI assistants to interact with Confluent Cloud REST APIs for managing Kafka, Flink, and related services via natural language.
This server provides some security measures like API key authentication and host validation. However, the ability to perform write and delete operations on critical infrastructure components means that compromised credentials could lead to significant damage. Use with caution and restrict API key access.
Performance depends on the Confluent Cloud infrastructure and the complexity of the operations being performed. Consider the impact of automated actions on cluster resources.
Automated actions can incur costs associated with Confluent Cloud API calls, resource utilization (e.g., Kafka topics, Flink compute), and data transfer.
npx @confluentinc/mcp-confluent --generate-key{
"mcpServers": {
"confluent": {
"command": "node",
"args": [
"/path/to/confluent-mcp-server/dist/index.js",
"--env-file",
"/path/to/confluent-mcp-server/.env",
]
}
}
}MCP_API_KEYCreate Kafka TopicCreates a new Kafka topic with specified configurations.
Creates new resources, impacting cluster capacity and potentially data governance.
Delete Kafka TopicDeletes an existing Kafka topic, including its data.
Destructive operation that permanently removes data.
List Kafka TopicsLists all Kafka topics in the cluster.
Read-only operation with no side effects.
Create Flink SQL StatementCreates a new Flink SQL statement for data processing.
Creates a new data processing job that could consume resources.
Delete Flink SQL StatementDeletes an existing Flink SQL statement.
Removes a data processing job, potentially disrupting data pipelines.
List ConnectorsLists all Kafka Connect connectors.
Read-only operation.
Create ConnectorCreates a new Kafka Connect connector.
Creates a new connector, impacting data flow and resource utilization.
Delete ConnectorDeletes a Kafka Connect connector.
Removes a connector, potentially disrupting data ingestion or egress.
API Key
hybrid
This server provides some security measures like API key authentication and host validation. However, the ability to perform write and delete operations on critical infrastructure components means that compromised credentials could lead to significant damage. Use with caution and restrict API key access.
The level of autonomy depends on the tool and the permissions granted to the API key. Exercise caution when granting write or delete permissions.
Production Tip
Implement robust monitoring and alerting to detect and respond to any issues caused by automated actions.
The server uses API key authentication and DNS rebinding protection. However, it's crucial to protect your API keys and limit their permissions.
Yes, you can configure the server to connect to different Confluent Cloud environments by setting the appropriate environment variables.
Use the command `npx @confluentinc/mcp-confluent --generate-key` to generate a secure API key.
No, disabling authentication is only recommended for local development and should never be done in production environments.
Immediately revoke the compromised API key and generate a new one. Also, review your Confluent Cloud audit logs for any suspicious activity.
Monitor the Confluent Cloud audit logs and implement alerting to detect any unauthorized or unexpected actions.
The documentation does not explicitly mention RBAC beyond API key authentication. Consider implementing additional access controls at the Confluent Cloud level.