Can I use Calendly as a CLI?

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

Can I expose Calendly through MCP?

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

Where are Calendly credentials stored?

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

Can I deny write access for Calendly MCP tools?

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

productivity

Calendly CLI for AI Agents

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

Calendly CLI Setup

Calendly can be configured headlessly with `kosmokrator integrations:configure calendly`.

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 calendly --set access_token="$CALENDLY_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor calendly --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`	`CALENDLY_ACCESS_TOKEN`	Secret `secret`	yes	Personal Access Token

Command Patterns

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

Generic CLI call

kosmo integrations:call calendly.calendly_list_event_types '{"user":"example_user","organization":"example_organization","active":true,"page_token":"example_page_token","count":1}' --json

Provider shortcut

kosmo integrations:calendly calendly_list_event_types '{"user":"example_user","organization":"example_organization","active":true,"page_token":"example_page_token","count":1}' --json

Discovery

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

Discovery commands

kosmo integrations:docs calendly --json
kosmo integrations:docs calendly.calendly_list_event_types --json
kosmo integrations:schema calendly.calendly_list_event_types --json
kosmo integrations:search "Calendly" --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.

`calendly.calendly_list_event_types`

List event types for a Calendly user or organization.

Read read

Parameters: user, organization, active, page_token, count

Generic call

kosmo integrations:call calendly.calendly_list_event_types '{"user":"example_user","organization":"example_organization","active":true,"page_token":"example_page_token","count":1}' --json

Shortcut

kosmo integrations:calendly calendly_list_event_types '{"user":"example_user","organization":"example_organization","active":true,"page_token":"example_page_token","count":1}' --json

`calendly.calendly_get_event_type`

Get a single Calendly event type by UUID.

Read read

Parameters: uuid

Generic call

kosmo integrations:call calendly.calendly_get_event_type '{"uuid":"example_uuid"}' --json

Shortcut

kosmo integrations:calendly calendly_get_event_type '{"uuid":"example_uuid"}' --json

`calendly.calendly_create_booking`

Create a booking in Calendly by generating a one-off event type with a scheduling URL for the invitee.

Write write

Parameters: host, start_time, end_time, location, name

Generic call

kosmo integrations:call calendly.calendly_create_booking '{"host":"example_host","start_time":"example_start_time","end_time":"example_end_time","location":"example_location","name":"example_name"}' --json

Shortcut

kosmo integrations:calendly calendly_create_booking '{"host":"example_host","start_time":"example_start_time","end_time":"example_end_time","location":"example_location","name":"example_name"}' --json

`calendly.calendly_list_bookings`

List scheduled Calendly bookings (events) with optional filters.

Read read

Parameters: user, organization, status, min_start_time, max_start_time, page_token, count

Generic call

kosmo integrations:call calendly.calendly_list_bookings '{"user":"example_user","organization":"example_organization","status":"example_status","min_start_time":"example_min_start_time","max_start_time":"example_max_start_time","page_token":"example_page_token","count":1}' --json

Shortcut

kosmo integrations:calendly calendly_list_bookings '{"user":"example_user","organization":"example_organization","status":"example_status","min_start_time":"example_min_start_time","max_start_time":"example_max_start_time","page_token":"example_page_token","count":1}' --json

`calendly.calendly_list_organizations`

List Calendly organizations the authenticated user belongs to.

Read read

Parameters: page_token

Generic call

kosmo integrations:call calendly.calendly_list_organizations '{"page_token":"example_page_token"}' --json

Shortcut

kosmo integrations:calendly calendly_list_organizations '{"page_token":"example_page_token"}' --json

`calendly.calendly_list_users`

List users (organization memberships) in a Calendly organization.

Read read

Parameters: organization, user, page_token, count

Generic call

kosmo integrations:call calendly.calendly_list_users '{"organization":"example_organization","user":"example_user","page_token":"example_page_token","count":1}' --json

Shortcut

kosmo integrations:calendly calendly_list_users '{"organization":"example_organization","user":"example_user","page_token":"example_page_token","count":1}' --json

`calendly.calendly_get_current_user`

Get the authenticated Calendly user profile.

Read read

Parameters: none

Generic call

kosmo integrations:call calendly.calendly_get_current_user '{}' --json

Shortcut

kosmo integrations:calendly calendly_get_current_user '{}' --json

Function Schemas

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

calendly.calendly_list_event_types 5 parameters

Schema command

kosmo integrations:schema calendly.calendly_list_event_types --json

Parameter	Type	Required	Description
`user`	string	no	The user URI to filter by (e.g. https://api.calendly.com/users/...).
`organization`	string	no	The organization URI to filter by.
`active`	boolean	no	Filter by active status. true returns only active event types.
`page_token`	string	no	Pagination token from a previous response.
`count`	integer	no	Number of results per page (default 20, max 100).

calendly.calendly_get_event_type 1 parameters

Schema command

kosmo integrations:schema calendly.calendly_get_event_type --json

Parameter	Type	Required	Description
`uuid`	string	yes	The event type UUID.

calendly.calendly_create_booking 5 parameters

Schema command

kosmo integrations:schema calendly.calendly_create_booking --json

Parameter	Type	Required	Description
`host`	string	yes	The host user URI (e.g. https://api.calendly.com/users/...).
`start_time`	string	yes	Start time in ISO 8601 format (e.g. 2024-06-15T10:00:00Z).
`end_time`	string	yes	End time in ISO 8601 format (e.g. 2024-06-15T11:00:00Z).
`location`	object	no	Location object with "type" (e.g. "zoom", "google_conference", "custom") and optional "location".
`name`	string	no	Name for the booking / event type.

calendly.calendly_list_bookings 7 parameters

Schema command

kosmo integrations:schema calendly.calendly_list_bookings --json

Parameter	Type	Required	Description
`user`	string	no	The user URI to filter by.
`organization`	string	no	The organization URI to filter by.
`status`	string	no	Filter by status: "active" or "canceled".
`min_start_time`	string	no	ISO 8601 lower bound for start time.
`max_start_time`	string	no	ISO 8601 upper bound for start time.
`page_token`	string	no	Pagination token from a previous response.
`count`	integer	no	Number of results per page (default 20, max 100).

calendly.calendly_list_organizations 1 parameters

Schema command

kosmo integrations:schema calendly.calendly_list_organizations --json

Parameter	Type	Required	Description
`page_token`	string	no	Pagination token from a previous response.

calendly.calendly_list_users 4 parameters

Schema command

kosmo integrations:schema calendly.calendly_list_users --json

Parameter	Type	Required	Description
`organization`	string	no	The organization URI to filter by (e.g. https://api.calendly.com/organizations/...).
`user`	string	no	The user URI to filter by.
`page_token`	string	no	Pagination token from a previous response.
`count`	integer	no	Number of results per page (default 20, max 100).

calendly.calendly_get_current_user 0 parameters

Schema command

kosmo integrations:schema calendly.calendly_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.