Can I use Make.com as a CLI?

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

Can I expose Make.com through MCP?

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

Where are Make.com credentials stored?

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

Can I deny write access for Make.com MCP tools?

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

productivity

Make.com CLI for AI Agents

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

Make.com CLI Setup

Make.com can be configured headlessly with `kosmokrator integrations:configure make-com`.

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 make-com --set api_token="$MAKE_COM_API_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor make-com --json
kosmokrator integrations:status --json

Credentials

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

Key	Env var	Type	Required	Label
`api_token`	`MAKE_COM_API_TOKEN`	Secret `secret`	yes	API Token

Command Patterns

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

Generic CLI call

kosmo integrations:call make-com.make_com_list_scenarios '{"organization_id":"example_organization_id","team_id":"example_team_id","folder_id":"example_folder_id","limit":1,"offset":1}' --json

Provider shortcut

kosmo integrations:make-com make_com_list_scenarios '{"organization_id":"example_organization_id","team_id":"example_team_id","folder_id":"example_folder_id","limit":1,"offset":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 make-com --json
kosmo integrations:docs make-com.make_com_list_scenarios --json
kosmo integrations:schema make-com.make_com_list_scenarios --json
kosmo integrations:search "Make.com" --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.

`make-com.make_com_list_scenarios`

List Make.com scenarios the authenticated user has access to. Supports filtering by organization, team, or folder. Use this to discover scenario IDs needed for other tools.

Read read

Parameters: organization_id, team_id, folder_id, limit, offset

Generic call

kosmo integrations:call make-com.make_com_list_scenarios '{"organization_id":"example_organization_id","team_id":"example_team_id","folder_id":"example_folder_id","limit":1,"offset":1}' --json

Shortcut

kosmo integrations:make-com make_com_list_scenarios '{"organization_id":"example_organization_id","team_id":"example_team_id","folder_id":"example_folder_id","limit":1,"offset":1}' --json

`make-com.make_com_get_scenario`

Get detailed information about a Make.com scenario by ID, including its blueprint, scheduling, and status.

Read read

Parameters: id

Generic call

kosmo integrations:call make-com.make_com_get_scenario '{"id":"example_id"}' --json

Shortcut

kosmo integrations:make-com make_com_get_scenario '{"id":"example_id"}' --json

`make-com.make_com_list_executions`

List Make.com scenario executions (runs) with optional filters. Filter by scenario ID or execution status. Useful for monitoring scenario health and debugging failed runs.

Read read

Parameters: scenario_id, status, limit, offset

Generic call

kosmo integrations:call make-com.make_com_list_executions '{"scenario_id":"example_scenario_id","status":"example_status","limit":1,"offset":1}' --json

Shortcut

kosmo integrations:make-com make_com_list_executions '{"scenario_id":"example_scenario_id","status":"example_status","limit":1,"offset":1}' --json

`make-com.make_com_get_execution`

Get detailed information about a Make.com scenario execution (run) by ID, including status, duration, input/output for each module, and any errors.

Read read

Parameters: id

Generic call

kosmo integrations:call make-com.make_com_get_execution '{"id":"example_id"}' --json

Shortcut

kosmo integrations:make-com make_com_get_execution '{"id":"example_id"}' --json

`make-com.make_com_list_connections`

List Make.com connections the authenticated user has access to. Supports filtering by team. Use this to inspect connected services and their status.

Read read

Parameters: team_id, limit, offset

Generic call

kosmo integrations:call make-com.make_com_list_connections '{"team_id":"example_team_id","limit":1,"offset":1}' --json

Shortcut

kosmo integrations:make-com make_com_list_connections '{"team_id":"example_team_id","limit":1,"offset":1}' --json

`make-com.make_com_list_teams`

List Make.com teams (organizations) the authenticated user has access to. Use this to discover team IDs needed for filtering scenarios and connections.

Read read

Parameters: limit, offset

Generic call

kosmo integrations:call make-com.make_com_list_teams '{"limit":1,"offset":1}' --json

Shortcut

kosmo integrations:make-com make_com_list_teams '{"limit":1,"offset":1}' --json

`make-com.make_com_get_current_user`

Get the currently authenticated Make.com user's profile, including ID, name, email, and team memberships.

Read read

Parameters: none

Generic call

kosmo integrations:call make-com.make_com_get_current_user '{}' --json

Shortcut

kosmo integrations:make-com make_com_get_current_user '{}' --json

Function Schemas

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

make-com.make_com_list_scenarios 5 parameters

Schema command

kosmo integrations:schema make-com.make_com_list_scenarios --json

Parameter	Type	Required	Description
`organization_id`	string	no	Filter by organization ID.
`team_id`	string	no	Filter by team ID.
`folder_id`	string	no	Filter by folder ID.
`limit`	integer	no	Number of results per page. Default: 20.
`offset`	integer	no	Offset for pagination.

make-com.make_com_get_scenario 1 parameters

Schema command

kosmo integrations:schema make-com.make_com_get_scenario --json

Parameter	Type	Required	Description
`id`	string	yes	Scenario ID.

make-com.make_com_list_executions 4 parameters

Schema command

kosmo integrations:schema make-com.make_com_list_executions --json

Parameter	Type	Required	Description
`scenario_id`	string	no	Filter by scenario ID.
`status`	string	no	Filter by status (e.g. "success", "error", "warning").
`limit`	integer	no	Number of results per page. Default: 20.
`offset`	integer	no	Offset for pagination.

make-com.make_com_get_execution 1 parameters

Schema command

kosmo integrations:schema make-com.make_com_get_execution --json

Parameter	Type	Required	Description
`id`	string	yes	Execution (run) ID.

make-com.make_com_list_connections 3 parameters

Schema command

kosmo integrations:schema make-com.make_com_list_connections --json

Parameter	Type	Required	Description
`team_id`	string	no	Filter by team ID.
`limit`	integer	no	Number of results per page. Default: 20.
`offset`	integer	no	Offset for pagination.

make-com.make_com_list_teams 2 parameters

Schema command

kosmo integrations:schema make-com.make_com_list_teams --json

Parameter	Type	Required	Description
`limit`	integer	no	Number of results per page. Default: 20.
`offset`	integer	no	Offset for pagination.

make-com.make_com_get_current_user 0 parameters

Schema command

kosmo integrations:schema make-com.make_com_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.