Can I use Loom as a CLI?

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

Can I expose Loom through MCP?

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

Where are Loom credentials stored?

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

Can I deny write access for Loom MCP tools?

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

data

Loom CLI for AI Agents

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

Loom CLI Setup

Loom can be configured headlessly with `kosmokrator integrations:configure loom`.

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 loom --set access_token="$LOOM_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor loom --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`	`LOOM_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`LOOM_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 loom.loom_list_videos '{"limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:loom loom_list_videos '{"limit":1,"page":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 loom --json
kosmo integrations:docs loom.loom_list_videos --json
kosmo integrations:schema loom.loom_list_videos --json
kosmo integrations:search "Loom" --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.

`loom.loom_list_videos`

List Loom videos. Returns video titles, IDs, durations, URLs, and creation dates. Use limit and page for pagination.

Read read

Parameters: limit, page

Generic call

kosmo integrations:call loom.loom_list_videos '{"limit":1,"page":1}' --json

Shortcut

kosmo integrations:loom loom_list_videos '{"limit":1,"page":1}' --json

`loom.loom_get_video`

Get detailed information about a specific Loom video by its ID, including playback URL, duration, thumbnail, and metadata.

Read read

Parameters: video_id

Generic call

kosmo integrations:call loom.loom_get_video '{"video_id":"example_video_id"}' --json

Shortcut

kosmo integrations:loom loom_get_video '{"video_id":"example_video_id"}' --json

`loom.loom_create_video`

Create a new Loom video with a title and optional description. Returns the video details and upload URLs.

Write write

Parameters: title, description

Generic call

kosmo integrations:call loom.loom_create_video '{"title":"example_title","description":"example_description"}' --json

Shortcut

kosmo integrations:loom loom_create_video '{"title":"example_title","description":"example_description"}' --json

`loom.loom_delete_video`

Delete a Loom video permanently. This action cannot be undone.

Write write

Parameters: video_id

Generic call

kosmo integrations:call loom.loom_delete_video '{"video_id":"example_video_id"}' --json

Shortcut

kosmo integrations:loom loom_delete_video '{"video_id":"example_video_id"}' --json

`loom.loom_list_workspaces`

List all Loom workspaces accessible to the authenticated user, including workspace names and member information.

Read read

Parameters: none

Generic call

kosmo integrations:call loom.loom_list_workspaces '{}' --json

Shortcut

kosmo integrations:loom loom_list_workspaces '{}' --json

`loom.loom_list_folders`

List Loom folders. Returns folder names, IDs, and video counts. Use limit and page for pagination.

Read read

Parameters: limit, page

Generic call

kosmo integrations:call loom.loom_list_folders '{"limit":1,"page":1}' --json

Shortcut

kosmo integrations:loom loom_list_folders '{"limit":1,"page":1}' --json

`loom.loom_get_folder`

Get detailed information about a specific Loom folder by its ID, including name, video count, and hierarchy.

Read read

Parameters: folder_id

Generic call

kosmo integrations:call loom.loom_get_folder '{"folder_id":"example_folder_id"}' --json

Shortcut

kosmo integrations:loom loom_get_folder '{"folder_id":"example_folder_id"}' --json

`loom.loom_get_current_user`

Get the authenticated Loom user's profile information, including name, email, and account details.

Read read

Parameters: none

Generic call

kosmo integrations:call loom.loom_get_current_user '{}' --json

Shortcut

kosmo integrations:loom loom_get_current_user '{}' --json

Function Schemas

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

loom.loom_list_videos 2 parameters

Schema command

kosmo integrations:schema loom.loom_list_videos --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of videos to return (default: 20, max: 50).
`page`	integer	no	Page number for pagination (default: 1).

loom.loom_get_video 1 parameters

Schema command

kosmo integrations:schema loom.loom_get_video --json

Parameter	Type	Required	Description
`video_id`	string	yes	The unique identifier of the Loom video.

loom.loom_create_video 2 parameters

Schema command

kosmo integrations:schema loom.loom_create_video --json

Parameter	Type	Required	Description
`title`	string	yes	The title of the video.
`description`	string	no	An optional description for the video.

loom.loom_delete_video 1 parameters

Schema command

kosmo integrations:schema loom.loom_delete_video --json

Parameter	Type	Required	Description
`video_id`	string	yes	The unique identifier of the Loom video to delete.

loom.loom_list_workspaces 0 parameters

Schema command

kosmo integrations:schema loom.loom_list_workspaces --json

Parameter	Type	Required	Description
No parameters.

loom.loom_list_folders 2 parameters

Schema command

kosmo integrations:schema loom.loom_list_folders --json

Parameter	Type	Required	Description
`limit`	integer	no	Maximum number of folders to return (default: 20).
`page`	integer	no	Page number for pagination (default: 1).

loom.loom_get_folder 1 parameters

Schema command

kosmo integrations:schema loom.loom_get_folder --json

Parameter	Type	Required	Description
`folder_id`	string	yes	The unique identifier of the Loom folder.

loom.loom_get_current_user 0 parameters

Schema command

kosmo integrations:schema loom.loom_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.