Can I use Confluent Cloud as a CLI?

Yes. KosmoKrator exposes a Confluent Cloud CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Confluent Cloud through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Confluent Cloud tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Confluent Cloud credentials stored?

Confluent Cloud credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Confluent Cloud MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

data

Confluent Cloud CLI for Shell Scripts

Use the Confluent Cloud CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API token auth

Submit Confluent Cloud feedback View package source

Confluent Cloud CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Confluent Cloud CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Confluent Cloud CLI for Shell Scripts
kosmokrator integrations:configure confluent --set api_token="$CONFLUENT_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call confluent.confluent_list_topics '{"cluster_id":"example_cluster_id"}' --json

Discovery Before Execution

Agents and scripts can inspect Confluent Cloud docs and schemas before choosing a function.

kosmo integrations:docs confluent --json
kosmo integrations:docs confluent.confluent_list_topics --json
kosmo integrations:schema confluent.confluent_list_topics --json
kosmo integrations:search "Confluent Cloud" --json
kosmo integrations:list --json

Useful Confluent Cloud CLI Functions

Function	Type	Parameters	Description
`confluent.confluent_list_topics`	Read	cluster_id	List Kafka topics in a Confluent cluster. Returns topic names, partition counts, replication factors, and status.
`confluent.confluent_get_topic`	Read	topic_name, cluster_id	Get full details of a specific Kafka topic by name. Returns partition count, replication factor, and topic configuration.
`confluent.confluent_create_topic`	Write	topic_name, partitions_count, replication_factor, configs, cluster_id	Create a new Kafka topic in a Confluent cluster. Specify the topic name, partition count, and optional replication factor and configs.
`confluent.confluent_list_clusters`	Read	none	List Kafka clusters in your Confluent Cloud environment. Returns cluster IDs, names, types, and status.
`confluent.confluent_get_cluster`	Read	cluster_id	Get details of a specific Kafka cluster. Returns broker count, controller info, and cluster configuration.
`confluent.confluent_list_environments`	Read	none	List Confluent Cloud environments. Returns environment IDs, names, and associated cluster resources.
`confluent.confluent_get_current_user`	Read	none	Get the currently authenticated Confluent Cloud user. Useful for verifying credentials and identifying the connected account.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Confluent Cloud CLI Pages

CI Confluent Cloud CLI for CI. Cron Jobs Confluent Cloud CLI for cron jobs. Headless Automation Confluent Cloud CLI for headless automation. Coding Agents Confluent Cloud CLI for coding agents.