Can I use Cloudinary as a CLI?

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

Can I expose Cloudinary through MCP?

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

Where are Cloudinary credentials stored?

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

Can I deny write access for Cloudinary MCP tools?

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

other

Cloudinary CLI for Headless Automation

Use the Cloudinary CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

6 functions 4 read 2 write Manual OAuth token auth

Submit Cloudinary feedback View package source

Cloudinary CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Cloudinary CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Cloudinary CLI for Headless Automation
kosmokrator integrations:configure cloudinary --set access_token="$CLOUDINARY_ACCESS_TOKEN" --set cloud_name="$CLOUDINARY_CLOUD_NAME" --enable --read allow --write ask --json
kosmo integrations:call cloudinary.cloudinary_upload '{"file":"example_file","public_id":"example_public_id","folder":"example_folder"}' --json

Discovery Before Execution

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

kosmo integrations:docs cloudinary --json
kosmo integrations:docs cloudinary.cloudinary_upload --json
kosmo integrations:schema cloudinary.cloudinary_upload --json
kosmo integrations:search "Cloudinary" --json
kosmo integrations:list --json

Useful Cloudinary CLI Functions

Function	Type	Parameters	Description
`cloudinary.cloudinary_upload`	Write	file, public_id, folder	Upload an image to Cloudinary. Provide a file URL or base64 data URI, an optional public ID, and an optional folder path. Returns the uploaded asset details.
`cloudinary.cloudinary_list_resources`	Read	type, max_results, next_cursor, prefix	List media resources in your Cloudinary cloud. Filter by resource type (image, video, raw) and prefix. Supports pagination with max_results and next_cursor.
`cloudinary.cloudinary_get_resource`	Read	type, public_id	Get details of a specific Cloudinary resource by its type and public ID. Returns full asset metadata including dimensions, format, URL, tags, and derived resources.
`cloudinary.cloudinary_delete_resource`	Write	type, public_id	Delete a media resource from Cloudinary by its type and public ID. This permanently removes the asset and all its derived resources.
`cloudinary.cloudinary_list_folders`	Read	max_results, next_cursor	List all folders in your Cloudinary cloud. Returns folder names and paths with pagination support.
`cloudinary.cloudinary_get_current_user`	Read	none	Get the currently authenticated Cloudinary user profile. Returns user name, email, and account details. Use this to verify that credentials are working.

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 Cloudinary CLI Pages

CI Cloudinary CLI for CI. Cron Jobs Cloudinary CLI for cron jobs. Shell Scripts Cloudinary CLI for shell scripts. Coding Agents Cloudinary CLI for coding agents.