Can I use Whereby as a CLI?

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

Can I expose Whereby through MCP?

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

Where are Whereby credentials stored?

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

Can I deny write access for Whereby MCP tools?

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

productivity

Whereby CLI for AI Agents

Use the Whereby CLI from KosmoKrator to call Whereby tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Whereby CLI Setup

Whereby can be configured headlessly with `kosmokrator integrations:configure whereby`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure whereby --set access_token="$WHEREBY_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor whereby --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`WHEREBY_ACCESS_TOKEN`	Secret `secret`	yes	API Key
`url`	`WHEREBY_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call whereby.whereby_list_rooms '{"limit":1,"cursor":"example_cursor"}' --json

Provider shortcut

kosmo integrations:whereby whereby_list_rooms '{"limit":1,"cursor":"example_cursor"}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs whereby --json
kosmo integrations:docs whereby.whereby_list_rooms --json
kosmo integrations:schema whereby.whereby_list_rooms --json
kosmo integrations:search "Whereby" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`whereby.whereby_list_rooms`

List Whereby rooms with optional pagination and filtering.

Read read

Parameters: limit, cursor

Generic call

kosmo integrations:call whereby.whereby_list_rooms '{"limit":1,"cursor":"example_cursor"}' --json

Shortcut

kosmo integrations:whereby whereby_list_rooms '{"limit":1,"cursor":"example_cursor"}' --json

`whereby.whereby_get_room`

Get detailed information about a specific Whereby room, including meeting URL, configuration, and host details.

Read read

Parameters: room_name

Generic call

kosmo integrations:call whereby.whereby_get_room '{"room_name":"example_room_name"}' --json

Shortcut

kosmo integrations:whereby whereby_get_room '{"room_name":"example_room_name"}' --json

`whereby.whereby_create_room`

Create a new Whereby video meeting room with optional configuration such as room mode, time limits, and participant settings.

Write write

Parameters: room_mode, room_name_prefix, start_date, end_date, fields

Generic call

kosmo integrations:call whereby.whereby_create_room '{"room_mode":"example_room_mode","room_name_prefix":"example_room_name_prefix","start_date":"example_start_date","end_date":"example_end_date","fields":"example_fields"}' --json

Shortcut

kosmo integrations:whereby whereby_create_room '{"room_mode":"example_room_mode","room_name_prefix":"example_room_name_prefix","start_date":"example_start_date","end_date":"example_end_date","fields":"example_fields"}' --json

`whereby.whereby_delete_room`

Delete a Whereby room by its name. This action is permanent and cannot be undone.

Write write

Parameters: room_name

Generic call

kosmo integrations:call whereby.whereby_delete_room '{"room_name":"example_room_name"}' --json

Shortcut

kosmo integrations:whereby whereby_delete_room '{"room_name":"example_room_name"}' --json

`whereby.whereby_list_meetings`

List past Whereby meetings with optional pagination and date filtering.

Read read

Parameters: limit, cursor, from_date, to_date, room_name

Generic call

kosmo integrations:call whereby.whereby_list_meetings '{"limit":1,"cursor":"example_cursor","from_date":"example_from_date","to_date":"example_to_date","room_name":"example_room_name"}' --json

Shortcut

kosmo integrations:whereby whereby_list_meetings '{"limit":1,"cursor":"example_cursor","from_date":"example_from_date","to_date":"example_to_date","room_name":"example_room_name"}' --json

`whereby.whereby_get_meeting`

Get detailed information about a specific past Whereby meeting, including participants, duration, and recording status.

Read read

Parameters: meeting_id

Generic call

kosmo integrations:call whereby.whereby_get_meeting '{"meeting_id":"example_meeting_id"}' --json

Shortcut

kosmo integrations:whereby whereby_get_meeting '{"meeting_id":"example_meeting_id"}' --json

`whereby.whereby_get_current_user`

Get the profile information of the currently authenticated Whereby user, including account details and plan information.

Read read

Parameters: none

Generic call

kosmo integrations:call whereby.whereby_get_current_user '{}' --json

Shortcut

kosmo integrations:whereby whereby_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

whereby.whereby_list_rooms 2 parameters

Schema command

kosmo integrations:schema whereby.whereby_list_rooms --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of rooms to return.
`cursor`	string	no	Pagination cursor for fetching the next page of results.

whereby.whereby_get_room 1 parameters

Schema command

kosmo integrations:schema whereby.whereby_get_room --json

Parameter	Type	Required	Description
`room_name`	string	yes	The unique name or identifier of the Whereby room.

whereby.whereby_create_room 5 parameters

Schema command

kosmo integrations:schema whereby.whereby_create_room --json

Parameter	Type	Required	Description
`room_mode`	string	no	Room mode, e.g. "normal" or "group".
`room_name_prefix`	string	no	Optional prefix for the generated room name.
`start_date`	string	no	ISO 8601 start date/time for the room.
`end_date`	string	no	ISO 8601 end date/time for the room.
`fields`	array	no	Additional room configuration fields such as lockRoomOnJoin, recording, etc.

whereby.whereby_delete_room 1 parameters

Schema command

kosmo integrations:schema whereby.whereby_delete_room --json

Parameter	Type	Required	Description
`room_name`	string	yes	The unique name or identifier of the Whereby room to delete.

whereby.whereby_list_meetings 5 parameters

Schema command

kosmo integrations:schema whereby.whereby_list_meetings --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of meetings to return.
`cursor`	string	no	Pagination cursor for fetching the next page of results.
`from_date`	string	no	ISO 8601 start date to filter meetings from.
`to_date`	string	no	ISO 8601 end date to filter meetings to.
`room_name`	string	no	Filter meetings by room name.

whereby.whereby_get_meeting 1 parameters

Schema command

kosmo integrations:schema whereby.whereby_get_meeting --json

Parameter	Type	Required	Description
`meeting_id`	string	yes	The unique identifier of the meeting.

whereby.whereby_get_current_user 0 parameters

Schema command

kosmo integrations:schema whereby.whereby_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.