mcp-confluent
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONFIG_PATH | Yes | File system path to store and retrieve conversation-based configurations for session persistence (Future Implementation) | |
| FLINK_ENV_ID | No | Unique identifier for the Flink environment, must start with 'env-' prefix | |
| FLINK_ORG_ID | No | Organization identifier within Confluent Cloud for Flink resource management | |
| KAFKA_ENV_ID | No | Environment identifier for Kafka cluster, must start with 'env-' prefix | |
| FLINK_API_KEY | Yes | Authentication key for accessing Confluent Cloud's Flink services, including compute pools and SQL statement management | |
| KAFKA_API_KEY | Yes | Authentication credential (username) required to establish secure connection with the Kafka cluster | |
| FLINK_ENV_NAME | No | Human-readable name for the Flink environment used for identification and display purposes | |
| FLINK_API_SECRET | Yes | Secret token paired with FLINK_API_KEY for authenticated access to Confluent Cloud's Flink services | |
| KAFKA_API_SECRET | Yes | Authentication credential (password) paired with KAFKA_API_KEY for secure Kafka cluster access | |
| KAFKA_CLUSTER_ID | No | Unique identifier for the Kafka cluster within Confluent Cloud ecosystem | |
| BOOTSTRAP_SERVERS | Yes | List of Kafka broker addresses in the format host1:port1,host2:port2 used to establish initial connection to the Kafka cluster | |
| FLINK_DATABASE_NAME | No | Name of the associated Kafka cluster used as a database reference in Flink SQL operations | |
| FLINK_REST_ENDPOINT | No | Base URL for Confluent Cloud's Flink REST API endpoints used for SQL statement and compute pool management | |
| KAFKA_REST_ENDPOINT | No | REST API endpoint for Kafka cluster management and administration | |
| FLINK_COMPUTE_POOL_ID | No | Unique identifier for the Flink compute pool, must start with 'lfcp-' prefix | |
| CONFLUENT_CLOUD_API_KEY | Yes | Master API key for Confluent Cloud platform administration, enabling management of resources across your organization | |
| SCHEMA_REGISTRY_API_KEY | Yes | Authentication key for accessing Schema Registry services to manage and validate data schemas | |
| SCHEMA_REGISTRY_ENDPOINT | No | URL endpoint for accessing Schema Registry services to manage data schemas | |
| CONFLUENT_CLOUD_API_SECRET | Yes | Master API secret paired with CONFLUENT_CLOUD_API_KEY for comprehensive Confluent Cloud platform administration | |
| SCHEMA_REGISTRY_API_SECRET | Yes | Authentication secret paired with SCHEMA_REGISTRY_API_KEY for secure Schema Registry access | |
| CONFLUENT_CLOUD_REST_ENDPOINT | No | Base URL for Confluent Cloud's REST API services |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-topicsB | List all topics in the Kafka cluster. |
| create-topicsC | Create new topic(s) in the Kafka cluster. |
| delete-topicsB | Delete the topic with the given names. |
| produce-messageA | Produce records to a Kafka topic. For saving user messages/history they should be saved to a kafka topic named claude-conversations unless otherwise specified. If the topic does not exist, it will be created via the create-topics tool. |
| list-flink-statementsB | Retrieve a sorted, filtered, paginated list of all statements. |
| create-flink-statementC | Make a request to create a statement. |
| read-flink-statementC | Make a request to read a statement and its results |
| delete-flink-statementsC | Make a request to delete a statement. |
| list-connectorsA | Retrieve a list of "names" of the active connectors. You can then make a read request for a specific connector by name. |
| read-connectorC | Get information about the connector. |
| create-connectorB | Create a new connector. Returns the new connector information if successful. |
| delete-connectorC | Delete an existing connector. Returns success message if deletion was successful. |
| search-topics-by-tagC | List all topics in the Kafka cluster with the specified tag. |
| search-topics-by-nameC | List all topics in the Kafka cluster matching the specified name. |
| create-topic-tagsC | Create new tag definitions in Confluent Cloud. |
| delete-tagC | Delete a tag definition from Confluent Cloud. |
| remove-tag-from-entityC | Remove tag from an entity in Confluent Cloud. |
| add-tags-to-topicC | Assign existing tags to Kafka topics in Confluent Cloud. |
| list-tagsC | Retrieve all tags with definitions from Confluent Cloud Schema Registry. |
| alter-topic-configC | Alter topic configuration in Confluent Cloud. |
| list-clustersC | Get all clusters in the Confluent Cloud environment |
| list-environmentsB | Get all environments in Confluent Cloud with pagination support |
| read-environmentB | Get details of a specific environment by ID |
| list-schemasC | List all schemas in the Schema Registry. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/confluentinc/mcp-confluent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server