confluent-mcp.yml
Confluent ships TWO distinct MCP products. The managed servers are remote HTTPS endpoints an agent can POST to today, governed by the caller's existing Confluent Cloud RBAC. The open-source server is a local stdio process a human must install and run first, and Confluent states plainly that it is community-supported with no service level commitments. They are not interchangeable and are recorded separately below.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Descriptor
Candidate descriptor · transport
Tools
list_environments— List all Confluent Cloud environments you can access, including environment IDs, names, and stream governance packages.read_environment— Get details for a specific environment.list_clusters— List Kafka clusters in an environment, including cluster type, cloud provider, region, and availability.read_cluster— Get details and endpoints for a specific cluster.list_connectors— List all connectors in a cluster with name, type, and current status.get_connector_config— Get the full configuration for a connector, including configuration parameters and task list.get_connector_status— Get runtime status and per-task status with error traces (PROVISIONING, RUNNING, DEGRADED, FAILED, PAUSED, DELETED).get_connector_logs— Fetch recent connector logs. ERROR-level by default, optional WARN and INFO. Maximum lookback is 72 hours.get_connector_offsets— Get partition and offset information showing the connector's consumption progress.get_connector_metrics— Fetch time-series metrics for a connector.get_connector_error_summary— Get an AI-generated summary of connector errors extracted from task status and error traces.get_connector_fix_recommendations— Get AI-generated fix recommendations for a failing connector.restart_connector— Restart a connector and its tasks.update_connector_config— Update a connector's configuration. Pass only the fields you want to change; other fields are preserved. You can't remove a field by omitting it.list_metrics— List available metric descriptors, including names, types, and units. Supports resource types kafka, connector, compute_pool, ksql, schema_registry.query_metrics— Query time-series metric data for a cluster, such as throughput or consumer lag. Supports custom time intervals, granularity, and grouping by topic or consumer group.list_kafka_topics— List all topics in a cluster.describe_kafka_topic— Get topic configuration, including partition count and replication factor.consume_kafka_messages— Read one to ten sample messages from a topic. You can target a specific partition and offset.list_schema_subjects— List all schema subjects in Schema Registry, including subject name, version, schema ID, and schema type.read_schema_subject— Get the full schema definition for a subject, including content, version, and references.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.