# Confluent MCP for AI Agents MCP

> Confluent MCP gives your AI agent direct access to the Confluent Cloud API, letting you manage complex Kafka clusters and data streams through natural language commands. You can check cluster health, list topics across environments, audit connectors, and verify configuration states without logging into a dashboard.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Tags:** apache-kafka, data-streaming, event-processing, cluster-monitoring, topic-management

## Description

This MCP connects your AI client directly to Confluent Cloud, the platform built on Apache Kafka for enterprise data streaming. It lets you treat your entire streaming infrastructure—from clusters to individual topics—as if it were sitting right in your chat window. Instead of navigating complex dashboards or writing boilerplate CLI scripts, you simply ask your agent what you need. For instance, you can request a list of all active environments, then check the health of a specific cluster within that environment, and finally audit which connectors are running. It’s about doing deep infrastructure work using just conversation. If you're building out an advanced AI toolset, Vinkius makes it easy to connect this level of data governance capability into your existing workflow.

## Tools

### get_cluster_details
Retrieves detailed information on a specific Kafka cluster, including its endpoint URLs and availability status.

### list_cloud_api_keys
Gets a list of all API keys currently active in your Confluent Cloud account for security auditing.

### list_clusters
Returns an overview of all Kafka clusters in your organization, showing their status and cloud provider region.

### list_connectors
Retrieves the configured source and sink connectors for a given environment or cluster to check their operational status.

### list_environments
Provides a list of available Confluent Cloud environments, which are needed identifiers for other operations.

### list_service_accounts
Retrieves service accounts used in your organization, useful when auditing programmatic access permissions.

### list_topics
Returns a comprehensive list of all topics, including their partition count and replication settings for quick review.

## Prompt Examples

**Prompt:** 
```
Which environments do I have available for my Kafka streams?
```

**Response:** 
```
**Confluent Cloud Environments Found:**

*   `staging-us`: Used for testing new features.
*   `production-eu`: Live environment for European data.
*   `dev-sandbox`: Sandbox for individual developer work.

You can use these IDs to check specific cluster details or topic lists.
```

**Prompt:** 
```
Check the status of all my Kafka clusters and tell me which one is in the EU region.
```

**Response:** 
```
I found 3 active clusters:

*   **Cluster A (US-EAST):** Status: Healthy. Provisioning: Complete.
*   **Cluster B (EU-WEST):** Status: Warning. Node count mismatch detected on node 4.
*   **Cluster C (US-WEST):** Status: Healthy. Provisioning: Complete.
The EU cluster (`Cluster B`) needs attention regarding its node count.
```

**Prompt:** 
```
List all topics that are part of the staging environment and tell me their partition counts.
```

**Response:** 
```
**Topics in `staging-us`:**

| Topic Name | Partitions | Replication Factor |
| :--- | :--- | :--- |
| user_login_events | 12 | 3 |
| payment_updates | 6 | 3 |
| analytics_stream | 8 | 3 |
These topics look correctly configured for staging.
```

## Capabilities

### Audit and list all environments
Discover the necessary environment IDs needed to perform operations on specific clusters or connectors.

### Inventory Kafka clusters
Retrieve a comprehensive list of all your available Kafka clusters, including their cloud provider and region status.

### Check cluster health metrics
Get detailed information on a specific cluster's configuration, endpoint URLs, availability, and provisioning status.

### Manage streaming topics
List all existing Kafka topics, viewing their partition count and replication configurations at a glance.

### Monitor data pipelines (connectors)
View the status of configured source and sink connectors, confirming if your data ingestion pipes are running correctly.

### Audit programmatic access
List service accounts or retrieve Cloud API keys to audit who has access to your Kafka organization.

## Use Cases

### A cluster is suddenly showing high latency
The DevOps team needs to know the root cause quickly. They ask their agent to run `get_cluster_details` and check the status of all connectors via `list_connectors`. The response immediately flags a specific connector as failing, directing the team straight to the broken pipeline.

### Pre-deployment topic audit is required
A Data Engineer needs to know if their new topic setup meets governance standards. They use `list_topics` to check existing topics for correct partition counts and replication factors across all environments, verifying compliance before committing the change.

### Investigating unauthorized access
An architect suspects a breach. They run `list_service_accounts` and immediately review the list of authorized credentials alongside using `list_cloud_api_keys` to see if any keys were recently generated outside normal process.

### Mapping out all data sources
A new team member needs a full picture of the streaming landscape. They ask their agent to first run `list_environments`, then use that ID list to check every active cluster using `list_clusters`.

## Benefits

- Quickly check cluster health using `get_cluster_details`. Instead of SSHing into a machine to verify node status, your agent gives you an immediate summary of CPU metrics and availability.
- Audit entire stream definitions by calling `list_environments` first. This ensures you have the correct IDs before attempting to inspect topics or connectors in a specific scope.
- Verify data pipeline integrity by running `list_connectors`. You can instantly confirm if your critical source-sink connections are active and report any failed tasks.
- Maintain security visibility using `list_service_accounts` and `list_cloud_api_keys`. You get an immediate, centralized audit log of who has access to the core Kafka infrastructure.
- Streamline topic governance with `list_topics`. See every relevant stream's partition count and replication factor without running multiple manual commands.
- Reduce operational friction by combining checks. Your agent can list environments, then check clusters in that environment, all from one prompt.

## How It Works

The bottom line is: you use simple conversation to perform complex data governance tasks that usually require multiple clicks in a specialized dashboard.

1. Add the Confluent integration to your AI client's toolset.
2. Provide your necessary Confluent Cloud API Key and Secret credentials.
3. Ask your agent a natural language question, like 'What is the CPU utilization for the main production cluster?'

## Frequently Asked Questions

**How can I check the current health of all my Kafka clusters with Confluent MCP?**
You can get a list of all clusters, then request detailed status reports for any specific one. This tells you if nodes are available and provides key metrics like CPU usage.

**I need to see every active topic in my streaming platform.**
Confluent MCP allows you to list all topics across a given cluster, providing the partition count and replication factor for quick compliance checks.

**How do I use Confluent MCP to audit data access?**
You can audit access by listing service accounts or retrieving API keys. This gives you a clear record of who has programmatic rights across your Kafka organization.

**Does Confluent MCP help me find the IDs for different environments?**
Yes, it provides a list of all available environments. Knowing these IDs is critical because they are needed to scope any cluster or connector operation correctly.