Can I use Zoom as a CLI?

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

Can I expose Zoom through MCP?

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

Where are Zoom credentials stored?

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

Can I deny write access for Zoom MCP tools?

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

communication

Zoom CLI for CI

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

7 functions 6 read 1 write Manual OAuth token auth

Submit Zoom feedback View package source

Zoom CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The Zoom CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Zoom CLI for CI
kosmokrator integrations:configure zoom --set access_token="$ZOOM_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call zoom.zoom_create_meeting '{"topic":"example_topic","type":"example_type","start_time":"example_start_time","duration":1,"timezone":"example_timezone","agenda":"example_agenda","user_id":"example_user_id","settings":"example_settings"}' --json

Discovery Before Execution

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

kosmo integrations:docs zoom --json
kosmo integrations:docs zoom.zoom_create_meeting --json
kosmo integrations:schema zoom.zoom_create_meeting --json
kosmo integrations:search "Zoom" --json
kosmo integrations:list --json

Useful Zoom CLI Functions

Function	Type	Parameters	Description
`zoom.zoom_create_meeting`	Write	topic, type, start_time, duration, timezone, agenda, user_id, settings	Create a new Zoom meeting. Provide a topic, start time (ISO 8601), duration, and optional timezone. Returns the meeting with join URL and password.
`zoom.zoom_get_current_user`	Read	none	Get the profile of the currently authenticated Zoom user. Returns email, name, account type, status, and timezone.
`zoom.zoom_get_meeting`	Read	meeting_id	Get details of a specific Zoom meeting by ID. Returns the meeting topic, agenda, start time, duration, join URL, and settings.
`zoom.zoom_get_user`	Read	user_id	Get details of a specific Zoom user by ID or "me" for the authenticated user. Returns email, name, type, status, and timezone.
`zoom.zoom_list_meetings`	Read	user_id, type, page_size, next_page_token	List meetings for a Zoom user. Returns meeting IDs, topics, start times, durations, and join URLs. Use type "live" for in-progress, "scheduled" for upcoming, or "upcoming" for all upcoming meetings.
`zoom.zoom_list_recordings`	Read	user_id, page_size, next_page_token	List cloud recordings for a Zoom user. Returns recording IDs, topics, start times, durations, and download URLs for recording files.
`zoom.zoom_list_users`	Read	page_size, next_page_token	List users in the Zoom account. Returns user IDs, emails, names, types (1=basic, 2=licensed), and status. Use this to find user IDs for other operations.

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

Cron Jobs Zoom CLI for cron jobs. Shell Scripts Zoom CLI for shell scripts. Headless Automation Zoom CLI for headless automation. Coding Agents Zoom CLI for coding agents.